-
Notifications
You must be signed in to change notification settings - Fork 228
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
macOS platform hack does not pick up workspace cargo configuration #235
Comments
To fix this, the check should be extended by also checking the workspace root for a configuration. The workspace root can be extracted from |
@evnu would you be able to create a repo with this setup so I can tinker with a fix? |
This should reproduce the problem: https://github.com/evnu/NifIo/tree/macos-platform-hack
I added a
|
@scrogson Any update here? |
I haven't spent any time thinking about this. Do we want to pull in a JSON library to remove a warning? I think the answer is no. Given that you have more experience with this setup, what do you think? |
I guess we could just check the root first and then fallback to the crate_path: https://github.com/rusterlium/rustler/blob/master/rustler_mix/lib/mix/tasks/compile.rustler.ex#L120 |
I also don't think that we should use a json library just for this. To get the workspace root, we might don't need to parse json, a regex could suffice. I can give that a try. |
See #381, we might need to parse the JSON produced by |
The platform hack for macOS does not consider a cargo configuration within a workspace, but only the configuration local to a crate. This results in unnecessary warnings when the correct arguments are already provided within the workspace-wide configuration.
The text was updated successfully, but these errors were encountered: