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 |
||
---|---|---|
.. | ||
ExternalPackage_python3.mk | ||
ExternalProject_python3.mk | ||
GeneratedPackage_python3.mk | ||
i100492-freebsd.patch.1 | ||
Makefile | ||
Module_python3.mk | ||
python-3.3.0-15833.patch.1 | ||
python-3.3.0-aix.patch.1 | ||
python-3.3.0-clang.patch.1 | ||
python-3.3.0-darwin.patch.1 | ||
python-3.3.0-elf-rpath.patch.1 | ||
python-3.3.0-ffi-clang.patch.1 | ||
python-3.3.0-gcc-4.8.patch.1 | ||
python-3.3.0-i42553.patch.2 | ||
python-3.3.0-implicit-int.patch.1 | ||
python-3.3.0-msvc-disable.patch.1 | ||
python-3.3.0-msvc-x64.patch.1 | ||
python-3.3.0-msvc2012.patch.1 | ||
python-3.3.0-pythreadstate.patch.1 | ||
python-3.3.0-ssl.patch.1 | ||
README | ||
UnpackedTarball_python3.mk |
CPython implementation of Python 3 from http://www.python.org