28 ms·

If it's an autoconf project you should be able to (as far as I recall) pass appropriate min version and architecture flags to ./configure Python bundles a bunc

by zZorgz 10y ago

If it's an autoconf project you should be able to (as far as I recall) pass appropriate min version and architecture flags to ./configure Python bundles a bunch of modules one may not need for embedding in either case, and they can be turned into byte code before distribution.

jventura 10y ago
I've managed to compile Python 3.5 from source setting MACOSX_DEPLOYMENT_TARGET=10.8 on the Makefile (after doing ./configure). But by default it compiles Python to a static library, which is quite ok, but I am having trouble compiling to a "Framework", which I think would give me the dynamic library. Although Python is widely used, everything related to these kind of things seems to be poorly documented.. Edit: just need to do "./configure --enable-shared" and it will compile Python as shared library (libpython3.5m.dylib)..
- deleted 10y ago
  [deleted]
- zZorgz 10y ago
  I think I have set CFLAGS to something like "-arch x86_64 -mmacosx-version-min=10.8″ when running ./configure to autoconf projects. It's not really specific to Python, so "poorly documented" isn't a surprise.
  - jventura 10y ago
    For Python you just need to do "./configure MACOSX_DEPLOYMENT_TARGET=10.8".. I'm creating another blog post with all the info I got from this thread, regarding compiling Python from sources. I'm going to put the link here when ready.. Edit: http://joaoventura.net/blog/2016/embeddable-python-osx-from-src/ http://joaoventura.net/blog/2016/embeddable-python-osx-from-...