scons

I've got a project built with SCons and I'm trying to use the Clang Static Analyzer to analyze the code. However, when running scan-build scons SCons seems to ignore the settings introduced by scan-build . How can I make this work? The way scan-build works is it sets up various environment variables that are usually used by build systems (such as make ) to control how the build happens. Some of these are: CC - name of program to use as C compiler CXX - name of program to use as C++ compiler CCC_* - various environment variables that control the behaviour of Clang's static analyzer SCons

I'm trying to build the C++ port of zxing on Windows, but scons fails with: cl : Command line error D8021 : invalid numeric argument '/Wextra' I have both VS2010 and MinGW installed, and scons tries to use the MSVC compiler, even though the SConscript file assumes gcc and use gcc-specific parameters, which causes the error. How can I tell scons to use MinGW instead? Torsten Scons uses MSVC compiler by default on windows. To set mignw compiler use tools parameter while creating Environment object. env = Environment(tools = ['mingw']) Below is my working SConstruct for mingw on Windows: import

I've been trying to get scons to output exe, obj, lib and dll files to a specific build directory. My file structure looks like this: /projectdir /build /bin /obj /source /subdirs /.. SConstruct Basically, what I get now is my source directory is getting polluted with obj files. I'd rather have it all in one place. The SConstruct file looks like this: env.VariantDir('build', 'source', duplicate = 0) env.Program('Hierarchy', source = ['source/sconstest.cpp', 'source/utils/IntUtil.cpp']) The easiest way I've found is to use 2 files, a SConstruct file and a separate SConscript. In the SConstruct

What are the differences between Autotools, Cmake and Scons? Svartalf In truth, Autotools' only real 'saving grace' is that it is what all the GNU projects are largely using. Issues with Autotools: Truly ARCANE m4 macro syntax combined with verbose, twisted shell scripting for tests for "compatibility", etc. If you're not paying attention, you will mess up cross-compilation ability (It should clearly be noted that Nokia came up with Scratchbox/Scratchbox2 to side-step highly broken Autotools build setups for Maemo/Meego.) If you, for any reason, have fixed, static paths in your tests, you're

I am currently setting up SCons for cross-compilation with Windows as the host OS. I am building a custom Environment for the cross-compiler, but SCons insists on looking for Visual Studio each time I start it up (and prints a warning that it cannot find it, because I don't have it installed). Can I prevent it from looking for standard tools I know I am not going to use? Brady There are at least 2 ways to do this, the first way is the easiest, try creating the environment specifying the compiler, as follows: env = Environment(CC = '/path/to/the/compiler') You'll probably need to add paths for