-
Notifications
You must be signed in to change notification settings - Fork 56
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
Ability to pass directory of C library #180
Comments
Compiling with the 'bundle' feature activated has cloned the nanomsg git repository in the nanomsg_sys directory, version 1.0.0. It seems you can control the version of nanomsg that will be included by cloning it manually and checking out the desired tag before building. If this is not sufficient for your needs I would happily merge any PR that adds this option without breaking the existing behavior. |
@blabaere it doesn't work that way, or I can't get it to work that way - what should be the path of my clone? If I clone it in the main directory of the repository this approach doesn't work - |
Here is the layout my local clone:
The Does it work for you if you clone the nanomsg git repository under |
@blabaere oh I thought that there might be a way to just include C sources in a submodule, but you suggest putting both |
@fuine I have not thought of the problem any further than getting the rust library to compile a locally modified C library. I now understand that you want to setup your working environment to actually work on the nanomsg source but use it from a rust progrem, is that correct ? If it is, I guess that making nanomsg a submodule of nanomsg.rs, right inside the nanomsg_sys directory is the way to go. But that's only a guess since I have never worked with submodules. |
Sort of, I would like to use a different version than |
I would like to be able to somehow pass path to the C sources of
nanomsg
, when featurebundled
is set - that way I don't have to rely ongit
and I can easily choose which version ofnanomsg
will the crate be compiled against. Is it doable and if so would maintainers consider incorporating this feature into the crate?I can see that
nanomsg-sys
checks ifnanomsg/.git
path exists, but it's not clear to me that working directory is it checking - I have Cnanomsg
in my project directory as git's submodule but it doesn't look likenanomsg-sys
finds it.The text was updated successfully, but these errors were encountered: