Book a Demo

Author Topic: C++ Include Paths - Pt 2  (Read 2121 times)

asahukar

  • EA Novice
  • *
  • Posts: 1
  • Karma: +0/-0
  • Go Green!
    • View Profile
C++ Include Paths - Pt 2
« on: October 13, 2006, 06:43:04 am »
Hello,

I am having a problem with definitions being read from included headers.

I searched this forum and found & read the post "C++ include paths" from June of this year.  

We are a multi-platform shop and specify compile-time include paths as part of the makefile/DevStudio project definitions.  

How do I specify such paths to EA so that the reverse engineering process does not fail due to 'expected symbol <symbol>' errors?

Please note, Local Paths don't make any sense in my context because they are not, in generally applicable to any given build setting.


Thank in advance for the help,
- AJ Sahukar

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8110
  • Karma: +119/-20
    • View Profile
Re: C++ Include Paths - Pt 2
« Reply #1 on: October 15, 2006, 03:09:32 pm »
It sounds like you're not so much needing include paths specified, but needing to specify macros.  Even if EA found the definitions of the macros used, it doesn't evaluate them.  You need to define the macro in EA (Settings | Preprocessor macros) so that EA knows how to skip over it.

See http://sparxsystems.com.au/EAUserGuide/index.html?languagemacros.htm