Re: [Chicken-users] CMake tarballs

[Brandon J. Van Every]

felix winkelmann wrote:
> On 7/31/06, Brandon J. Van Every <address@hidden> wrote:
> > >
> > > Next question: can the CMake build omit the "boot" and create the
> > > .c files in the toplevel directory?
> > > (I know you won't like it, but is it possible?)
> >
> > The CMake build does have to remain two-stage, so "omit" is the wrong
> > word here.  I can change the directory structure so that the boot stuff
> > gets done in the main directory, and the final output gets done in a
> > /stagetwo directory.  This would allow ./configure to avoid messing with
> > any directory structure issues.
> >
> > *.c vs. *.c.in is still an issue though.  What I'd like ./configure to
> > do, is distribute *.c.in files, and copy them at configure time to .c
> > files.  That keeps in-directory and out-of-directory builds from getting
> > clobbered.  How doable is this from your perspective?
>
>
> Hm. I think I rather modify the autotools build to use "boot"...
> Would that be ok?

Of course!  Less work for me.  :-)  But to sanity check your motives, 
the *.c.in stuff is still necessary in /boot.  *.c.in is how I keep 
distro files from colliding with built files.


Cheers,
Brandon Van Every