Core release, Wed
I'm mostly satisfied with the libraries now, which is to say, I don't really have any time to make any significant changes. So I'll plan on freezing the release this Wednesday. Unless there are any objections. ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: Core release, Wed
On Jul 18, 2005, at 9:59 AM, Nicola Pero wrote: I'm mostly satisfied with the libraries now, which is to say, I don't really have any time to make any significant changes. So I'll plan on freezing the release this Wednesday. Unless there are any objections. The Windows pseudo-framework support needs more polishing ... hopefully I can do some more tomorrow (there are nice patches and suggestions pending -- thanks!). It's probably not a release-critical issue though ? Yes. Do what you can do. I find that things don't really get tested until after I make a release anyway. So it's more than likely I'll have a patch release within a few weeks. ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: Core release, Wed
Adam Fedor wrote: > I'm mostly satisfied with the libraries now, which is to say, I don't > really have any time to make any significant changes. So I'll plan on > freezing the release this Wednesday. Unless there are any objections. > Fine for me. I am still investigating on how best to implement the pattern colours, so this will only go into the release after. Cheers Fred ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: Core release, Wed
> I'm mostly satisfied with the libraries now, which is to say, I don't > really have any time to make any significant changes. So I'll plan on > freezing the release this Wednesday. Unless there are any objections. The Windows pseudo-framework support needs more polishing ... hopefully I can do some more tomorrow (there are nice patches and suggestions pending -- thanks!). It's probably not a release-critical issue though ? Thanks ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: Core release, Wed
Nicola Pero wrote: I'm mostly satisfied with the libraries now, which is to say, I don't really have any time to make any significant changes. So I'll plan on freezing the release this Wednesday. Unless there are any objections. The Windows pseudo-framework support needs more polishing ... hopefully I can do some more tomorrow (there are nice patches and suggestions pending -- thanks!). It's probably not a release-critical issue though ? I also have some windows changes changes to check in. Was planning to do that over the next couple of days. Regards, Sheldon ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: Core release, Wed
On 2005-07-18 15:25:36 +0100 Adam Fedor <[EMAIL PROTECTED]> wrote: I'm mostly satisfied with the libraries now, which is to say, I don't really have any time to make any significant changes. So I'll plan on freezing the release this Wednesday. Unless there are any objections. Well ...I have nothing very concrete but ... I'm dubious about the recent make packagechange to when the objc library is linked into things (the one which seems to have caused problems on bsd). The reason I'm worried is that, on a couple of production machines I wanted to make local bugfix updates to part of my software, and (for no very good reason ... I just like to keep things up to date) I updated the make package on these machines before recompiling my patched code. Upon relinking I got a load of errors about undefined symbols from the runtime library ... but upon reverting to the earlier make package I was able to build without problems. I haven't investigated in any depth ... partly lack of time, partly because I don't want to tinker too much with live production systems running customer-facing services. The linkage problems may well be something wrong in my makefiles which the make system was masking and is not masking any more, but it may be the case that the make package really should link every tool/app with -lobjc evn though it has already linked the base library with it, I'm just not sure - I find the rules about dynamic libraries confusing. ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: Core release, Wed
> > I'm mostly satisfied with the libraries now, which is to say, I don't > > really > > have any time to make any significant changes. So I'll plan on freezing the > > release this Wednesday. Unless there are any objections. > > Well ...I have nothing very concrete but ... I'm dubious about the recent > make packagechange to when the objc library is linked into things (the one > which seems to have caused problems on bsd). > > The reason I'm worried is that, on a couple of production machines I wanted > to make local bugfix updates to part of my software, and (for no very good > reason ... I just like to keep things up to date) I updated the make package > on these machines before recompiling my patched code. Upon relinking I got > a load of errors about undefined symbols from the runtime library ... but > upon reverting to the earlier make package I was able to build without > problems. > > I haven't investigated in any depth ... partly lack of time, partly because > I don't want to tinker too much with live production systems running > customer-facing services. The linkage problems may well be something wrong > in my makefiles which the make system was masking and is not masking any > more, but it may be the case that the make package really should link every > tool/app with -lobjc evn though it has already linked the base library with > it, I'm just not sure - I find the rules about dynamic libraries confusing. Thanks - yes, I had exactly that same problem on my office workstation. :-) I believe the problem is that if you switch to the new -make package, you have to recompile everything from scratch (which I didn't, I reverted to the old gnustep-make as you did). :-( My understanding is that before the change, we linked a tool against -lgnustep-base and -lobjc. gnustep-base itself was not linked against libobjc. After the change, we now link a tool just against -lgnustep-base. gnustep-base itself is now linked to libobjc. So if your gnustep-base was built with the old gnustep-make, but you're using the new gnustep-make to link a tool, libobjc is not linked into gnustep-base (old building style), and will not be linked into the tool (new building style), so you get undefined symbols because libobjc is never linked. Rebuilding only gnustep-base might be enough to fix the problem ... I'd still rebuild everything just to be sure. This makes upgrades a bit cumbersome as you have to upgrade everything, but well that's why we're making a major release I suppose. ;-) Thanks ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: Core release, Wed
Adam, --- Adam Fedor <[EMAIL PROTECTED]> wrote: > I'm mostly satisfied with the libraries now, which is to say, I don't > really have any time to make any significant changes. So I'll plan on > freezing the release this Wednesday. Unless there are any objections. > There is a memory leak in NSWindowController which I'd like to fix before the release. The class should, per specs, release all of the top level objects in the nib/gorm it loads when it is released. It currently doesn't do that. > ___ > Gnustep-dev mailing list > Gnustep-dev@gnu.org > http://lists.gnu.org/mailman/listinfo/gnustep-dev > Later, GJC Gregory John Casamento -- CEO/President Open Logic Corp. (A MD Corp.) ## Maintainer of Gorm (IB Equiv.) for GNUstep. ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: Core release, Wed
On Jul 20, 2005, at 6:14 AM, Nicola Pero wrote: I believe the problem is that if you switch to the new -make package, you have to recompile everything from scratch (which I didn't, I reverted to the old gnustep-make as you did). :-( My understanding is that before the change, we linked a tool against -lgnustep-base and -lobjc. gnustep-base itself was not linked against libobjc. After the change, we now link a tool just against -lgnustep-base. gnustep-base itself is now linked to libobjc. So if your gnustep-base was built with the old gnustep-make, but you're using the new gnustep-make to link a tool, libobjc is not linked into gnustep-base (old building style), and will not be linked into the tool (new building style), so you get undefined symbols because libobjc is never linked. Rebuilding only gnustep-base might be enough to fix the problem ... I'd still rebuild everything just to be sure. This makes upgrades a bit cumbersome as you have to upgrade everything, but well that's why we're making a major release I suppose. ;-) Well, I can revert the make part of the patch. It shouldn't be a problem to have lobjc linked multiple times. ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: Core release, Wed
> > This makes upgrades a bit cumbersome as you have to upgrade everything, > > but well that's why we're making a major release I suppose. ;-) > > > > Well, I can revert the make part of the patch. It shouldn't be a > problem to have lobjc linked multiple times. My personal suggestion would be to leave the change in, but add a clear explanation (that you need to recompile everything) in the release notes. Eg, taking us (Brainstorm/Opera Telecom) as an example, ordinately rebuilding all software on our live systems when we do our next upgrade should not be too much of a problem ... the important thing is that we know we have to do it! :-) I'm happy with any other solution (including reverting the make part of the patch), I don't think it is particularly important -- the most important thing is having a clear understanding of what is needed to upgrade without problems, and communicating it to users. Thanks ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: Core release, Wed
On Jul 21, 2005, at 4:31 PM, Fred Kiefer wrote: Are you making a release of GUI and back as well? In the last few days I did get the basic cairo backend working again on the changed cairo code. If the back release isn't due in the next few days I'll add that code to CVS, if it's going out soon, I'll wait til after that. Greg asked me to hold Gui until he checks some things. I don't know how long that will be. ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: Core release, Wed
Adam Fedor wrote: > I'm mostly satisfied with the libraries now, which is to say, I don't > really have any time to make any significant changes. So I'll plan on > freezing the release this Wednesday. Unless there are any objections. > Are you making a release of GUI and back as well? In the last few days I did get the basic cairo backend working again on the changed cairo code. If the back release isn't due in the next few days I'll add that code to CVS, if it's going out soon, I'll wait til after that. Fred ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: Core release, Wed
All, --- Adam Fedor <[EMAIL PROTECTED]> wrote: > > On Jul 21, 2005, at 4:31 PM, Fred Kiefer wrote: > > Are you making a release of GUI and back as well? In the last few days > > I > > did get the basic cairo backend working again on the changed cairo > > code. > > If the back release isn't due in the next few days I'll add that code > > to > > CVS, if it's going out soon, I'll wait til after that. > > > Greg asked me to hold Gui until he checks some things. I don't know how > long that will be. I'm done. I needed to check a change I made to GSWindowTemplate for custom window classes. My tests indicate it's working properly. Please go ahead with the release. Sorry for the delay, but I was at work a little late today. :) Thanks, GJC Gregory John Casamento -- CEO/President Open Logic Corp. (A MD Corp.) ## Maintainer of Gorm (IB Equiv.) for GNUstep. ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
