ali5h

Results 17 comments of ali5h

with this patch i see the change in `project-config.jam` but `g++` calls still use the wrong include path for python include.

we have the option to change the prefix of the names of repos generated by pip_import, you can change it to something other than `pypi` and then they don't overwrite...

yes, it is recent, i think it is reasonable

another solution is that we can include platform in the generated repo name

basically the whole wheel signature

please rebase on master, thanks

I don't fully understand your concern. what do you mean user provides the pip-tools?

I haven't figure out yet why some of the binaries have this without setting any option, but i know in pure more none of them has it. My use case...

interesting, this does not work in pure mode I assume, which is what we are using right now.

I tried for one binary. Build failed in pure mode and no build id was set in non-pure mode either.