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?
相关问题
- Cross compiling Qt 5
- scons executable + shared library in project direc
- How to set duplicate=0 for all SCons build variant
- Cross compiling Gnu Radio for Openwrt
- How can I measure the build time for each componen
相关文章
- Raspberry Pi crosscompile on Ubuntu 13.10 “libstdc
- CMake CMAKE_AUTOMOC in cross compilation
- Building native library with standalone toolchain
- How to configure a particular GCC cross toolchain
- Is that possible to run a python built program on
- How to tell scons to use the C++11 standard
- Cross-Compiling for an embedded ARM-based Linux sy
- cross compiling of openssl for linux arm-v5te-linu
You may suppress warnings like this
For example, to cross-compile for ARM Cortex-M microcontrollers I'm doing this
There are at least 2 ways to do this, the first way is the easiest, try creating the environment specifying the compiler, as follows:
You'll probably need to add paths for the linker and other tools as well. Then SCons shouldnt search for them.
Another way to do it would be to create a tool definition for the cross-compiler using the
tools
argument on theEnvironment()
function as mentioned in the CONFIGURATION FILE REFERENCE section of the SCons man page, where the following is mentioned:tools/my_tool.py:
SConstruct: