Hello,
LOCALINSTALLDIR was not created for this situation. Typically you can
use PKGFORMAT=installed without any problem. You will get all
installation sets in the output of instsetoo_native, the same way you
will get the RPMs or the tar.gz files. In instsetoo_native you have the
productname in the path to the installation set, so that there is no
conflict. This works for all package formats, for "rpm", for "archive"
and for "installed". But if you use LOCALINSTALLDIR, you break the
standard output directory, because you decide, where the installation
set shall be located. And if you build three installation sets, all
three are of course created into LOCALINSTALLDIR. Of course we can add
the productname automatically to LOCALINSTALLDIR, but this fails, if you
build OOo in French after OOo in English. So adding the language would
also be necessary.
So please use LOCALINSTALLDIR only, if you create one specified
installation set. By the way, FORCE2ARCHIVE forces the package format to
"archive", which is pretty the same as "installed", but only compresses
the content at the end. So please feel free to use "installed", but not
in combination with LOCALINSTALLDIR. Use LOCALINSTALLDIR not as default,
but only, if you want to create the installation set at a specified
location.
Regards
Ingo
On 11/02/09 16:34, Imre Steer wrote:
Hello guys,
Thanks for the quick response, I will try these and I think it will be OK.
Kind regards,
Imre
2009/11/2 bjoern michaelsen - Sun Microsystems - Hamburg Germany <
[email protected]>
On Mon, 02 Nov 2009 14:40:31 +0100
Stephan Bergmann <[email protected]> wrote:
On 11/02/09 14:02, Imre Steer wrote:
3. Run the bootstrap script and set up the environment variables
with the LinuxX86Env.Set.sh and with:
export LOCALINSTALLDIR="/usr/local/ooo"
export PKGFORMAT="installed"
[...]
5. After about three hours the compilation finished, showed no
error but I cannot find the resulting executables in the given
directory, only URE has been put here.
I assume what happens is the following: Per
instsetoo_native/util/makefile.mk, three products are built by
default, openoffice_en-US, sdkoo_en-US, and ure_en-US. If each
builds into $LOCALINSTALLDIR, and presumably removes the directory
before installing into it, the net effect would be to have just URE
(the product that happens to be built last) afterwards. (Also, if
you did a parallel build, you would probably get even more funny
results.)
Is there a bug for this? If not, I think we should create one. This is
really confusing for newcomers. For now, I removed PKGFORMAT=installed
from the Building Guide. FORCE2ARCHIVE should do for now.
Best Regards,
Bjoern
--
===========================================================================
Sitz der Gesellschaft:
Sun Microsystems GmbH, Sonnenallee 1, D-85551 Kirchheim-Heimstetten
Amtsgericht Muenchen: HRB 161028
Geschaeftsfuehrer: Thomas Schroeder, Wolfgang Engels, Wolf Frenkel
Vorsitzender des Aufsichtsrates: Martin Haering
===========================================================================
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
