[KDE-Darwin] Re: RFC on Makefile.am fixes for (non-portable) linking against libtool modules in KDE
ranger at befunk.com
Thu Mar 6 15:04:00 GMT 2003
Lubos Lunak wrote:
> On Thursday 06 of March 2003 15:45, Michael Matz wrote:
>>On Thu, 6 Mar 2003, Benjamin Reed wrote:
>>>>That might not be for a couple weeks though since I have tons of work
>>>>and travel next week.
> Actually, yesterday I tried to write am_edit/automake support for kdeinit
> modules too.
>>>Yeah, I started looking into it a bit last night and I think it will
>>>basically be impossible (or impractical) to implement in am_edit.
>>>am_edit edit's the .in files (strangely enough), and by the time you
>>>have those it's too late.
>>What makes you think that?
>>>I'm going to try to find some docs on adding keywords to automake (if
>>>it's even possible) and then I guess we'll go from there.
>>Ehh no. You don't want to do this in automake. am_edit is perfectly
>>capable to do the rewriting you want.
> And how exactly should the Makefile.am look for am_edit to work?
> I first thought about simply having the app written normally without all that
> LTLIBRARIES stuff, only with some flag marking it as kdeinit module, and I
> thought am_edit could do the rest. Very simple to find out this doesn't work.
> If automake doesn't see any LTLIBRARIES stuff in Makefile.am, it won't
> generate rules for building libraries -> myapp.la building will fail.
Exactly, the output of this transform has to become the input of
automake (the .am), not the result of it, or else the separate libraries
will never get generated.
More information about the kde-core-devel