Thomas Desveaux

Making `sysincludedirs` points to `SYSTEM_HEADER_SEARCH_PATHS` seems the correct solution to me. I do not use XCode, what are the differences between `USER_HEADER_SEARCH_PATHS` and `HEADER_SEARCH_PATHS`?

@samsinsane I don't know how many people rely on the D module with gmake so I wouldn't just drop it. Also, I think it would be a good use case...

I looked into porting the D module and I'm now inclined to dropping it. The only changes I saw looks more like people trying to adapt it when they are...

This works and add both files to each projects. ```lua workspace "Solution" configurations { "Release", "Debug" } platforms { "x64", "x32" } files { "test.natvis", "config.editorconfig" } project "Project" kind...

Indeed, that would be useful. Do you know if natvis informations from a solution level file are added to the pdb when building a c++ project as they are when...

I can't think of any either. I do like the `solutionitems` container proposed by @tvandijck, this would leave the possibility to add files at workspace scope that are inherited by...

To shorten your workaround, you could use tokens and have something like this ```lua -- GCC Options filter { "toolset:gcc" } linkoptions{"-Wl,--whole-archive libStaticLib%{cfg.buildcfg}.a -Wl,--no-whole-archive"} -- Clang options filter { "toolset:clang"...

I know that Blizzard had a premake module for consoles on their github and I based the one we use on theirs (thanks by the way). However, they either deleted...

So, I also asked and I should be able to use our contacts but I am waiting the final confirmation about this (which will be tomorrow morning, Paris time). About...

So I got the greenlight to contact Microsoft, Sony and Nintendo through our account managers. I will let you know when I have further information.