This thread has been utterly useful, and thanks all for the input. May I
suggest, however, these tips get documented somehow (e.g. in the wiki)?
As it happens, what Eddy and Thiago wrote was truly a life saver for my
current poking into qtbase. Rebuilding the bootstrap lib invalidates
basically
> On 14 Jan 2022, at 11:44, Mitch Curtis wrote:
>
> This is the same situation I’m in. Would be nice if they were built when you
> hit run, but as a workaround I use Alt+B, Alt+R (from memory… I think that’s
> right):
>
> https://codereview.qt-project.org/c/qt-creator/qt-creator/+/330075
This is the same situation I’m in. Would be nice if they were built when you
hit run, but as a workaround I use Alt+B, Alt+R (from memory… I think that’s
right):
https://codereview.qt-project.org/c/qt-creator/qt-creator/+/330075
That way you can do that key combination and then Ctrl+R to run the
On 1/13/22 08:24, Eike Ziller wrote:
I.e. better use qt-configure-module to configure modules. That probably gets
some edge cases right, that aren’t covered by just qt-cmake-private.
The main reason for its existence are configure features.
For example:
$ ../qtbase/bin/qt-configure-module
>
> With the provision that I haven't looked inside qt-cmake-private what would
> be the difference from the qt-configure-module, which Arno suggested?
I didn’t realize qt-configure-module existed. Looks like that passes on some
configure options from the original / allows to pass configure
Thank you all for the insights!
On Sun, Jan 9, 2022 at 5:02 PM Arno Rehn wrote:
> I don't think that this is possible with CMake.
>
> I've been working around that by (re-)building only the module I'm
> working on with qtbase/bin/qt-configure-module in a seperate directory.
> That single-module
Am 11.01.2022 um 12:39 schrieb Edward Welbourne:
Arno Rehn (9 January 2022 15:59) wrote:
I'm skipping building the tests by default and would like
to build only a subset (the ones of the module I'm working on).
QtCreator doesn't seem to support EXCLUDE_FROM_ALL tests at all, so I
usually have
Arno Rehn (9 January 2022 15:59) wrote:
> I'm skipping building the tests by default and would like
> to build only a subset (the ones of the module I'm working on).
> QtCreator doesn't seem to support EXCLUDE_FROM_ALL tests at all, so I
> usually have to resort to the command line for that.
I
On Monday, 10 January 2022 06:02:43 PST Thiago Macieira wrote:
> The only problem is if you do the above, then you don't have qmake and you
> can't build qmake-based projects against your Qt build. You can get away
> with using the other build's qmake and then changing LD_LIBRARY_PATH to
> point
On Monday, 10 January 2022 00:10:54 PST Eike Ziller wrote:
> Accept that, and open the toplevel Qt project. Should work fine, and
> _because_ CMake does not recursively create subprojects, the incremental
> build with Ninja is very fast on the whole project. No recursive make
> involved.
Unless
Hi!
qmake actually creates a “subproject” per sub-.pro file, and these “subproject”
can be opened, built, run separately.
CMake works different, a build only consists of a single “project”, so it is
not possible to open “subprojects”.
The options, as I see them:
Accept that, and open the
On 09.01.22 12:47, Konstantin Shegunov wrote:
In the Qt5 times with qmake I was able to run the makefile generator on
the top of the Qt tree and then import build in Creator for some
specific module I'd wanted to work on. Is something like this still
possible for Qt6 and cmake (I'm currently
Hello,
In the Qt5 times with qmake I was able to run the makefile generator on the
top of the Qt tree and then import build in Creator for some specific
module I'd wanted to work on. Is something like this still possible for Qt6
and cmake (I'm currently using the default ninja generator)?
The
13 matches
Mail list logo
