Joris Dauphin

Similarly, [premake](https://github.com/premake/premake-core) uses some functions to *"open"* block. Wonder if it could be handled in some way.

Closing as probably outdated, reopen it or open another one if problem is still present.

Indeed, disabled project aren't build with workspace, but can directly be build (I mess up with shortcut with my tests :-/ ) But "Compiler (maybe linker) is not required for...

For VS2010+ in fact.

(deprecated) gmake can have similar fix. Question, why not have something like following instead ``` function gmake2.objDirRules(cfg, toolset) if cfg.objdir ~= cfg.targetdir then gmake2.mkdirRules("$(OBJDIR)") end ```

Related to https://github.com/premake/premake-core/issues/1346 As premake uses Lua, you might still create Lua functions: ```Lua function useGsl() externalincludedirs { "gsl/include" } defines { "HAS_GSL" } end ``` and then ```Lua project...

``` filter { "files:**.c++" } compileas "C++" ``` Should do the trick for gmake2. (not or partially supported by other generators). See [`compileas`](https://premake.github.io/docs/compileas/) for details.

As I remember, it might be useful only for cases with `absolute = true` (as other values are identical as without pathvars)... But I would say our handling of absolute...

For info, posted on [stackoverflow](https://stackoverflow.com/questions/77747797/premake5-generated-xcode-project-does-not-see-vcpkg-installed-dependency)

Just added sample project to test ["external" links](https://github.com/Jarod42/premake-sample-projects/tree/master/projects/project-linkexternalproject). It compiles with xcode4 (on CI, I don't have MacOS). It is possible though that you cannot see the libraries where you...