-
Notifications
You must be signed in to change notification settings - Fork 44
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
Unable to link to native library #104
Comments
It looks like the command to This comment is interesting...
We add the |
Hi @Michael-F-Bryan nice to hear from you!
Unfortunately there is no fool proof way to ask cargo for the paths at the moment without actually invoking the full On the other hand I've experimented with direct cargo invocation with enormous performance penalty due to cargo instances locking on project root dir. As far as I remember @brson had similar idea recently, maybe he had more success. |
Thanks for the link @budziq. I had a look through the related issues and found the build-plan crate on crates.io for reading the output from I did a bit of digging and found the file where
How hacky would it be to look for the build ouput files which correspond to our dependencies (i'm guessing we have access to the name and hash?) and then interpret them as I'm surprised using |
Skeptic is already re-implementing cargo functionality to some extent already
Very ;) but I'll try to tackle it if I'm able find some time (no promises in the near future though). In the mean time would you be able to provide me with a minimal reproducible example (some stale PR to your repo maybe) for me to tinker with in spare time? |
Not to discourage any short-term solutions to this, but I'm still of the opinion that the way to solve all these problems is to just use cargo. I mentioned some progress #18 (comment), but dropped work on it for other things. It is like 80% done though, and includes several compile-time performance mitigations. I'm sorry I've not followed through on that, but this is at least a reminder. I'm afraid that if this mess isn't solved soon that some better solution will displace skeptic. |
It looks like the
I just tried to make a minimal repro which has a The original PR is whisperfish/libsignal-protocol-rs#35, so you could check out the EDIT: You can also see the failing travis build here |
I'm wanting to test the examples in the README for a crate wrapping the
libsignal-protocol-c
library. My*-sys
crate is able to link to the C library just fine (tests run on my linux laptop, Travis CI, and a contributor's computer), but when running theskeptic
test the generated code isn't able to link to thesignal-protocol-c
library.Does the
skeptic
crate do anything special when resolving dependencies that may affect linking?Loads of compiler output
The main detail from that output is
In particular, I know my
*-sys
crate's build script tellscargo
to add/home/michael/Documents/libsignal-protocol-rs/target/debug/build/libsignal-protocol-sys-ae980dfaf57dd706/out/lib
to the library search path, but I can't see a-L /home/michael/.../out/lib
argument in the failedrustc
command.The text was updated successfully, but these errors were encountered: