[Issue 15105] paths never work

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=15105

--- Comment #5 from Manu <turkeyman at gmail.com> ---
(In reply to Rainer Schuetze from comment #4)
> > Sounds like quite a bit of work, but it might make this entire class of problem disappear once and for all :)
> 
> Although it sounds like a feasible idea I'm a bit hesitent to build a
> framework for specifying a new tool chain. Each one has its special cases
> not easily mapped to a simple definition file.
> It also means that a project won't compile correctly on another system
> without also transferring the tool chain setup (which is not part of the
> project).

This is an open problem. A project with an 'XBox 360' platform can't build
those configurations if the user doesn't have the toolset installed.
In the case of C/C++, if the platform is unavailable, the project still loads,
but those particular configurations give build errors.

I think the conventional way to solve this problem is to make the solution
platforms known defined values. That way, when the user configures the
toolchain, the solution platform names will be standardised and match properly.

Clang support is implemented via platform-toolset, but the same story there;
platform toolset names need to match appropriately, although in that case, it's
all just MSBuild mischief. If LLVM isn't installed, it just complains when
trying to build that config.

> I'll have a closer look at how QtCreator is dealing with this...
> 
> I was also considering allowing to build through msbuild, but that needs
> people to write support assemblies for the specific tool chains.

I had a brief look into this at one point; it looked to me like it might be
possible to make regular vcxproj files capable of building D code with
appropriate property pages. The problem then would probably become launching
the correct debug environment when launching.

--