AuroraPipeline/fuck-premake-old2
Archived
1
0
Fork 0
Code Issues 1 Pull Requests Projects Releases Wiki Activity

compilebuildoutputs make some comments obsolete.

Browse Source
This commit is contained in:
Jarod42 2021-07-04 00:22:22 +02:00
parent 0c42fb8691
commit a70c67b7e7
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
website/docs/Custom-Build-Commands.md
View File

@ -48,7 +48,8 @@ The basic syntax follows Visual Studio's model, but it should be easy to see how
Build rules follow the same configuration scoping as the rest of the Premake API. You can apply rules to a specific platform or build configuration, to specific files or all files, or to any combination. And you can use [Tokens](Tokens.md) to create generic commands that will work across platforms and configurations.
If the outputs include any object files, they will be automatically added to the link step. Ideally, any source code files included in the outputs would be fed back into the build, but that is not the case currently.
If the outputs include any object files, they will be automatically added to the link step.
Any source code files included in the outputs might be fed back into the build with [compilebuildoutputs](compilebuildoutputs.md).
Custom build commands currently have a few shortcomings. Help fixing these issues, or any other gaps, would be most appreciated!