Skip to content
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

Static builds don't work with Cython #567

Open
indygreg opened this issue May 30, 2022 · 1 comment
Open

Static builds don't work with Cython #567

indygreg opened this issue May 30, 2022 · 1 comment
Labels
bug Something isn't working enhancement New feature or request

Comments

@indygreg
Copy link
Owner

Our current method for producing static builds is to patch distutils in order to capture object files (.o or .obj) before they are linked. This allows us to easily supplement the final set of linked objects with ones providing symbols for extensions.

This approach is currently broken on Cython because we don't have a mechanism to peer into Cython and obtain the list of object files it produces. This can result in build/link time or possibly even run-time failures due to missing symbols.

#107, #169, #171, #215, #339, and possibly other issues have exposure to this shortcoming.

@indygreg indygreg added bug Something isn't working enhancement New feature or request labels May 30, 2022
@michelhe
Copy link

Hey @indygreg
I believe that a more generic solution like wrapping CC to hijack built object files will work better instead of relying on distutils hacks, and will also catch cython objs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants