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
Context
Re: [Libreoffice] Platform-specific OUTPATH variables · Tor Lillqvist
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.