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


Hi gbuild Wizzards !

If it works, don't fix it... but it is a brain itch I'm scratching.

I'm looking to improve our new help build with a clever way to deliver
collateral (companion) file for packaging.

The current way is as simple as copying existing files to the target as
shown below (and thanks to Stephan Bergman for the invaluable contribution):

(in helcontent2/AllLangPackage_html_media_lang.mk)

------8<-----
$(foreach lang,$(filter-out en-US,$(gb_HELP_LANGS)),$(eval $(call
gb_AllLangPackage_add_files_for_lang,helpcontent2_html_media_lang,$(lang),$(LIBO_SHARE_HELP_FOLDER)$(if
$(HELP_ONLINE),/$(PRODUCTVERSION))/media, \
    files/scalc/$(lang)/imtrigon.ods \
    files/scalc/$(lang)/trigon.ods \
    files/scalc/$(lang)/pivot.ods \
    files/scalc/$(lang)/functions_ifs.ods \
)))
------8<-----

Which requires that the ods files to exist beforehand for each of the
~40 languages we build. However not every language has it's localized
ods file so to build successfully we need to copy the en-US file to
$(lang)/ folder,

The en-US file is located in files/scalc/<file>.ods .

IOW,
If localized file exist, then deliver localized file to localized package

else deliver en-US file to localized package.

Is there a trick to change the gbuild piece above for the purpose?

Thanks in advance!

-- 
Olivier Hallot
LibreOffice Documentation Coordinator
Comunidade LibreOffice
Rio de Janeiro - Brasil - Local Time: UTC-03:00
http://tdf.io/joinus

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.