[Development] New proposal for the tool naming

[BRM]

> From: Konstantin Ritt <ritt.ks at gmail.com>
> Sent: Sunday, October 21, 2012 5:56 AM
> Subject: Re: [Development] New proposal for the tool naming
>>>  > The easiest way to achieve that is probably to create a solution 
> based on
>>>  > files and you create a ~/.config/qconfig-maemo5 which shadows the 
> one in
>>>  > /etc/qconfig-maemo5 and adds what you want. (Assuming the -add-qt 
> option
>>>  > described below would be implemented to find files like that, but 
> you get
>>>  > the idea).
>>  <snip>
>>  Just to review who *is* supposed to benefit from this:
>>  * Not Windows or Mac users. They are already managed by the user
> 
> Qt users on Widnows could use such qmake to manage their Qt
> installations. Have no clue about the Mac users, though.
> My proposition was to not install this new qmake wrapper by default
> iff libexecdir equals to bindir - so the old behavior could be
> achieved easily.

Windows users don't need to do anything. They already have:

1. The Command-line Short-cut on the Start Menu to access specific environments.
2. The Visual Studio Plug-in which allows one to change between versions from with VS.

If you use the plug-in, then no need to run qmake at all - it does it for you.
I've had issues with the plug-in, and have several projects (main + dependencies) that need to be built utilizing separate PRO files, under both Linux and Windows so I don't use the plug-in.

Ben