On Thu, 2016-12-01 at 16:29 +0100, Jason H wrote:
> The rest of these are less critical, but could cause problems:
> 2. When I did the import the shadow build directory was:
> however it was really /Users/jhihn/Projects/build-prep-
> iphonesimulator_clang_Qt_5_6_2_ios-Debug (No _for_ in the path)
When importing the directory should be exactly the one you had before: If it is
not, then that is not a import, it is a new build directory using the old kit.
> 3. My import of desktop wound up with a build directory of
> /Users/jhihn/Projects/build-prep-Qt_5_6_2_clang_64_temporary-Debug. What's
> temporary doing in there?)
The importer creates "temporary" kits if it finds some combination of Qt,
compiler and whatnot that no existing kit covers. These kits will only get
properly added once you actually use them.
But again, that is no import if the build directory differs, as it probably does
> 4. It would be nice if (tm) the import could also figure out the other
> platforms and do all of that in one step.
It does scan for builds of the source directory in the parent of your default
build directory. So it should do exactly what you are asking for.
Note that the project importing should not have changed since it was updated in
4.0, so I am a bit surprised you report that now:-).
How about filing bugs about your issues? They do get lost when reported only
Tobias Hunger, Senior Software Engineer | The Qt Company
The Qt Company GmbH, Rudower Chaussee 13, D-12489 Berlin
Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho. Sitz der
Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B
Qt-creator mailing list