please
please copied to clipboard
High-performance extensible build system for reproducible multi-language builds.
Reduces one allocation in `provideFor` and a few other things in paths of varying temperatures (notably getting rid of `fmt.Sprintf` which isn't the most efficient way to put strings together,...
We have a whole bunch of tarballs and whatnot. I'd like to get rid of them to simplify what we're doing with our downloads. I think a nice future state...
Set an environment variable of `PLEASE=1` for all commands so that it's possible to detect if the command is being run inside Please.
Fixes #3318, fixes #3168 Currently, if a rule creates multiple outputs that are not known at initial run, there is no way to have please generate the required rules in...
When cross compiling, the wrong settings are getting used for subrepos sometimes. I haven't been able to create a minimal environment that reproduces this behavior unfortunately. What I can say...
I've recently begun trying to use the [go-rules](https://github.com/please-build/go-rules) plugin in place of the built-in go rules as the direction of travel seems to be that the built-in rules will get...
The [get_outs(label)](https://github.com/thought-machine/please/blob/dec2032f737f00579930a01e3028514041884850/rules/builtins.build_defs#L260) builtin doesn't seem to return all the actual outputs of the given label. The outputs that are returned reliably seem to be those literally defined within the `outs=`...
After we performed a recent Please upgrade, we noticed major differences between the output of `please query deps` in version 17.8.7 (our previous version) and the latest, 17.12.7. In particular...
Please take a look at https://github.com/linuxerwang/plz-config. It gets error at building: ``` $ plz build cmd:cmd Build stopped after 180ms. 1 target failed: //cmd:cmd Error building target //cmd:cmd: exit status...