Re: [autotools-idl] IDL include paths

[Milo H. F. <mf...@pa...>]

Thx Vlado -- I got off on the wrong foot using IDLCXXFLAGS

v/r
milo

>-----Original Message-----
>From: Vladimir Panov [mailto:gb...@vo...]
>Sent: Tuesday, April 08, 2014 16:20
>To: Milo H. Fields
>Cc: aut...@li...
>Subject: Re: [autotools-idl] IDL include paths
>
>Hi, Milo.
>
>It is just like for C/C++, only the variable is named IDLCPPFLAGS instead of
>CPPFLAGS. I.e. here are the rules:
>
>1. Put your (the maintainer's) additions in AM_IDLCPPFLAGS. If you need it
>global then just do it in every Makefile.am with the same substituted value
>from configure.ac.
>2. Your user will put his global additions in IDLCPPGLAGS. A help message is
>available in "configure --help" about this.
>
>It is possible to add your global additions in IDLCPPFLAGS in configure.ac
>instead of in all Makefile.am's. In configure.ac use the
>following:
>IDLCPPFLAGS="${IDLCPPFLAGS} ..."
>Make sure to append but not to substitute or you will overwrite your user's
>additions.
>
>I personally prefer the rule:
>AM_IDLCPPFLAGS is for the maintainer.
>IDLCPPFLAGS is for the user.
>
>Vlado
>
>
>Milo H. Fields wrote:
>> Greetings, Vlado!
>> Could you tell me the 'recommended' method for extending the IDL
>> search path for the IDL complier - for both a configure.ac system wide
>> and local Makefile.am?
>>
>> v/r
>> Milo
>>
>>
>>
>> ----------------------------------------------------------------------
>> --------
>> Put Bad Developers to Shame
>> Dominate Development with Jenkins Continuous Integration Continuously
>> Automate Build, Test & Deployment Start a new project now. Try Jenkins
>> in the cloud.
>> http://p.sf.net/sfu/13600_Cloudbees
>>
>>
>>
>> _______________________________________________
>> autotools-idl-general mailing list
>> aut...@li...
>> https://lists.sourceforge.net/lists/listinfo/autotools-idl-general
>>