That means that if you type a scons command with command-line options, then later without those command line options, the options from the first run will still be there, because they will have been saved in the cache.Ī major fiddle with SCons, especially on Windows, is ensuring that all the required programs are present in your path. On top of that, you should also be aware that the SCons build will cache your build options in a file called options.cache. So, if you want to set configuration options so that they always get applied, edit your config.py file. WITH_LOCAL_HELP = /usr/local/share/ascend/manualĭEFAULT_ASCENDLIBRARY = /usr/local/share/ascend/models For example, you might create a config.py file like this: For instance, type scons WITH_LOCAL_HELP = /usr/local/share/ascend/manual.Īny build option that you see in scons -Qh can be entered into a file config.py that you can create in the root source directory (ie ~/src/ascend/trunk). To include any building options, type scons followed by options. To clean up after your build, type scons -c. Get info on the current build options by typing scons -Qh. 3.2 32-bit executable for 64-bit or 32-bit Windows, using MinGW/MSYSīuilding with SCons (as of Jun 2010, we recommend version 1.x) should be as simple as typing.3.1 64-bit executable for 64-bit Windows, using MinGW-w64/MSYS.
