On 4/29/07, Quentin Mathé <[EMAIL PROTECTED]> wrote: > Le 28 avr. 07 à 04:06, Yen-Ju Chen a écrit : > > > Since gnustep-make 2.0 have better frameworks support, > > I think we can convert most of libraries into frameworks. > > The advantage of framework is that frameworks can have resources while > > libraries need GNUstep additions for resources. > > And resources are essential for better localization (gorm and > > localizable string). > > GNUstep-make will automatically install frameworks as libraries with > > symbolic links. > > There is no need to change GNUmakefile of applications. > > But since some of the components were installed as libraries, > > you may need to remove them in order to install new version as > > frameworks. > > I will delay syncing -stable with -trunk until the conversion is done, > > probably over this weekend and one-by-one. > > I'm not sure it's reasonable to do it when we have no resources to > bundle yet. May be better wait until gnustep-make 2.0 has been more > widely distributed and tested. I'm not yet using gnustep-make 2 > personally :-) > With XWindowServerKit, I encounter now the same issue we had with > Addresses and PopplerKit… you should change GNUmakefile in the same > way I did for PopplerKit and Addresses to fix it and apply this > change to all libraries you turn into frameworks. I don't remember > the bug report number but this should be easy to find.
Well, I figure if we are going to do it, it is better to do it once to ease the pain. One side effect of framework is that it tries to create symbolic link to Library/Headers and Library/Libraries. If you have old libraries installed, the creation of symbolic link will fail. So it will fail on 'make install', not 'make; make' as the bug report. I do test the bug regarding conflict between etoile.make and gnustep-make. Are you sure you met the same bug, just it is just a failure of symbolic creation ? In any case, we will need to match GNUstep's stable release. So I would suggest you to upgrade to gnustep-make. There is no problem with gnustep-make as far as I can tell. And we can avoid all the problems of supporting different releases of GNUstep. As long as we stick with stable release of GNUstep, it should be fine for users and packagers. I only update some libraries and see whether it causes problems. So let me know if you still have the same problem with gnustep-make. Remember to remove your old libraries to avoid conflict. Any framework which has messages for users will need to be localized. Therefore, almost every frameworks we have need to be frameworks, not libraries. That is the basic reason behind the conversion. And I believe it is better to do it as early as possible when our user base is still small. Yen-Ju > > Cheers, > Quentin. > > > _______________________________________________ > Etoile-discuss mailing list > [email protected] > https://mail.gna.org/listinfo/etoile-discuss > _______________________________________________ Etoile-discuss mailing list [email protected] https://mail.gna.org/listinfo/etoile-discuss
