You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 17, 2024. It is now read-only.
I've found that proto does include the native libraries necessary to build python native code, but it doesn't expose them. There are two problems I've identified so far:
the python-config binary is not exposed in bin or shims. I am working around that like this:
For build systems that us the pkg-config tool, the prefixes in the .pc files located in .proto/tools/python/3.10.12/install are wrong. They are just prefix=/install when they should be a correct absolute path.
I am working around that with this hack:
sed -i 's|prefix=/install|prefix=/home/.../.proto/tools/python/3.10.12/install|' ~/.proto/tools/python/3.10.12/install/lib/pkgconfig/python3.pc
sed -i 's|prefix=/install|prefix=/home/.../.proto/tools/python/3.10.12/install|' ~/.proto/tools/python/3.10.12/install/lib/pkgconfig/python3-embed.pc
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I've found that proto does include the native libraries necessary to build python native code, but it doesn't expose them. There are two problems I've identified so far:
python-config
binary is not exposed inbin
orshims
. I am working around that like this:For build systems that us the
pkg-config
tool, the prefixes in the .pc files located in.proto/tools/python/3.10.12/install
are wrong. They are justprefix=/install
when they should be a correct absolute path.I am working around that with this hack:
The text was updated successfully, but these errors were encountered: