[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: file-specific optimization options?
From: |
Nicola Pero |
Subject: |
Re: file-specific optimization options? |
Date: |
Tue, 6 Nov 2001 05:48:45 +0000 (GMT) |
> Nicola Pero wrote:
>
> >
> > (ii): gnustep-make does not support file-specific CC options ... hmmm ...
>
> Actually, gnustep-base has a similar hack in Source/Makefile.postamble,
> just set up a specific rule for compiling that file:
Ok - very convincing example ... in attach a diff on current rules.make
with implemented support for adding file-specific compiler flags and
specifying file-specific filter-out patterns for compiler flags ... with
these changes, the base library (and Stephen as well) can remove their
hacks, and simply do -
mframe.m_FILE_FILTER_OUT_FLAGS = -O%
NSConnection.m_FILE_FILTER_OUT_FLAGS = -O%
NSInvocation.m_FILE_FILTER_OUT_FLAGS = -O%
to disable optimization flags for those specific files ... now the only
point is ... is it ok to apply to gnustep-make considering that it is in
prerelease state ?
it shouldn't break too much I think, but I didn't really test it
extensively.
it's quite nice that we are implementing this kind of stuff ... pretty
advanced features ... not sure other make packages have them.
rules.make.diff
Description: Text document
- Re: file-specific optimization options?,
Nicola Pero <=