-
Notifications
You must be signed in to change notification settings - Fork 54
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
pybind_libraries get compiled twice #47
Comments
How much trouble is it to provide a reproducer (something that I could git clone unzip or similar, then run some commands you give me)? I'm not a blaze expert myself, but I'm pretty sure there are valid situations in which there are multiple compilations for the same sources, but without a reproducer it's difficult to tell if that's a situation you have. It could also happen by accident. |
Hmmm it seems like this might be on me. I'm using pybind_library and then using that as a srcs in pybind_extension. If I just use the pybind_extension it seems like things only get compiled once. Sorry I don't have a good reproduction for you, this is pretty tightly embedded in our code base and would be non-trivial to get a minimal reproduction. Happy to close it though as this seems to solve my issue. |
Did you already try using that as That's how we do it internally. I'm not very familiar with the external side myself, which is a lot less developed than the internal adaption of the same core tool. For reasons I don't know, here What I know though is that that works. |
I'm not sure if I'm using the rule correctly or if this is intended behavior but I seem to be getting two compilations for my pybind targets w/ very slightly different compiler options.
The text was updated successfully, but these errors were encountered: