summaryrefslogtreecommitdiff
path: root/pyuno
diff options
context:
space:
mode:
authorTor Lillqvist <tml@collabora.com>2013-09-25 20:42:34 +0200
committerTor Lillqvist <tml@collabora.com>2013-09-25 22:13:23 +0200
commit7a8db272e95e0d3255b515567ed5e00738cf6760 (patch)
treee46475b2aeabffd00e117c9ebe46eec60226fed2 /pyuno
parentaa26a065867c36a412193db9854cf2ca97154dde (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 'pyuno')
-rw-r--r--pyuno/Package_python_shell.mk2
1 files changed, 1 insertions, 1 deletions
diff --git a/pyuno/Package_python_shell.mk b/pyuno/Package_python_shell.mk
index a986d72900f3..3f148417c231 100644
--- a/pyuno/Package_python_shell.mk
+++ b/pyuno/Package_python_shell.mk
@@ -11,6 +11,6 @@ $(eval $(call gb_Package_Package,python_shell,$(call gb_CustomTarget_get_workdir
$(eval $(call gb_Package_set_outdir,python_shell,$(INSTROOT)))
-$(eval $(call gb_Package_add_file,python_shell,$(gb_Package_PROGRAMDIRNAME)/python,python.sh))
+$(eval $(call gb_Package_add_file,python_shell,$(LIBO_BIN_FOLDER)/python,python.sh))
# vim: set noet sw=4 ts=4: