[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    RE: Questions about Makefile.am
From:       Jesper Pedersen <jep () systematic ! dk>
Date:       2000-04-03 10:52:22
[Download RAW message or body]

Hi Stephan.

> -----Original Message-----
> From: Stephan Kulow [mailto:coolo@kde.org]
> Sent: 3. april 2000 12:48
> To: kde-devel@kde.org
> Subject: Re: Questions about Makefile.am
> 
> 
> Jesper Pedersen wrote:
> > 
> > > -----Original Message-----
> > > From: David Faure [mailto:david@mandrakesoft.com]
> > > Sent: 3. april 2000 11:32
> > > To: kde-devel@kde.org
> > > Subject: Re: Questions about Makefile.am
> > >
> > >
> > > On Mon, Apr 03, 2000 at 11:17:04AM +0200, Jesper Pedersen wrote:
> > > > Hi.
> > > >
> > > > I have 2 questions about Makefile.am:
> > > >
> > > > 1) I have a program which lie outside the KDE source 
> directories,
> > > > but I would like to use:
> > > >
> > > >  libMyProgramLib_la_METASOURCES = AUTO
> > > Tip: METASOURCES = AUTO is even better
> > >
> > Ok. I'll use that instead.
> > 
> > > > in my Makefile.am files to generate the moc-files.
> > > > How do I easily do this without moving my program ?
> > >
> > > That's the job of am_edit (automoc for KDE-1.x).
> > 
> > It's a KDE-2 program, so I look forward to the freeze later today :)
> > 
> > > Since you seem to use autoconf/automake alread,
> > > all you need to do is to call "perl admin/am_edit" between
> > > autoconf and automake.
> > >
> > 
> > So the cleanest way is to include KDE's am_edit in the 
> program directory
> > and do:
> > 
> >  aclocal
> >  autoconf
> >  perl kdefiles/am_edit
> >  automake
> > 
> > in my Makefile.cvs ?
> > 
> Definitly not. you have to call autoheader before automake and am_edit
> after
> automake. There is Makefile.common which does most for you - 
> if you use
> the
> whole admin dir, there is even a configure.in.min you can use by just
> putting
> an almost empty configure.in.in in your toplevel dir.
> 

I'll have a look at the KDE admin/ dir, when I come home and maybe
copy the whole directory to my source directory and use this instead.

> Greetings, Stephan
> 
> -- 
> It said Windows 95 or better, so in theory Linux should run it
>                                                 GeorgeH on /.
> 
> 

[prev in list] [next in list] [prev in thread] [next in thread]