-
Notifications
You must be signed in to change notification settings - Fork 1k
[Feature] Added features to the premake cli wrapper #17398
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
Conversation
- Modifiable premake action (autodetected in constructor) - Modifiable lua file location - Custom user actions (defined within the premake5.lua file) exposed as 'arguments'
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be great to add a couple of unit test illustrating the usage and functionality of these changes. I understand they cover some customization cases, which seems legit, but seeing the actual usage tests help to polish the UI and also to get them covered for the future to avoid possible future breakages.
Thanks for your contribution @Ohjurot !
Thanks for the feedback @memsharded! I will implement as soon as I have time. |
Hi @Ohjurot It would be nice to get this merged, do you think you will be able to add a couple of small tests? |
Hi @memsharded |
Taking over the tests, I am also provisioning premake in CI in #17765 |
Merged, it will be in next Conan 2.13, thanks again for the contribution |
Changelog: Feature: Enhanced
Premake
CLI wrapper with configurable Lua file path, and support for custom command-line arguments.Docs: conan-io/docs#4000
premake5.lua
file is changeablearguments
Thees changes are required in order to fully support calling the premake5 executable. This lays the foundation for a
PremakeToolchain
.This is one of the key components of #14724 but in a modified version. I plan to add the other main feature (build) as a follow up under
PremakeToolchain
. As I have understand as long as premake does not have a build feature. Which it does not have. It should be "chained" as a Toolchain that would utilize the cli wrapper and the platform specific build system wrapper (MSBuild
or a directmake
call) other than being integrated in the cli wrapper. Correct?Would we need to add any test coverage other than the "basic" test @memsharded added? Like checking that arguments work etc.)
Currently there is (as previously discussed) no documentation for the whole premake feature set. I assume we will stay like this for now. I would however recommend to document the feature as soon as premake is feature complete.
develop
branch, documenting this one.