Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index

Le 21/02/2013 13:41, Dan Lewis a écrit :

Hi Dan,

     What I am going to do is run make again. This time I will use the
following so I have a log of the process: |||||
make 2>&1 | tee build.log

You have a successful LO build, congratulations.

You can now setup the build as a developer install with :

make dev-install

Upon successful completion, you will get a line that says something
about being able to set up the working environment to run the dev
version, using /.../.../ooenv. The ooenv script file is created
non-executable so you have to chmod +x it. Then you can launch ooenv
script, it doesn't do anything visible, just sets up your environment to
point to the LO-dev install tree (and probably some other magic I
haven't understood yet, like a separate configuration folder). Then you
can start LO-dev with the equivalent soffice script from the same folder
as ooenv.


For unsubscribe instructions e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.