-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
macos deployment target #80
Comments
Hmm, i have another M1 Mac user who (without xcode installed) had no problem a while ago. The WHEEL file in their imgui_bundle-0.8.2.dist-info lists this: Wheel-Version: 1.0 which surprises me. Apparently they run through rosetta: Thats fine, but what surprises me is that they have a macosx_10_16 wheel while whats on pypi for 0.8.2 is a macosx_11_0 wheel. Whats the lowest deployment target you can get away with by the way? The lower the better is my understand, because the more compatible. |
The other user now managed to install after installing xcode (compile failed since they didn't have it, xcrun not found). This is whats in the wheel file of the installed package: sysconfig.get_platform() So same as the other guy for which it did work |
Enjoy your holiday! No rush! I do see Maybe its the OpenCV? Have you tried specifying |
Closing this, as I cannot reproduce it, and it was probably solved in the next releases. Please reopen if still present. |
@pthom I cannot reopen, but this issue persists. I have a user on OSX 13.4.1 on an M1 pro for who the wheel gets compiled through xcode when trying to install imgui_bundle. For students of this user who do not have xcode, the install fails completely (of course). I asked the user to give me some info about their environment. "environment": {
"implementation_name": "cpython",
"implementation_version": "3.11.7",
"os_name": "posix",
"platform_machine": "x86_64",
"platform_release": "22.5.0",
"platform_system": "Darwin",
"platform_version": "Darwin Kernel Version 22.5.0: Thu Jun 8 22:22:20 PDT 2023; root:xnu-8796.121.3~7/RELEASE_ARM64_T6000",
"python_full_version": "3.11.7",
"platform_python_implementation": "CPython",
"python_version": "3.11",
"sys_platform": "darwin"
} A selection of what
and a whole bunch of variations with lower Python versions and lower deployment targets (10_15, etc). The problem is that your packages on pypi are Compared to our discussion from before, i see that your wheels now target 11.0 at least, instead of 13.0. But thats still too high. Could you try specifying 10.14? I am pointing out that one as some code i have that uses pretty new C++ features compiles and bundles fine with |
So that's the following locations where you could set 10.14 instead of 11.0: Line 83 in 670c72e
|
Despite your pyproject.toml listing 11.0 as a deployment target, the arm64 (but not the x86_64) wheels for 3.10 and 3.9 seem to have 13.0 as deployment target, see here: https://pypi.org/project/imgui-bundle/#files. That is causing trouble for some of my users who are on an M1, its a pretty high requirement to reach. Is it possible to correct that?
The text was updated successfully, but these errors were encountered: