-
Notifications
You must be signed in to change notification settings - Fork 2
Deploying a DEBUG build IOC
Wiki > The Backend System > IOCs > Debug Builds
DEBUG DLL builds are kept in EPICS_DEBUG_CLEAN_win7_x64
in the usual kits deployment area. If you wish to deploy only a single IOC in debug mode rather than replace the whole installation with the above debug build then:
- Double-click on the
dllCopy.bat
file in theiocBoot
area of the IOC you want to deploy on kits, this will copy the dependent DLL and pdb files to the {ioc}/bin/windows-x64-debug directory - Backup the
{ioc}/bin/windows-x64
directory on the target computer to be tested. - Copy the EXE and all DLL/pdb files from the
kits/{ioc}/bin/windows-x64-debug
directory to thebin/windows-x64
of the target IOC. - Also copy the files in
kits/EPICS/crtl/windows-x64-debug
to the target{ioc}/bin/windows-x64
directory.
When you start the IOC it should now start the debug build you have copied over.
Note: there is also a EPICS_STATIC_DEBUG_CLEAN_win7_x64 build - this would only require copying the single EXE and pdb file as all DLLs are bundled into the EXE in a static build; however static builds have sometimes behaved differently to DLL builds in the past and so the above DLL option is a better test of the eventual mechanism, though trying a static EXE may be enough for diagnostics. The files here will be in windows-x64-static-debug