-
Notifications
You must be signed in to change notification settings - Fork 17
Package Building on Windows
Thomas Beale edited this page Mar 14, 2016
·
6 revisions
Below are instructions for how to set up a full package-building environment for Windows.
Using the following method, you can do a batch build of one or more apps, and also build the installer package. To do this, you need to install a few things:
- Python: There are various ways to do this; I install things like Python under cygwin, but you can just do a normal windows install as well.
- SCons builder (make replacement): SCons
- NSIS (Windows .msi/.exe installer builder): NSIS
To build just the adl_workbench application...
-
start a command shell window in the .../openEHR directory
-
type
scons downloads/windows/adl_workbench
This assumes SCons, Python and NSIS are in your path. If not, you could use a script like the following in the .../openEHR directory:
set path=%path%;c:\cygwin\bin;c:\program files\nsis
set PLATFORM=win32
scons ..\downloads\windows\adl_workbench
If everything went well, there should be a new .exe package installer at ...\openehr\downloads\windows\adl_workbench\ADLWorkbenchInstall.exe
The build scripts are as follows:
-
.../openEHR/adl-tools/SConstruct
- the master SCons build script. This builds apps in a standard way on all platform, then decides based on which platform it is running on, which package installer to invoke. - Windows package installer (NSIS) script is at
...\openEHR\adl-tools\apps\adl_workbench\install\windows\ADL_Workbench
- OSX installer is created as an archive of a directory structure at
...\openEHR\adl-tools\apps\adl_workbench\install\mac_osx