Mailing-List: contact stdcxx-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: stdcxx-dev@incubator.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <44202AB9.1070605@roguewave.com>
Date: Tue, 21 Mar 2006 09:32:57 -0700
From: Liviu Nicoara <nicoara@roguewave.com>
User-Agent: Thunderbird 1.5 (X11/20051201)
MIME-Version: 1.0
To: stdcxx-dev@incubator.apache.org
Subject: Re: VACPP 8.0 builds with custom compiler cfg file
References: <20060312000514.64778.qmail@minotaur.apache.org>
 <441F275F.9000603@roguewave.com> <441F2921.9080202@roguewave.com>
 <441F2ADB.2070006@roguewave.com> <441F2B38.3030004@roguewave.com>
 <441F372F.2090505@roguewave.com> <441F3DA7.3020601@roguewave.com>
In-Reply-To: <441F3DA7.3020601@roguewave.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Martin Sebor wrote:
>> Liviu Nicoara wrote:
>> A cursory look at toplevel GNUMakefile shows that CXXOPTS, CPPOPTS and
>> LDOPTS values are not saved in makefile.in. The easiest fix would be to
>> append their values to the corresponding ~FLAGS variables. I have not
>> tested it and I am not aware of any adverse effects.
>>
>> What do you think?
> 
> I'm not sure. This is what we used to do but I changed it because
> they get appended in makefile.common adding them to CXXFLAGS in
> makefile.in will end up duplicated. I'll have to think about how
> to do what you want w/o duplicating the options.

The reason I believe we should address this and avoid manual
modification of makefile.in is that all invocations of the compiler
before makefile.in is created are failing with consequences like
choosing the wrong build model (tempinc vs template registry).

Liviu