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

Incorrect behaviour of cffi build step for deeply nested modules (nesting level > 1) #15

Closed
daa opened this issue May 14, 2018 · 0 comments

Comments

@daa
Copy link
Contributor

daa commented May 14, 2018

First, thank you for milksnake, I found it very helpful in building external libraries with setuptools.

Here is a problem I've met: consider cffi module named p0.p1.modname, currently CffiModuleBuildStep determines module base as p0 and consequently puts compiled library and generated cffi module in build/lib/p0 directory instead of correct build/lib/p0/p1 and thus required module cannot be found and imported.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants