On Tue, Feb 3, 2009 at 3:02 PM, Stefan Sperling <stsp_at_elego.de> wrote:
> On Tue, Feb 03, 2009 at 03:06:15PM -0600, Hyrum K. Wright wrote:
> > Julian Foad wrote:
> > > Well, isn't the proper solution to use "make" to do this job, instead
> of
> > > a manual step in "autogen"? (This is about re-making a target file from
> > > a source file if it's out of date or doesn't yet exist, which is
> exactly
> > > the purpose of "make".) Is there any reason this step needs to be done
> > > so early in the build process?
> >
> > Not a deal breaker, but gen-make.py will complain if the referenced
> header file
> > doesn't exist. That's why I put this step in autogen.sh before
> gen-make.py is run.
>
> So gen-make.py complains about something that is not a problem?
> If so, making some fix to gen-make.py was not an option?
>
> I'd also think having make sort this stuff out, if at all possible,
> is a better solution. It's more portable.
gen_make.py only complains about a header file being missing if gen_make.py
doesn't know that the file is built by 'make'. Adding the header file to
'private-built-includes' in 'build.conf' should resolve the issue and allow
you to generate the header file normally using make.
Cheers,
David
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1099543
Received on 2009-02-04 02:12:29 CET