-
Notifications
You must be signed in to change notification settings - Fork 248
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
Replace target attribute with targets #428
Conversation
Also update hashes for recently rebased pull requests: - bazel-contrib/rules_foreign_cc#427 - bazel-contrib/rules_foreign_cc#428
This includes 75e74567c76fa0dabf4cc5752af3b7cee7689704 and updates for rebased pull requests: - bazel-contrib/rules_foreign_cc#427 - bazel-contrib/rules_foreign_cc#428
Actually, let's hold off with this: it should be possible to use a file group or something similar to get this to work. |
Yes that's what I was also thinking; the other way is a Also see the changes I'm making in #437 - enabling use of |
Yes, let me revert this back to a draft PR while I try to plumb something together on my side. |
This is so that multiple labels could be provided to a toolchain as sources. An example is `emcmake`, which needs both `emscripten` and `binaryen` to run. Another reason for this is to pass in config files that might be needed for the toolchain. The config files can be passed in as a label and will be available in ${EXT_BUILD_DEPS}/bin, just like any other directory.
I'm trying to get this to work, but I think it won't be possible until #437 is merged.
|
I finally managed to work around this, but I basically had to inject all required tools into It's not great but should work until #437 is done, and so I don't need this change any more. |
This is so that multiple labels could be provided to a toolchain as sources. An example is
emcmake
, which needs bothemscripten
andbinaryen
to run.Another reason for this is to pass in config files that might be needed for the toolchain. The config files can be passed in as a label and will be available in
${EXT_BUILD_DEPS}/bin
, just like any other directory.