|
On 7/19/2012 8:14 PM, Jay Carlson wrote:
It can't do that when cross-compiling. However, run-time behavior comes up less often than you'd think. The presence of an #include or #define is a feature of the cross-compiler, not the target. This can be tested at compile time: does "mipsel-linux-gcc -c foo.c" succeed and produce a foo.o? The presence of a symbol, or which library is needed for a symbol, can be tested at link time.
Thanks Jay! That was good explanation, after all lots of platform specific magic might be found at the preprocessor, or testing for expected/unexpected compiler errors, so no need to actually run it on the device.