On 11/20/2013 12:56 AM, Sieghard wrote:
> You got a funny gcc. Mine doesn't do any preprocessing itself, it
> needs to call an external program (named "cpp") for that purpose.
> Where does your gcc come from?
in fact this is seems to be wrong.
Do
cp -dumpecs
and you will see that it's the (arch-depending) C compiler (supposedly
"cpp" = "C plus plus" ), and not the (arch-independent) preprocessor.
Thus I still suggest that the preprocessor is build in the "main
executable" file called gcc ("gcc" = Gnu Compiler Collection").
Thus the preprocessor should be usable with all languages supported by gcc.
-Michael
------------------------------------------------------------------------------
Shape the Mobile Experience: Free Subscription
Software experts and developers: Be at the forefront of tech innovation.
Intel(R) Software Adrenaline delivers strategic insight and game-changing
conversations that shape the rapidly evolving mobile landscape. Sign up now.
http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk
_______________________________________________
mseide-msegui-talk mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
