diff options
| author | Tor Lillqvist <tml@collabora.com> | 2013-09-25 20:42:34 +0200 |
|---|---|---|
| committer | Tor Lillqvist <tml@collabora.com> | 2013-09-25 22:13:23 +0200 |
| commit | 7a8db272e95e0d3255b515567ed5e00738cf6760 (patch) | |
| tree | e46475b2aeabffd00e117c9ebe46eec60226fed2 /oovbaapi | |
| parent | aa26a065867c36a412193db9854cf2ca97154dde (diff) | |
Start hacking --enable-canonical-installation-tree-structure back into shape
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
Diffstat (limited to 'oovbaapi')
| -rw-r--r-- | oovbaapi/UnoApi_oovbaapi.mk | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/oovbaapi/UnoApi_oovbaapi.mk b/oovbaapi/UnoApi_oovbaapi.mk index e545cbc33d25..a80fb8825d11 100644 --- a/oovbaapi/UnoApi_oovbaapi.mk +++ b/oovbaapi/UnoApi_oovbaapi.mk @@ -19,7 +19,7 @@ $(eval $(call gb_UnoApi_UnoApi,oovbaapi,oovbaapi)) -$(eval $(call gb_UnoApi_install,oovbaapi,$(gb_PROGRAMDIRNAME)/types/oovbaapi.rdb)) +$(eval $(call gb_UnoApi_install,oovbaapi,$(LIBO_ETC_FOLDER)/types/oovbaapi.rdb)) $(eval $(call gb_UnoApi_use_api,oovbaapi,\ udkapi \ |