[aspectc-user] Setting header paths

[Olaf Spinczyk]

Hi,

just a short remark:

The parser configuration file is not only about include paths. It also 
contains the list of pre-defined macros of your compiler. These macros 
are necessary for correct parsing of the system or library header files.

Best regards,

Olaf

Gordon Schumacher wrote:
> Is it possible to deploy an application that uses Puma without shipping
> along a puma.cfg, assuming that you have some method to figure out what
> the normal include paths are and such?
>
> I'm using something like this (assume that the defaultIncludePaths()
> function is indeed correctly fetching my compiler's paths):
>
>       std::list<std::string>  includePaths = defaultIncludePaths();
>       Puma::ErrorStream       err;
>       Puma::CProject          project(err);
>       Puma::Config            config(err);
>       for (std::list<std::string>::const_iterator str =
> includePaths.begin(); str != includePaths.end(); ++str)
>          config.Add("-I", str->c_str());
>       project.configure(config);
>
> ...but when I do this on a different computer (with a different
> compiler), it doesn't quite seem to matter what I pass along to the Add
> function (space or no space after -I, -I and path as separate
> parameters, etc. etc.) it still tells me that there is no path
> containing my compiler's header files.
>
> If I run it under MinGW on the system I used to build Puma, it seems to
> do better.
> _______________________________________________
> aspectc-user mailing list
> aspectc-user at aspectc.org
> http://www.aspectc.org/mailman/listinfo/aspectc-user
>
>