[issue46248] Compilation errors on macOS

Change by Ned Deily : -- resolution: -> third party stage: -> resolved status: open -> closed ___ Python tracker ___ ___

[issue46248] Compilation errors on macOS

Ronald Oussoren added the comment: The libraries you mention are 3th party projects. Please check with the project first. I've look at the GitHub repository for libmobiledevice and have no idea how they determine the compiler flags for Python. As mentioned in an earlier version

[issue46248] Compilation errors on macOS

Sandip Shah added the comment: Hi, Like I mentioned in the ticket, I am trying to compile libplist, libimobiledevice , and libimobiledevice-glue-1.0 on my mac. These are needed to do any development on a mobile device (specifically for testing / automation). I use Python for a lot of

[issue46248] Compilation errors on macOS

Ronald Oussoren added the comment: Part of the problem here is that most keys in the result of sysconfig.get_config_vars() are copied as-is from the CPython Makefile and pyconfig.h header file. The keys copied from the Makefile are in a lot of cases not useful for users of python because

[issue46248] Compilation errors on macOS

Ned Deily added the comment: Thanks for the report. Without more details, we can only guess at what you are trying to accomplish. I would assume it involves embedding Python in another library or application. If so, you should not be using LINKFORSHARED at all which is used to build Python

[issue46248] Compilation errors on macOS

New submission from Sandip Shah : macOS Monterey 12.1 Python 3.10.1 Trying to compile libplist, libimobiledevice, libimobiledevice_glue generates the error "Could not link test program to Python. Maybe the main Python library has been installed in some non-standard library path. If so, pass