Re: [Libreoffice] Platform-specific OUTPATH variables
On Tue, Aug 30, 2011 at 12:51 AM, Francois Tigeot ftig...@wolfpond.org wrote:
On Mon, Aug 29, 2011 at 12:17:33AM -0600, Tor Lillqvist wrote:
I'd like to consolidate the different OUTPATH values to a single one or two
at most (unx and wnt). Thoughts ?
That will break cross-compilation as currently implemented. It isn't
entirely unthinkable that somebody might at some point want to cross-compile
from some (well, *the*) mainstream Linux platform, x86_64, to a rare Linux
platform.
I have no idea how cross-compilation is currently implemented, but can't that
be done with the same build directory name for all platforms ? I would think
the path which matters most in the end is the installation one...
no, in cross compile you may have to build object/executable that run
on the build machine on top of objects/executable for the target
machine (thinks about stuff we build and use during the build like
idlc or the like)
If we have just one OUTPATH for all Unixes, the above won't work.
Can't we at least get rid of the '350' subdirectory ? Apart from $OUTPATH it
seems to always be empty.
Due to the way the build system works, I have to put many of the lib/
subdirectories in LD_LIBRARY_PATH. Otherwise, LibreOffice can simply not be
packaged in pkgsrc:
LD_LIBRARY_PATH=${BUILDLINK_DIR}/lib:${WRKSRC}/desktop/unxdfly.pro/lib:${WRKSRC}/solver/350/unxdfly.pro/lib:${WRKSRC}/desktop/unxnbsd.pro/lib:${WRKSRC}/solver/350/unxnbsd.pro/lib:${X11BASE}/lib
For now, I only do this for DragonFly and NetBSD but this is not ideal and I
will
certainly blow up some limit if I add all the Linux variants...
I'm confused, why do you need to concatenate all of these ?
Norbert
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Platform-specific OUTPATH variables
On Tue, Aug 30, 2011 at 01:07:03AM -0500, Norbert Thiebaud wrote:
On Tue, Aug 30, 2011 at 12:51 AM, Francois Tigeot ftig...@wolfpond.org
wrote:
On Mon, Aug 29, 2011 at 12:17:33AM -0600, Tor Lillqvist wrote:
I'd like to consolidate the different OUTPATH values to a single one or
two
at most (unx and wnt). Thoughts ?
I have no idea how cross-compilation is currently implemented, but can't
that
be done with the same build directory name for all platforms ? I would think
the path which matters most in the end is the installation one...
no, in cross compile you may have to build object/executable that run
on the build machine on top of objects/executable for the target
machine (thinks about stuff we build and use during the build like
idlc or the like)
Then we should only need two build directories:
- one for the host binaries
- one for the target binaries
Due to the way the build system works, I have to put many of the lib/
subdirectories in LD_LIBRARY_PATH. Otherwise, LibreOffice can simply not be
packaged in pkgsrc:
LD_LIBRARY_PATH=${BUILDLINK_DIR}/lib:${WRKSRC}/desktop/unxdfly.pro/lib:${WRKSRC}/solver/350/unxdfly.pro/lib:${WRKSRC}/desktop/unxnbsd.pro/lib:${WRKSRC}/solver/350/unxnbsd.pro/lib:${X11BASE}/lib
For now, I only do this for DragonFly and NetBSD but this is not ideal and
I will
certainly blow up some limit if I add all the Linux variants...
I'm confused, why do you need to concatenate all of these ?
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.
--
Francois Tigeot
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Platform-specific OUTPATH variables
On Tue, Aug 30, 2011 at 12:15:50AM -0600, Tor Lillqvist wrote: I have no idea how cross-compilation is currently implemented, but can't that be done with the same build directory name for all platforms ? Not unless the way it is done currently is changed. New ideas, and patches to implement them welcome. But don't just break it. Don't worry, I don't have time to work on it currently anyway. In theory, we only need two things: - tools and binaries to complete the build (run on the host) - a place to put the final binaries and files needed to run on the target For instance, when cross-compiling to PowerPC Linux from x86_64 Linux (hypothetical example, but as such potentially useful), idlc would be in solver/350/unxlngx6.pro/bin, and the PowerPC binaries being produced in solver/350/unxlngppc.pro/bin. If I understand correctly, two build subdirectories are only what is needed here. The problem is they use the exact names of the currently used host and target platforms. We could simply name them build_tools and target_files for example and this would eliminate the problem. Can't we at least get rid of the '350' subdirectory ? Yes please. I'll give it a try then. -- Francois Tigeot ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Platform-specific OUTPATH variables
Then we should only need two build directories: - one for the host binaries - one for the target binaries Bzzt, you are misunderstanding the GNU autofoo cross-compilation terminology;) (A *very* common trap to fall in...) In general, in GNU autofoo cross-compilation terminology, there are *three* platforms involved: build, host and target. The general case is when building a compiler. Consider buildng a gcc cross-compiler that should run on Windows and produce binaries for Android, and building this cross-compiler on Linux. (This is a real example.) Then build == Linux, host == Windows, target == Android. Now, LibreOffice is not a compiler, so for it host == target, and the term target should not really be used, as it means the platform a compiler or similar tool targets. So what you mean is that we need two build directories: one for the *build* platform binaries, one for the *host* platform binaries. (For instance, with host and build in their names.) Sure. That would be a pretty obvious change. It would match the file names Env.Host.sh and Env.Build.sh nicely, too. --tml ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Platform-specific OUTPATH variables
Hi Tor, On Tuesday, 2011-08-30 00:15:50 -0600, Tor Lillqvist wrote: Can't we at least get rid of the '350' subdirectory ? Yes please. The 350 should be 340 (isn't it?) for 3-4 branches, so different output hierarchies when switching branches is nice to have in order to not spoil already existing outputs. Eike -- PGP/OpenPGP/GnuPG encrypted mail preferred in all private communication. Key ID: 0x293C05FD - 997A 4C60 CE41 0149 0DB3 9E96 2F1A D073 293C 05FD signature.asc Description: Digital signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Platform-specific OUTPATH variables
Hi, On Tuesday, 2011-08-30 00:15:50 -0600, Tor Lillqvist wrote: For instance, when cross-compiling to PowerPC Linux from x86_64 Linux (hypothetical example, but as such potentially useful), idlc would be in solver/350/unxlngx6.pro/bin, and the PowerPC binaries being produced in solver/350/unxlngppc.pro/bin. Additionally, when building both, with --enable--dbgutil and without, there are for example solver/350/unxlngx6 and solver/350/unxlngx6.pro Eike -- PGP/OpenPGP/GnuPG encrypted mail preferred in all private communication. Key ID: 0x293C05FD - 997A 4C60 CE41 0149 0DB3 9E96 2F1A D073 293C 05FD signature.asc Description: Digital signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Platform-specific OUTPATH variables
Sent from my iPhone On 30.08.2011, at 14:40, Eike Rathke o...@erack.de wrote: Hi Tor, On Tuesday, 2011-08-30 00:15:50 -0600, Tor Lillqvist wrote: Can't we at least get rid of the '350' subdirectory ? Yes please. The 350 should be 340 (isn't it?) for 3-4 branches, so different output hierarchies when switching branches is nice to have in order to not spoil already existing outputs. Maybe, once a build only generates output in that single directory. Until then, the point is rather moot, IMO. -Stephan___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Platform-specific OUTPATH variables
Hi Stephan, On Tuesday, 2011-08-30 14:59:23 +0200, Stephan Bergmann wrote: Can't we at least get rid of the '350' subdirectory ? Yes please. The 350 should be 340 (isn't it?) for 3-4 branches, so different output hierarchies when switching branches is nice to have in order to not spoil already existing outputs. Maybe, once a build only generates output in that single directory. Until then, the point is rather moot, IMO. True, but instead of getting rid of solver/350 I'd rather introduce a module/$INPATH/350 ... on the other hand, having two cloned repos and build trees for different branches is a better approach. Just was thinking in terms of disk space, maybe a moot argument these days. So, I'm fine with removing 350. Eike -- PGP/OpenPGP/GnuPG encrypted mail preferred in all private communication. Key ID: 0x293C05FD - 997A 4C60 CE41 0149 0DB3 9E96 2F1A D073 293C 05FD signature.asc Description: Digital signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Platform-specific OUTPATH variables
On Tue, Aug 30, 2011 at 03:42:22PM +0200, Eike Rathke wrote: On Tuesday, 2011-08-30 14:59:23 +0200, Stephan Bergmann wrote: Can't we at least get rid of the '350' subdirectory ? Yes please. The 350 should be 340 (isn't it?) for 3-4 branches, so different output hierarchies when switching branches is nice to have in order to not spoil already existing outputs. Maybe, once a build only generates output in that single directory. Until then, the point is rather moot, IMO. True, but instead of getting rid of solver/350 I'd rather introduce a module/$INPATH/350 ... on the other hand, having two cloned repos and build trees for different branches is a better approach. Just was thinking in terms of disk space, maybe a moot argument these days. There are better solutions for the disk space problem. In the past, projects such as XFree86 used symbolic links to create shadow copies of directories: http://xfree86.org/4.3.0/lndir.1.html That way, you can have two separate source trees and only use about the same disk space than with a single one. Git clone uses hard links when the source and clone repositories are on the same filesystem. That also prevents using twice the space. For my part, I'm using filesystem deduplication; even if I cp files, they only take space once on the disk. So, I'm fine with removing 350. I'll push the commit then :-) -- Francois Tigeot ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Platform-specific OUTPATH variables
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 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) Norbert ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Platform-specific OUTPATH variables
Hi Kohei, On Tuesday, 2011-08-30 10:20:05 -0400, Kohei Yoshida wrote: You can try git-new-workdir http://kohei.us/2010/11/16/working-with-a-branch-using-git-new-workdir/ Way cool, thanks! I'll try that one day. Eike -- PGP/OpenPGP/GnuPG encrypted mail preferred in all private communication. Key ID: 0x293C05FD - 997A 4C60 CE41 0149 0DB3 9E96 2F1A D073 293C 05FD signature.asc Description: Digital signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Platform-specific OUTPATH variables
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. -- Francois Tigeot ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Platform-specific OUTPATH variables
On Tue, Aug 30, 2011 at 05:42:42PM +0200, Eike Rathke wrote: Which reminds me there may be other places that rely on the $UPD path particle. Francois, did you adapt solenv/bin/linkoo as well? Good catch, I didn't. What does this file do ? I did a complete build before commiting the patch and there was no obvious problem. -- Francois Tigeot ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Platform-specific OUTPATH variables
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=/$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
Re: [Libreoffice] Platform-specific OUTPATH variables
On Tue, Aug 30, 2011 at 11:21:18AM -0500, Norbert Thiebaud wrote: 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: I don't know what you packaging script look like, It's a Makefile: http://pkgsrc-wip.cvs.sourceforge.net/viewvc/pkgsrc-wip/wip/libreoffice/Makefile?hideattic=1revision=1.15view=markup 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=/$OUTPATH/xxx No need to maintain a separate list... (1) eval $(grep ^OUTPATH= Env.Host.sh) I could try that. Thanks for the tip! -- Francois Tigeot ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Platform-specific OUTPATH variables
On Tue, Aug 30, 2011 at 11:48 AM, Francois Tigeot ftig...@wolfpond.org wrote:
On Tue, Aug 30, 2011 at 11:21:18AM -0500, Norbert Thiebaud wrote:
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:
I don't know what you packaging script look like,
It's a Makefile:
http://pkgsrc-wip.cvs.sourceforge.net/viewvc/pkgsrc-wip/wip/libreoffice/Makefile?hideattic=1revision=1.15view=markup
btw, based on the file above and specifically the LD_LIBRARY_PATH
section I could see, it may well be that what you need is INPATH not
OUTPATH
and
${TOUCH} ${WRKSRC}/clone/repos_changed
I don't think repos_changed is used anymore (that was a trick in the
3.3 'build-repo' based build)
Norbert
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Platform-specific OUTPATH variables
On Tue, Aug 30, 2011 at 11:58:08AM -0500, Norbert Thiebaud wrote:
On Tue, Aug 30, 2011 at 11:48 AM, Francois Tigeot ftig...@wolfpond.org
wrote:
On Tue, Aug 30, 2011 at 11:21:18AM -0500, Norbert Thiebaud wrote:
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:
I don't know what you packaging script look like,
It's a Makefile:
http://pkgsrc-wip.cvs.sourceforge.net/viewvc/pkgsrc-wip/wip/libreoffice/Makefile?hideattic=1revision=1.15view=markup
btw, based on the file above and specifically the LD_LIBRARY_PATH
section I could see, it may well be that what you need is INPATH not
OUTPATH
Afaik INPATH = $OUTPATH + something . That could be true
and
${TOUCH} ${WRKSRC}/clone/repos_changed
I don't think repos_changed is used anymore (that was a trick in the
3.3 'build-repo' based build)
It was needed in July at least; otherwise, some script tried to download all
the possible remotes files in src/
--
Francois Tigeot
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Platform-specific OUTPATH variables
On Tue, Aug 30, 2011 at 12:01 PM, Francois Tigeot ftig...@wolfpond.org wrote:
On Tue, Aug 30, 2011 at 11:58:08AM -0500, Norbert Thiebaud wrote:
On Tue, Aug 30, 2011 at 11:48 AM, Francois Tigeot ftig...@wolfpond.org
wrote:
On Tue, Aug 30, 2011 at 11:21:18AM -0500, Norbert Thiebaud wrote:
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:
I don't know what you packaging script look like,
It's a Makefile:
http://pkgsrc-wip.cvs.sourceforge.net/viewvc/pkgsrc-wip/wip/libreoffice/Makefile?hideattic=1revision=1.15view=markup
btw, based on the file above and specifically the LD_LIBRARY_PATH
section I could see, it may well be that what you need is INPATH not
OUTPATH
Afaik INPATH = $OUTPATH + something . That could be true
and
${TOUCH} ${WRKSRC}/clone/repos_changed
I don't think repos_changed is used anymore (that was a trick in the
3.3 'build-repo' based build)
It was needed in July at least; otherwise, some script tried to download all
the possible remotes files in src/
hummm... maybe.. but right now git grep repos_changed return nothing at all
are you sure you are not confusing it with src.downloaded ?
Norbert
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Platform-specific OUTPATH variables
Hi Francois, On Tuesday, 2011-08-30 17:49:06 +0200, Francois Tigeot wrote: Francois, did you adapt solenv/bin/linkoo as well? Good catch, I didn't. What does this file do ? I did a complete build before commiting the patch and there was no obvious problem. When doing make dev-install it creates symbolic links from the basis-link/program/ directory to the platform's solver directory for most libraries, where applicable. So, after having rebuilt some module(s) you can just run the application from the installation without having to copy libs around. Btw, one of my earlier mails Cc'ed franc...@freedesktop.org and I got a bounce for that: SMTP error from remote server after RCPT command: host gabe.freedesktop.org[131.252.210.177]: 550 5.1.1 franc...@freedesktop.org: Recipient address rejected: User unknown in local recipient table Eike -- PGP/OpenPGP/GnuPG encrypted mail preferred in all private communication. Key ID: 0x293C05FD - 997A 4C60 CE41 0149 0DB3 9E96 2F1A D073 293C 05FD signature.asc Description: Digital signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Platform-specific OUTPATH variables
Hi Eike, On Tue, Aug 30, 2011 at 07:42:54PM +0200, Eike Rathke wrote: On Tuesday, 2011-08-30 17:49:06 +0200, Francois Tigeot wrote: Francois, did you adapt solenv/bin/linkoo as well? Good catch, I didn't. What does this file do ? I did a complete build before commiting the patch and there was no obvious problem. When doing make dev-install it creates symbolic links from the basis-link/program/ directory to the platform's solver directory for most libraries, where applicable. So, after having rebuilt some module(s) you can just run the application from the installation without having to copy libs around. OK. It is now fixed. Btw, one of my earlier mails Cc'ed franc...@freedesktop.org and I got a bounce for that: That address doesn't exist; it could have been a bug or some sort of mistake... -- Francois Tigeot ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Platform-specific OUTPATH variables
I'd like to consolidate the different OUTPATH values to a single one or two at most (unx and wnt). Thoughts ? That will break cross-compilation as currently implemented. It isn't entirely unthinkable that somebody might at some point want to cross-compile from some (well, *the*) mainstream Linux platform, x86_64, to a rare Linux platform. So any remoival of infromation from OUTPATH will cause a clash for such. Ditto for cross-compilation from Intel Mac OS X to PowerPC Mac OS X, which in fact is the cross-compilation setup that in theory should be the easiest to handle. (Even if it is the one that has received least attention so far.) If we have just one OUTPATH for all Unixes, the above won't work. Also iOS (unxiosr) and Android (unxandr) would clash with a generic unx. (Sure, we could change the OUTPATH values for these two special cases, to, say, ios and and if we want to stick to three letters. As such I don't see why we should stick to three-letter codes, though; if we do what you suggest to OUTPATH, surely we should get rid of odd pointless abbreviations and just spell unix in full etc.) --tml ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [Libreoffice] Platform-specific OUTPATH variables
On Mon, Aug 29, 2011 at 12:17:33AM -0600, Tor Lillqvist wrote:
I'd like to consolidate the different OUTPATH values to a single one or two
at most (unx and wnt). Thoughts ?
That will break cross-compilation as currently implemented. It isn't entirely
unthinkable that somebody might at some point want to cross-compile from some
(well, *the*) mainstream Linux platform, x86_64, to a rare Linux platform.
I have no idea how cross-compilation is currently implemented, but can't that
be done with the same build directory name for all platforms ? I would think
the path which matters most in the end is the installation one...
If we have just one OUTPATH for all Unixes, the above won't work.
Can't we at least get rid of the '350' subdirectory ? Apart from $OUTPATH it
seems to always be empty.
Due to the way the build system works, I have to put many of the lib/
subdirectories in LD_LIBRARY_PATH. Otherwise, LibreOffice can simply not be
packaged in pkgsrc:
LD_LIBRARY_PATH=${BUILDLINK_DIR}/lib:${WRKSRC}/desktop/unxdfly.pro/lib:${WRKSRC}/solver/350/unxdfly.pro/lib:${WRKSRC}/desktop/unxnbsd.pro/lib:${WRKSRC}/solver/350/unxnbsd.pro/lib:${X11BASE}/lib
For now, I only do this for DragonFly and NetBSD but this is not ideal and I
will
certainly blow up some limit if I add all the Linux variants...
--
Francois Tigeot
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice
