Skip to content

Update Developer-Server-Build.md - use whole path so you can copy and… #83

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 9, 2025
Merged

Update Developer-Server-Build.md - use whole path so you can copy and… #83

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions doc/iocs/compiling/Developer-Server-Build.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,8 +8,10 @@ You need to be using a Visual Studio compatible with the build server, currently
:::{tip}
**Quick Instructions**

Run `install_developer_build.bat` in either `\\isis.cclrc.ac.uk\inst$\Kits$\CompGroup\ICP\developer\EPICS` (for 64bit builds, what you usually need) or `\\isis.cclrc.ac.uk\inst$\Kits$\CompGroup\ICP\developer\EPICS32` (for 32 bit builds, only if you have to build/test a specific driver needing 32bit versions). It will prompt you to choose from normal/debug/static - in most cases `normal`
is what you want and is what is deployed to an instrument, `static` and `debug` are for special cases/testing
Run `\\isis.cclrc.ac.uk\inst$\Kits$\CompGroup\ICP\developer\EPICS\install_developer_build.bat`. It will prompt you to choose from normal/debug/static - in most cases `normal`
is what you want and is what is deployed to an instrument, `static` and `debug` are for special cases/testing.

For 32 bit builds, (only if you have to build/test a specific driver needing 32bit versions) run `\\isis.cclrc.ac.uk\inst$\Kits$\CompGroup\ICP\developer\EPICS32\install_developer_build.bat`
:::

:::{note}
Expand Down Expand Up @@ -65,4 +67,4 @@ This scheme works as Visual Studio is binary compatible (even at object file lev
We now copy `CMakeCache.txt` across, if we later again have different developer and build server versions of visual studio then we will again need to not copy it as it is invalid if the visual studio version number is different (2017 v 2019).

CMake is used in a few third party modules e.g. MySQL, gsl, OpenCV. Compatible binaries for these will always be copied across, so IOCs can be compiled and linked, but if `CMakeCache.txt` is missing a `make` in the top level will rebuild these modules, some of which do take a while.
</details>
</details>
Loading