Oliver Braun wrote: > Mathias Bauer wrote: >> Oliver Braun wrote: >>> What are the reasons (again) why shared libraries and dlls aren't directly >>> created in solver instead of the modules local output tree ? >> >> I assume mainly the fact that Hamburg developers don't have write access >> to solver when building non-locally. ;-) > > For CWS's they usually do have write access. Yes, but you didn't ask for a *good* reason, you asked for *the* reason(s) and the whole "build in local tree and deliver" stuff is much older than the CWSs. :-)
> I could also live with making > $(SLB) depend on some environment variable, so that building to solver is off > by > default: the build system is a much more appropriate place for this than the > product code. > >> Besides I think it's just because nobody asked for it and now it's quite >> some work to change the build system in a way that "deliver" is >> incorporated into it (there's more than just dlls to build). > > I don't think we need to drop "deliver" to make this work. We probably do not > even have to touch any d.lst. You misunderstood me. I meant that what currently is done in "deliver" needs to be done in the build step if you omit the "delivery". Of course if you only wanted to change the process for dlls that would be trivial. But why not get rid of the local output for all "delivered" files... Ciao, Mathias -- Mathias Bauer (mba) - Project Lead OpenOffice.org Writer OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't reply to "[EMAIL PROTECTED]". I use it for the OOo lists and only rarely read other mails sent to it. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
