[Qt-creator] How to keep ".." in default build directory

[Prav]

I want the "Default Build Directory" for new projects to be 
"..\Build\%{CurrentBuild:Name}"

By "Default Build Directory" I mean parameter in Options -> Build & Run -> 
General.

But unfortunately QtC replaces ".." with full folder name (wonder why there is 
this obtrusive service ... but never mind).
This forces me to put ".." back and delete full folder name in the begining.
For EVERY QtKit and EVERY Build-type! I am tied of this same task.


Is there a way/trick to somehow keep ".." inside Default Build Directory?


Thanks in advance!

___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Generating QtCreator cmake project for given CMakeLists.txt from command line

[René J . V . Bertin]

On Thursday June 02 2016 19:24:51 Konstantin Tokarev wrote:

> The next sequence have worked for me:
> 
> 1. Open CMakeLists.txt
> 2. Choose appropriate Kit from list, or create one if it is missing. Import 
> project
> 3. Go to project settings and switch build directory to the one which has 
> your configured build.

That works but only as long as Creator doesn't judge it necessary to rerun 
CMake.

It may work better to figure out what additional argument Creator needs (a 
priori the "Unix Makefiles - CodeBlocks" generator) and then run cmake as you 
want it in the build directory Creator is supposed to use?

R.
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Generating QtCreator cmake project for given CMakeLists.txt from command line

[Konstantin Tokarev]

02.06.2016, 19:07, "René J.V. Bertin" :
> Hi,
>
> Reviving an older thread after, well to honest, not having had a reason to 
> use Creator for a while ...
>
> So I updated to git/master, and discover that it's become even more 
> complicated to import a CMake-based project for which you already have a 
> (lengthy) cmake command line. Have I missed a place to input the commandline 
> "as is" during the import procedure, or does one really have to cut it up and 
> create the entries one by one through a WYSIAYG interface?

The next sequence have worked for me:

1. Open CMakeLists.txt
2. Choose appropriate Kit from list, or create one if it is missing. Import 
project
3. Go to project settings and switch build directory to the one which has your 
configured build.

-- 
Regards,
Konstantin
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Re: [Qt-creator] Generating QtCreator cmake project for given CMakeLists.txt from command line

[René J . V . Bertin]

Hi,

Reviving an older thread after, well to honest, not having had a reason to use 
Creator for a while ...

So I updated to git/master, and discover that it's become even more complicated 
to import a CMake-based project for which you already have a (lengthy) cmake 
command line. Have I missed a place to input the commandline "as is" during the 
import procedure, or does one really have to cut it up and create the entries 
one by one through a WYSIAYG interface?

R.
___
Qt-creator mailing list
Qt-creator@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator