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

Compiling with --no-default-features #36

Closed
ennis opened this issue Jan 29, 2019 · 3 comments
Closed

Compiling with --no-default-features #36

ennis opened this issue Jan 29, 2019 · 3 comments

Comments

@ennis
Copy link

ennis commented Jan 29, 2019

I ran into issue #33 and as a workaround, I wanted to provide my own version of the shaderc_combined library instead of compiling in build.rs. The readme suggests this is possible by disabling default features and putting the library in the correct target/deps directory, but this does not seem to work: the linker does not find the shaderc_* symbols (also the native library doesn't seem to be passed into the linker arguments).

I might be forgetting something obvious that's needed for linking with the native library, but the readme doesn't say a lot on this particular use case.

@antiagainst
Copy link
Collaborator

Hey @ennis, sorry about that. It seems building with --no-default-features has gone stale for a while. I committed 2069b5a to improve it. Will prepare a release soon.

@antiagainst
Copy link
Collaborator

Pushed out v0.3.14 including the fix. Let me know if it still has problems. Thanks!

@ennis
Copy link
Author

ennis commented Feb 4, 2019

I can see the new warning, and putting the lib at the specified location works perfectly. Thanks!

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