I am using Xcode's modified gcc, and I notice that sometimes when I include a file that doesn't exist, it just silently skips it. How can I get it to give me a warning?
A:
Sounds like a bug. If so, then fixing it might be the best way.
edit: I forgot, Xcode is not open. Never mind.
Tim Sylvester
2009-07-16 20:34:00
gcc is GPL - if they modified and distributed it the source must be available
anon
2009-07-16 20:39:36
Good point, I guess it's just the IDE that's proprietary? - Are you sure they didn't get around this with the GPL "Linking Exception"? http://developer.apple.com/opensource/tools/xcodetools2.2.html
Tim Sylvester
2009-07-16 20:58:13
The links on the page you linked to that refer to "linking exception" don't work. But in any case, the GPL is very clear, if you distribute modified GPL'd code, you must provide the source to your licensees - no exceptions.
anon
2009-07-16 21:04:19
Xcode's (3.1.3) gcc (4.2) open source is at http://www.opensource.apple.com/source/gcc/gcc-5493/ but I don't think that gcc is the issue here. Until we see what the OP is actually doing this is shooting in the dark.
cdespinosa
2009-07-17 06:40:36
A:
I find it very hard to believe that any version of gcc will not produce an error message if a #include fails, if that is what you are asking about. Have you tried building the code from the command line?
anon
2009-07-16 20:44:08
+1
A:
It is likly that the build system, i.e. the xcode builder isn't re-compiling certain source files and so you don't get an error. It's hard to say why. We use Scons for our cross platform builds.
Spacen Jasset
2009-08-07 10:02:21
A:
That'ŝ normally something that belongs in the configure script. It checks for some headers and chooses the ones best fitted.
Georg
2009-09-26 11:19:19