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


Hi Markus,

--with-help works fine. Thank you.

Kind regards
Regina

Markus Mohrhard schrieb:
Hey Regina,

On Sat, Jul 18, 2015 at 3:05 PM, Regina Henschel
<rb.henschel@t-online.de <mailto:rb.henschel@t-online.de>> wrote:

    Hi all,

    I want to add the information in the build-in help for the new
    command .uno:ImportMathMLClipboard. But I need some "getting
    started" help.

    I have (first time) got a build following the description in
    https://wiki.documentfoundation.org/Development/BuildingOnWindows.
    But that is only for core.

    What command to use for clone "help" so that is is usable together
    with "core"?

    What configure to use, so that the English "help" is compiled too?

    How to get the help to be tested in my self-made build?

    I have found
    https://wiki.documentfoundation.org/Development/Submodules. But that
    is about sending a patch to Gerrit and currently I do not even have
    got .git/modules


Just add --with-help to your autogen.lastrun or autogen.input and the
build system will take care of the rest.

Regards,
Markus


    Kind regards
    Regina


    _______________________________________________
    LibreOffice mailing list
    LibreOffice@lists.freedesktop.org
    <mailto:LibreOffice@lists.freedesktop.org>
    http://lists.freedesktop.org/mailman/listinfo/libreoffice




Context


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.