7a8db272e9
Had been totaly broken by the recent changes. (Which is fine, it is just an experimental hack anyway, I am not sure whether it will ever be used in anger. Just a pet peeve of mine, I dislike seeing libraries, configuration files, resources etc mixed together in one "program" folder, especially on OS X, where the convention is to have app-specific dylibs and frameworks in "Frameworks", and resource files in "Resources". But this is not any requirement as such; there are apps in the Mac App Store that blatantly "break" this convention.) Basically, replace uses of gb_PROGRAMDIRNAME and gb_Package_PROGRAMDIRNAME with more specific LIBO_FOO_FOLDER, which for normal builds all expand to the same "program" anyway. Change-Id: I16c2b3351caa00e251e229aafbccb8346042d3c1 |
||
|---|---|---|
| .. | ||
| inc_common/windows/msi_templates/Binary | ||
| inc_ooohelppack/windows/msi_templates | ||
| inc_openoffice | ||
| inc_sdkoo/windows/msi_templates | ||
| util | ||
| CustomTarget_install.mk | ||
| CustomTarget_setup.mk | ||
| Makefile | ||
| Module_instsetoo_native.mk | ||
| Package_setup.mk | ||
| README | ||
native install-set creation This is where you will find your natively packaged builds after the build has completed. On windows these would live in: workdir/*/installation/LibreOffice_Dev/native/install/en-US/*.msi for example (nothing like a few long directory names before breakfast).