Download Scons For Windows EXCLUSIVE
Mufid Bonnet
Hi, I tried once to install scons and I did after hours of digging in internet.Now I had to update python to 2.7.4 version (was 2.4.3) and I 'm in the same situation like before:The documentation about here _for_windows.html#setting-up-scons
People are forced to waste hours each time happen to make some adjustments? Can someone add in documentation this link: -user.html#idm139933257250608and a basic example/user-case how and where use this command line: "python setup.py install --standard-lib" That for my understanding is the only option to make scons work ?And some suggestions how to modify scons.bat in case someone have more than one version installed in windows - in my computer I have 19 "python.exe" installed... :smiley: - ? "where" is a good utility to understand which python.exe is called first ( -a-file-on-the-path)
I was stucked by that too, -to-make-scons-work-on-windows#latest I missed the kind answer back then, but you can try that.Now I'm on Linux and Scons is installed through the Synaptic software. The switch to Linux was difficult, I admit, but now I'm happy.
To test if this worked, you can use git bash (if you already have this open, close it and restart it). Open your start menu, find "Git bash" somewhere there, probably in the git folder. Run it, it will display a shell. Type cc and press enter, it should say something like "cc.exe: fatal error: no input files, compilation terminated." That is alright, it means that it finds the compiler and everything works correctly. If instead you get "cc: command not found", then you did something wrong and it wasn't properly added to path. Check it again and make sure you typed it exactly.
Now type python -h, if you see "python: command not found", it can't find python, you probably didn't add it to path correctly, so check again. If it worked correctly, it will print a large amount of help text and exit.
Lastly, to check if SCons is in path, type scons.py, it should say "scons: *** No SConstruct file found", that's alright, since we don't even have the source at this point. If it says "scons.py: command not found", it means you've probably done something wrong in path setup.
Now to compile, run scons.py. It should check for libraries, then should start compiling (if anything fails, check config.log in the folder and post to pastebin.com if you need help figuring out what it means). Depending on your computer it will take from a few, to a few dozen minutes.If your compilation succeeds, the exe will be placed in the build/ folder, so go run it and hope it works. If it does, you can now start modding tpt.
P.S. If you have a multicore processor, and installed the pywin32 extensions earlier, use scons.py -j#, replacing # with the number of cores you have, ex. -j4 for 4 cores. This will make it compile with all the cores, making it go much faster.
P.P.S. You can append compiler options to change how TPT builds. For instance --no-sse makes a legacy version, --debugging allows you to debug with gdb, and --64bit allows you to create a 64 bit executable (if you install MinGW-W64 from here [1]).
List of all sconscript flags you can use
By default scons hashes and processes every file in the tree before performing a build. On a large tree (e.g. rosetta) and filesystem with high io latency (e.g. a NFS or GPFS filesystem) this causes ridiculously slow build times. In order to improve build times disable file hashing and allow caching of build dependency metadata. Add the follow lines to the project's root SConscript file:
The Xcode build and clean commands tell scons to take the appropriate actions. Xcode will by default instruct scons to use 2 processors for compilation. To change that number, double click the "Rosetta" icon in the "Groups & Files" pane. Then switch to the "Build" tab and change the "NUM_PROCESSORS" setting to the desired number of processors.
The make_project.py and cmake commands should be run whenever files are added or removed from the rosetta_source/src/*.src.settings files. The -j8 flag for cmake has the same interpretation as the -j8 flag for scons . The command cmake . generates a "makefile", which means that alternate programs such as distcc can be used for building Rosetta 3. (The ninja_build.py script in rosetta_source automatex the combined cmake/ninja process and responds to build abbreviations like 'r' for 'release'.)
At the commandline, execute g++ --version and clang --version. If one of them works, you can try specifying that compiler explicitly on the scons commandline with either cxx=gcc or cxx=clang. (This is a label, rather than the compiler command, so it cannot take arbitrary input.)
The MPI-mode build test simply tries to compile Rosetta with the -extras=mpi flag passed to scons. Selective failure of this build means that code surrounded by #ifdef USEMPI ... #endif lines has errors in it.
The proposed SConstruct file from the last example runs well under Linux for scons v0.98, however the last lines fail on Mac OS X. We will simply remove them, since they are not needed under Linux either if you are not building and linking against you own software library (which is probably the case for more than 90% of the projects out there).
Wx-Config enables cross-platform building with relative ease. There are some caveats though with different operating systems and versions of wxWidgets. The following SCons python module was tested for MSVC on windows and gcc on Linux and MacOSX and wxWidgets versions 2.4 and 2.6.
I just (incorrectly) thought it was ok with with 3.8/3.10 as it seemed to be working for me.
but appears my earlier assumptions that scons was going to die were correct!
all the more reason to move it to the later scons
On a 64 bit Windows, you can run any of above prompts and compilers(cl.exe executables) because 64 bit windows can run any 32 bitapplication. 32 bit Windows can not run 64 bit executables, so theVisual Studio installer will not even install shortcuts for some ofthese prompts.
If all goes well, the resulting binary executable will be placed inC:\godot\bin\ with the name of godot.windows.tools.32.exe orgodot.windows.tools.64.exe. SCons will automatically detect whatcompiler architecture the environment (the prompt) is setup for and willbuild a corresponding executable.
SCons runs the SConstruct file in the configuration directory of the platform from which you run the scons command. SConstruct file is the entry point for building the application and contains the information about the Kanzi Engine location and runs these files:
// Builds the application with the default settings as specified// in config.py and SConstruct configuration files.scons// Builds the debug version of the application with// the OpenGL graphics library.scons GL debug// Builds the debug version of the application with the// OpenGL ES 2.0 graphics library from the Kanzi Studio// project named MyProject.scons ES2 debug MyProject
df19127ead