Joris Dauphin
Joris Dauphin
premake5.lua might add extra options to the help (extra command lines, extra modules, ...), so to be accurate, executable has to read the file.
In the PR https://github.com/dcourtois/premake-qt/pull/21 I add 2 scripts one with that premake module, and one without. For `uic`, the alternative is fine: you can use premake rule Something like ```...
Some advancements: - https://github.com/premake/premake-core/pull/1951 fixes Codelite generation. - Code::Blocks doesn't handle custom build on headers which generate cpp files. (And would require premake-qt fix for qrc).
- For gmake2, there is still your opened ticket https://github.com/premake/premake-core/issues/1916 - Codelite generation is now fixed (by above PR in premake-core :-) ) Next one I'm working on is for...
Just tested gmake (not gmake2), and it is working :-)
I don't use xcode ;-) So, I don't know if xcode has special field for that. At worst, it could be added as it does with `buildoptions`. Discovered with my...
I wonder if [`os.chdir`](https://premake.github.io/docs/os.chdir) would do the job. Else I would look at `premake.field.kind("path",`.
[`basedir`](https://premake.github.io/docs/basedir/) seems indeed a good track.
D module seems written in modular way though. You might use D as model to write premake-tcc as external module.
> Missing documentation file for: documentationfile