Skip to content

No recommended practices for non-system libraries #1299

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

Closed
spease opened this issue Apr 3, 2018 · 0 comments · Fixed by #2318
Closed

No recommended practices for non-system libraries #1299

spease opened this issue Apr 3, 2018 · 0 comments · Fixed by #2318

Comments

@spease
Copy link

spease commented Apr 3, 2018

It would be nice if the manual provided an example of a non-system library. There are probably two common cases:

  • The source code is available and the library needs to be checked out and perhaps built
  • The library is prebuilt and distributed with libraries and header files

Specifically the point of ambiguity right now is what path I should put in link() for the generated code to work correctly on someone's system who's trying to build the Rust library. This will likely become clear eventually, but it'd be nice to know up-front while I'm writing the build script.

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

Successfully merging a pull request may close this issue.

2 participants