Replies: 1 comment 9 replies
-
|
The correct setting is |
Beta Was this translation helpful? Give feedback.
9 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Moved from #958:
@kfchou commented:
I have 2 wheels I'd like to use:
In briefcase' pyproject.toml file:
Note that the android_21 tag is incorrect; I had specified android_30. This is an issue on my end.
Nevertheless, the build fails with:
How come the build process is not honoring the x86_64.whl file?
I haven't tried to build numpy 2.3.2. Would that be the issue?
It is possible that the wheels are not compiled correctly; I'm trying to test them. The best way I thought to do this was to build a briefcase example project (
briefcase start) and ask it to import numpy.Please advise
@mhsmith commented:
You can't mix wheels for multiple architectures in your
requireslist, because each architecture is installed with a separate run ofpip. Instead, yourrequireslist should simply saynumpy==2.4.0.dev0.There is no
pip_install_argssetting. Where did you get that from? The correct setting isrequirement_installer_args.Finally, for pip's
--extra-index-urloption to work, you'll need to put the wheels inside anumpysubdirectory. Alternatively, you can use--find-links, which expects a flat directory layout. See therequirement_installer_argsdocumentation for examples.@kfchou commented:
Thanks for your response @mhsmith . I've updated my configurations but the build is still failing. My
pyproject.tomlfile hasand my directory structure is
The build log suggests pip is still looking in pypi:
Is there something I'm missing?
Beta Was this translation helpful? Give feedback.
All reactions