[Qt-interest] Qt Visual Studio plugin doesn't honor paths on import

[David Ching]

FWIW, I sympathize with Robert.  It's just not easy enough to maintain both
.pro and .vcproj simultaneously.  Best I've done is edit my .pro file (which
is necessary for non-Windows development anyway, as well as those using Qt
Creator for Windows) and re-import, but then I need to redo the settings
after the re-import because it is not a 100% conversion.  In the end, I
established a policy that said, "going forward, all Windows development will
be done using Visual Studio projects and not the .pro file anymore."  This
worked because all the Windows developers far preferred Visual Studio to Qt
Creator and only used Qt Creator on non-Windows anyway.  But as QML becomes
more and more used, Qt Creator does have distinct advantages now, even for
Windows....

-- David


"Joerg Bornemann" <joerg.bornemann at nokia.com> wrote in message
news:<4E93F5F9.4070301 at nokia.com>...
> On 11/10/11 08:56, ext Schimkowitsch Robert wrote:
> 
> >> "The actual question is: why would they care where generated files are
placed?"
> >
> > Because (as per default settings) they clutter up folders that should
only contain source files. That can be changed, but every user has to
manually change the settings. They might have to change the settings for
different projects with different folder structures.
> 
> Generating files in a subfolder named "Generated Files" isn't really 
> cluttering the source directory. Also, you just can use out-of-source 
> builds.
> 
> > Because when I switch between command line and IDE build, I would use
different paths, which means a lot of duplicate files, and a lot of wasted
compile time.
> 
> Then don't switch between devenv and nmake.
> You can perfectly build your project by calling "devenv /build ..." on 
> the command line.
> 
> 
> Jörg