Hello, I am beginning to understand the directory structure of the project :-). And yes, the last build was successful, scalc is now running on my desktop.
Thank you all for the help, it saved me days of struggling. Regards, Imre > 2009/11/2 Ingo Schmidt - Sun Germany - ham02 - Hamburg < > [email protected]> > > 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 >> >>
