Dear Tamas, > I need to know which compiler directives are set. Can be they dumped during > the compilation process? I'd like to check if __18F25J50 is in the list.
You should be able to use 'sdcc -Wp,-dM [more options] source.c' to obtain a list of defined preprocessor makros (inherited from GNU CPP, see info gcc) -- actually, that does not work: the preprocessor bails out with 'ISO forbids empty source file' -- there is probably some empty argument passed along, not sure. As a workaround, you can call 'sdcc -V [more options] source.c' to see how the preprocessor is invoked, copy that and add -dM to its arguments. Alternatively you believe me that the desired makro is not defined (sdcc does not generate it, the included header file (if any) apparently does not define it, so where would it come from?), but you can easily add -D__18F25J50 to the sdcc command line to achieve the desired effect. You may also want to add --use-non-free to gain access to the device headers and libraries ... Raphael ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ Sdcc-user mailing list Sdcc-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sdcc-user
