Skip to content

Conversation

@mirko
Copy link
Member

@mirko mirko commented May 8, 2025

Qt6 is a largely complex beast and given the experience from previous ports of Qt4 and Qt5, it will require quite some more work to accommodate all needs and configurations.

Qt6 kind of ditched support for qmake in favour of cmake, at least when it comes to building Qt6 and its official modules itself.

The qmake eco-system is and still needs to be supported though, as 3rd party projects are still allowed to use qmake - for the time being at least. qmake support for external projects untested for the time being, though.

Qt6 is a largely complex beast and given the experience from previous
ports of Qt4 and Qt5, it will require quite some more work to accommodate
all needs and configurations.

Qt6 kind of ditched support for qmake in favour of cmake, at least when
it comes to building Qt6 and its official modules itself.

The qmake eco-system is and still needs to be supported though, as 3rd
party projects are still allowed to use qmake - for the time being at
least.

Signed-off-by: Mirko Vogt <[email protected]>
@mirko mirko force-pushed the mirko/add-qt6base branch from c8e3a2f to 91254db Compare May 24, 2025 13:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant