Joris Dauphin
Joris Dauphin
About Codelite, ignoring premake issues, it has issue with semicolon in MACRO and compiler options :( . For gmake; I tried: -- defines {"\'FOO=const char* foo() { return \"[]|\"; }\'"}...
I have that which works (I replace ; by SEMICOLON as workaroung for bug inside codelite). ``` ```
As it is in string (inside XML), yes. "defines" goes in "Preprocessor", "buildoptions" goes in "Compiler" "Options" for c++, C_Options for C. Notice that I'm just user of Codelite, not...
I tested both buildoptions and defines. Premake should handle both (up to you to prioritize bug resolution though ;) ) It is easier for me to use -D in buildoptions...
Codelite has just fixed their semicolon bug (I have to test it), so, Premake just has to fix escaping.
It is mostly my point about those unit tests where it is difficult (when possible) to see the issue in expected result: ``` ``` Escaping space (`\ `) inside (escaped)...
@samsinsane: I know expected codelite/gmake result, but I have to know the wanted premake syntax (behavior has changed between premake4 and premake5, not sure it is intended) As I said,...
Related to #1216 and #1059
About python (and most lib), notice there are several versions. How about `os.findheader('python3.8/Python.h')`?
I don't know.