Le 1 mai 07 à 09:02, Yen-Ju Chen a écrit : > On 4/30/07, Quentin Mathé <[EMAIL PROTECTED]> wrote: >> Le 30 avr. 07 à 23:27, Yen-Ju Chen a écrit : >> >>> On 4/30/07, Quentin Mathé <[EMAIL PROTECTED]> wrote: >>>> Author: qmathe >>>> Date: Mon Apr 30 22:36:47 2007 >>>> New Revision: 1802 >>>> >>>> URL: http://svn.gna.org/viewcvs/etoile?rev=1802&view=rev >>>> Log: >>>> Fixed XWindowServerKit compilation with gnustep-make version older >>>> than 2.0 (see bug #8806 for more explanation) >>> >>> This fix actually breaks the XWindowServerKit with gnustep-make 2.0. >>> In order to reduce the troubles, >>> I really suggest people to use gnustep-make 2.0. >> >> I will try to take a look at it today. Does PopplerKit compiles with >> gnustep-make 2.0? I used exactly the same trick to fix it few >> weeks ago. > > I found that I can fix it by putting an aggregate.make in front of > etoile.make even though there is no subproject in XWindowServerKit.
Ok. Ugly but great hack :-) > I think you may want to revise etoile.make since gnustep-make 2.0 > automatically create symbolic link to expose libraries and headers. > Some of the function of etoile.make may be redundant with gnustep- > make 2.0. > > In short, etoile.make was designed to solve the dependencies issues. > If the issues do not exist in gnustep-make 2.0, > then there is no need of etoile.make > I doubt that is the case, but I think there are some redundancy > between etoile.make and gnupste-make 2.0. > It is just my wild guess. etoile.make is mainly here to allow a full repository build when nothing is already installed or the install isn't up-to-date. It is also provides few other features like UnitKit linking by passing 'test=yes', headers searching in some standard locations like Headers directory etc. For example, if XWindowServerKit isn't installed and you remove etoile.make. Then trying to compile Azalea will lead to an error because gnustep-make cannot resolve the dependency. etoile.make just takes care to avoid this by exporting each dependency once built in Build directory. gnustep-make doesn't provide that sort of features (version 2.0 or previous). The problem is gnustep-make tends to quite sensitive to the order in which make rules are included… that's why we encounter such bug. Cheers, Quentin. _______________________________________________ Etoile-discuss mailing list [email protected] https://mail.gna.org/listinfo/etoile-discuss
