makefiles and CVS

[Joel Sherrill]

Salman wrote:
> 
> On Fri, 2003-01-24 at 14:25, Joel Sherrill wrote:
> > Ralf Corsepius wrote:
> > >
> > > On Fri, 2003-01-24 at 14:01, Salman wrote:
> > > > Hey guys,
> > > >
> > > > I have a package here, which has its own makefile, and provides a single
> > > > object file, which should be loaded as module into the linux kernel.
> > > >
> > > > Now, i've modified the code to load into rtems, and it should be placed
> > > > in /libbsp/i386/pc386 directory. but i'm confused regarding Makefiles.
> > > >
> > > > RTEMS doc, states Makefile.in are the only makefiles required and the
> > > > configure script generates other makefiles from this. Can anyone suggest
> > > > how can I go about extracting Makefile.in files out of exisitng
> > > > Makefiles?
> > > No way. You need to manually write a Makefile.in or better (much easier)
> > > write a Makefile.am.
> >
> > Sounds like some piece of documentation needs to be updated to reflect
> > the
> > use of automake now.  Hopefully Salman can point us to the broken
> > documentation.
> >
> 
> /ftp/pub/rtems/cd-working/rtems-doc-20021016/share/rtems/pdf/bsp_howto.pdf, section 3.1, there's no mention of Makefile.am and it mostly implies that Makefile.in is the key to all Makefiles and has to be provided by the user.

Thanks.  FWIW the source for these is in every snapshot:

doc/bsp_howto/makefiles.t  (leaf directory Makefile description)
doc/bsp_howto/support.t    (libbsp/CPU/XXX/Makefile* description)

Anyone should feel free to fix documentation problems and submit
patches.

> > Now this is the auto generated chain:
> >
> > Makefile.am
> >   - automake produces Makefile.in
> >   - configure produces Makefile
> > configure.ac
> >   - auto??? produces configure.in
> >   - autoconf produces configure
> >
> > Notice that I don't even remember offhand the complete magic.  I rely
> > on bootstrap also.
> >
> > So Ralf is pointing you in the right direction, write a Makefile.am and
> > use bootstrap.  I can't believe that it wouldn't be easier to adapt an
> > existing RTEMS Makefile.am to compile the pieces you want than to
> > attempt
> > to bring a Linux Makefile in.  Ultimately, all you want to do is compile
> > a few files with possibly some macros defined.
> >
> > > Alternatively you can try to modify the linux-Makefile to to fit into
> > > RTEMS source-tree. Something I would strongly discourage you from,
> > > because IMNSHO, the Linux' kernel Makefiles are not really worth looking
> > > into, to put it politely ;)]
> > >
> > > > I am now starting to modify rtems code as well, and would like to do
> > > > this with aid of CVS, but when importing source files, it neglects
> > > > Makefiles and configure scripts, has anyone experienced this problem
> > > > before?
> > > .
> > > http://www.oarcorp.com/rtemsdoc-current/html/FAQ/FAQ00052.html
> > >
> > > Ralf

-- 
Joel Sherrill, Ph.D.             Director of Research & Development
joel at OARcorp.com                 On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
Support Available                (256) 722-9985