On Tue, Aug 30, 2011 at 10:43 AM, Francois Tigeot <ftig...@wolfpond.org> wrote: > On Tue, Aug 30, 2011 at 10:06:57AM -0500, Norbert Thiebaud wrote: >> On Tue, Aug 30, 2011 at 1:35 AM, Francois Tigeot <ftig...@wolfpond.org> >> wrote: >> > >> > The build system uses so many flags and tricks it can't run as-is under >> > the pkgsrc framework, many libraries are not found at link time. >> > Some platforms don't understand the -rlink-path and related options either. >> > >> > Using LD_LIBRARY_PATH is the simplest way I've found to package LibreOffice >> > properly on most (all ?) supported systems. >> >> I'm sorry but I really don't understand the problem you are trying to solve > > Removing unneeded complexity. > >> beside how hard can it be to figure-out on which system you are and >> use the proper path ? (see set_soenv.in for an authoritative list of >> possible values) > > It will not be too hard by itself but this will be one more script to > maintain, with its own possible problems which will bite me in the future. > > I'd rather like to not have to manage a list in the first place, and keep > the packaging script (and set_soenv.in) simple.
I don't know what you packaging script look like, but removing OUTPATH will not make set_soenv.in any substantially simpler. and no matter how hard you try there will be the nedd for per-platform value. how hard would it be for your packaging script to take advantage of Env.Host.sh ? you could get OUTPATH (1) (and/or any other similar variables) from there and then LD_LIBRARY_PATH=xxxx/$OUTPATH/xxx No need to maintain a separate list... Norbert (1) eval $(grep "^OUTPATH=" Env.Host.sh) _______________________________________________ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
