2019-10-11 13:13:48 +00:00
|
|
|
type: Group
|
|
|
|
|
instructions:
|
|
|
|
|
- type: MakeDirectory
|
|
|
|
|
directory: .git
|
|
|
|
|
- type: MakeDirectory
|
|
|
|
|
directory: build
|
|
|
|
|
- type: ChangeDirectory
|
|
|
|
|
directory: "{{.BuildDir}}/build"
|
|
|
|
|
- type: MakeDirectory
|
|
|
|
|
directory: target
|
2020-05-27 13:24:24 +00:00
|
|
|
- type: Group
|
|
|
|
|
instructions:
|
|
|
|
|
- type: MakeDirectory
|
|
|
|
|
directory: host
|
|
|
|
|
- type: SetBuildDirectory
|
|
|
|
|
directory: "{{.SourceDir}}/build/host"
|
|
|
|
|
- type: ChangeDirectory
|
|
|
|
|
directory: "{{.BuildDir}}"
|
coin: Use configure and qt-configure-module in instructions
We want to use configure and qt-configure-module when building in
Coin, rather than pure cmake and qt-cmake.
There are a few benefits:
- CI tests the scripts, making sure we don't introduce regressions
- CI uses the same scripts that we mention in our documentation for
developers to use
- The platform configurations become a bit less verbose and easier to
read due to less shouty-case CMake options
To ensure a more gradual porting, Coin will only use the new
instructions if the 'UseConfigure' feature is set on a platform
configuration in qt5.git. This allows going back to the old
instructions in case if something isn't working properly.
Due the opt-in, we need to support both old and new instructions in
the implementation.
The change strives to remove as much duplicate code as possible,
by moving it into common includes.
The README.md is updated to mention the overview of how the different
environment variables are used.
There are a few important things to point out.
1) Because during the porting we have to allow mixing of the old style
and new style, platform configs have to separate CMake-style options
from configure-style options in different environment variables.
Otherwise the instructions wouldn't be able to create a valid
configure call, where all CMake-style options have to go at the end
after a double dash --.
After all platform configs are ported to the new style, it should be
possible to combine all the options in a single environment variable
if that is desired, but it will require another round of porting to
remove all the '-D' prefixes in CMake-style options, and just use
regular variable assignment which configure supports.
e.g. -DQT_BUILD_EXAMPLES=ON becomes QT_BUILD_EXAMPLES=ON, which can be
mixed in-between configure-style args.
2) Configure is more strict in that it doesn't allow passing
unknown options. Due to that, we can't pass non-qtbase configure
options via NON_QTBASE_CONFIGURE_ARGS. qt-configure-module would
error out in the repos where the configure option is unknown.
Because we don't have a Coin configure variable for each repo,
we circumvent the issue by continuing to pass CMake-style options via
NON_QTBASE_CMAKE_ARGS instead, which does not do validation checks.
In the future, we could introduce a configure flag that disables
the validation checks.
Pick-to: 6.2 6.3
Task-number: QTQAINFRA-4357
Task-number: QTQAINFRA-4815
Change-Id: I72d8ba0b3a543b42982e22ae8d6566c0e885c446
Reviewed-by: Jörg Bornemann <joerg.bornemann@qt.io>
Reviewed-by: Toni Saario <toni.saario@qt.io>
2022-02-15 12:59:33 +00:00
|
|
|
|
|
|
|
|
- type: EnvironmentVariable
|
|
|
|
|
variableName: COIN_CONFIGURE_ARGS
|
|
|
|
|
variableValue: "{{.Env.CONFIGURE_ARGS}}"
|
|
|
|
|
- type: EnvironmentVariable
|
|
|
|
|
variableName: COIN_CMAKE_ARGS
|
|
|
|
|
# Use unix separators even on Windows, to avoid escaping issues the in configure script.
|
|
|
|
|
variableValue: "{{.Env.CMAKE_ARGS}} {{.Env.COMMON_CMAKE_ARGS}} -DCMAKE_INSTALL_PREFIX:PATH={{unixPathSeparators .InstallDir}}/host"
|
|
|
|
|
- type: EnvironmentVariable
|
|
|
|
|
variableName: CONFIGURE_ENV_PREFIX
|
|
|
|
|
variableValue: "{{.Env.ENV_PREFIX}}"
|
|
|
|
|
- !include "{{qt/qtbase}}/call_configure_qtbase.yaml"
|
|
|
|
|
|
2020-05-27 13:24:24 +00:00
|
|
|
- type: ExecuteCommand
|
coin: Use configure and qt-configure-module in instructions
We want to use configure and qt-configure-module when building in
Coin, rather than pure cmake and qt-cmake.
There are a few benefits:
- CI tests the scripts, making sure we don't introduce regressions
- CI uses the same scripts that we mention in our documentation for
developers to use
- The platform configurations become a bit less verbose and easier to
read due to less shouty-case CMake options
To ensure a more gradual porting, Coin will only use the new
instructions if the 'UseConfigure' feature is set on a platform
configuration in qt5.git. This allows going back to the old
instructions in case if something isn't working properly.
Due the opt-in, we need to support both old and new instructions in
the implementation.
The change strives to remove as much duplicate code as possible,
by moving it into common includes.
The README.md is updated to mention the overview of how the different
environment variables are used.
There are a few important things to point out.
1) Because during the porting we have to allow mixing of the old style
and new style, platform configs have to separate CMake-style options
from configure-style options in different environment variables.
Otherwise the instructions wouldn't be able to create a valid
configure call, where all CMake-style options have to go at the end
after a double dash --.
After all platform configs are ported to the new style, it should be
possible to combine all the options in a single environment variable
if that is desired, but it will require another round of porting to
remove all the '-D' prefixes in CMake-style options, and just use
regular variable assignment which configure supports.
e.g. -DQT_BUILD_EXAMPLES=ON becomes QT_BUILD_EXAMPLES=ON, which can be
mixed in-between configure-style args.
2) Configure is more strict in that it doesn't allow passing
unknown options. Due to that, we can't pass non-qtbase configure
options via NON_QTBASE_CONFIGURE_ARGS. qt-configure-module would
error out in the repos where the configure option is unknown.
Because we don't have a Coin configure variable for each repo,
we circumvent the issue by continuing to pass CMake-style options via
NON_QTBASE_CMAKE_ARGS instead, which does not do validation checks.
In the future, we could introduce a configure flag that disables
the validation checks.
Pick-to: 6.2 6.3
Task-number: QTQAINFRA-4357
Task-number: QTQAINFRA-4815
Change-Id: I72d8ba0b3a543b42982e22ae8d6566c0e885c446
Reviewed-by: Jörg Bornemann <joerg.bornemann@qt.io>
Reviewed-by: Toni Saario <toni.saario@qt.io>
2022-02-15 12:59:33 +00:00
|
|
|
command: "{{.Env.CONFIGURE_ENV_PREFIX}} cmake --build . --parallel -v"
|
2020-05-27 13:24:24 +00:00
|
|
|
maxTimeInSeconds: 6000
|
2021-11-15 12:19:38 +00:00
|
|
|
maxTimeBetweenOutput: 4800
|
2020-05-27 13:24:24 +00:00
|
|
|
userMessageOnFailure: >
|
2022-03-17 07:26:16 +00:00
|
|
|
Failed to build sources.
|
2020-05-27 13:24:24 +00:00
|
|
|
- type: EnvironmentVariable
|
Move Some of the Private CMake Helper Scripts from `bin/` to `libexec/`
After this change, private CMake scripts are mostly live in
`libexec/`, except the `qt-cmake` which will stay in `bin/`.
This doesn't affect the Windows configuration.
- `qt-cmake` stays in `bin/`
- `qt-configure-module` moves into `libexec/`
- `qt-cmake-private` moves into `libexec/`
- `qt-cmake-private-install.cmake` moves into `libexec/`
- `qt-cmake-standalone-test` moves into `libexec/`
- `qt-internal-configure-test` moves into `libexec/`
In cases where `QT_GENERATE_WRAPPER_SCRIPTS_FOR_ALL_HOSTS` is set to
ON, e.g., ANDROID, WASM, both Batch and Bash files will be generated
and placed in `bin/` and `libexec/` accordingly; in both cases,
qt-cmake and qt-cmake.bat will be in `bin/` anyway.
[ChangeLog][CMake] The private Qt CMake scripts, i.e.,
qt-configure-module, qt-cmake-private, qt-cmake-private-install.cmake,
qt-cmake-standalone-test and qt-internal-configure-test were moved
into $prefix/libexec on Unix platforms.
Fixes: QTBUG-107621
Change-Id: Ic4f4ec85f64d2ede0e208bca928959e30be906a6
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
2022-10-17 13:50:18 +00:00
|
|
|
variableName: COIN_CMAKE_BUILD_DIR
|
2020-05-27 13:24:24 +00:00
|
|
|
variableValue: "{{.BuildDir}}"
|
Move Some of the Private CMake Helper Scripts from `bin/` to `libexec/`
After this change, private CMake scripts are mostly live in
`libexec/`, except the `qt-cmake` which will stay in `bin/`.
This doesn't affect the Windows configuration.
- `qt-cmake` stays in `bin/`
- `qt-configure-module` moves into `libexec/`
- `qt-cmake-private` moves into `libexec/`
- `qt-cmake-private-install.cmake` moves into `libexec/`
- `qt-cmake-standalone-test` moves into `libexec/`
- `qt-internal-configure-test` moves into `libexec/`
In cases where `QT_GENERATE_WRAPPER_SCRIPTS_FOR_ALL_HOSTS` is set to
ON, e.g., ANDROID, WASM, both Batch and Bash files will be generated
and placed in `bin/` and `libexec/` accordingly; in both cases,
qt-cmake and qt-cmake.bat will be in `bin/` anyway.
[ChangeLog][CMake] The private Qt CMake scripts, i.e.,
qt-configure-module, qt-cmake-private, qt-cmake-private-install.cmake,
qt-cmake-standalone-test and qt-internal-configure-test were moved
into $prefix/libexec on Unix platforms.
Fixes: QTBUG-107621
Change-Id: Ic4f4ec85f64d2ede0e208bca928959e30be906a6
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
2022-10-17 13:50:18 +00:00
|
|
|
- type: EnvironmentVariable
|
|
|
|
|
variableName: COIN_CMAKE_BUILD_LIBEXEC_DIR
|
|
|
|
|
variableValue: "{{.BuildDir}}{{.Env.CI_PATH_SEP}}libexec"
|
|
|
|
|
disable_if:
|
|
|
|
|
condition: and
|
|
|
|
|
conditions:
|
|
|
|
|
- condition: property
|
|
|
|
|
property: host.os
|
|
|
|
|
equals_value: Windows
|
|
|
|
|
- condition: property
|
|
|
|
|
property: target.osVersion
|
|
|
|
|
not_in_values: [WebAssembly, Android_ANY]
|
|
|
|
|
- type: EnvironmentVariable
|
|
|
|
|
variableName: COIN_CMAKE_BUILD_LIBEXEC_DIR
|
|
|
|
|
variableValue: "{{.BuildDir}}{{.Env.CI_PATH_SEP}}bin"
|
|
|
|
|
enable_if:
|
|
|
|
|
condition: and
|
|
|
|
|
conditions:
|
|
|
|
|
- condition: property
|
|
|
|
|
property: host.os
|
|
|
|
|
equals_value: Windows
|
|
|
|
|
- condition: property
|
|
|
|
|
property: target.osVersion
|
|
|
|
|
not_in_values: [WebAssembly, Android_ANY]
|
2020-05-27 13:24:24 +00:00
|
|
|
- !include "{{qt/qtbase}}/call_host_install.yaml"
|
|
|
|
|
- type: EnvironmentVariable
|
|
|
|
|
variableName: DESTDIR
|
|
|
|
|
variableValue: "{{.InstallRoot}}"
|
|
|
|
|
- !include "{{qt/qtbase}}/call_host_install.yaml"
|
|
|
|
|
enable_if:
|
|
|
|
|
condition: property
|
|
|
|
|
property: platformDependency
|
|
|
|
|
equals_value: null
|
2019-11-14 10:51:11 +00:00
|
|
|
- type: EnvironmentVariable
|
|
|
|
|
variableName: DESTDIR
|
|
|
|
|
variableValue: ""
|
2019-10-11 13:13:48 +00:00
|
|
|
- type: SetBuildDirectory
|
|
|
|
|
directory: "{{.SourceDir}}/build/target"
|
|
|
|
|
- type: ChangeDirectory
|
|
|
|
|
directory: "{{.BuildDir}}"
|
coin: Use configure and qt-configure-module in instructions
We want to use configure and qt-configure-module when building in
Coin, rather than pure cmake and qt-cmake.
There are a few benefits:
- CI tests the scripts, making sure we don't introduce regressions
- CI uses the same scripts that we mention in our documentation for
developers to use
- The platform configurations become a bit less verbose and easier to
read due to less shouty-case CMake options
To ensure a more gradual porting, Coin will only use the new
instructions if the 'UseConfigure' feature is set on a platform
configuration in qt5.git. This allows going back to the old
instructions in case if something isn't working properly.
Due the opt-in, we need to support both old and new instructions in
the implementation.
The change strives to remove as much duplicate code as possible,
by moving it into common includes.
The README.md is updated to mention the overview of how the different
environment variables are used.
There are a few important things to point out.
1) Because during the porting we have to allow mixing of the old style
and new style, platform configs have to separate CMake-style options
from configure-style options in different environment variables.
Otherwise the instructions wouldn't be able to create a valid
configure call, where all CMake-style options have to go at the end
after a double dash --.
After all platform configs are ported to the new style, it should be
possible to combine all the options in a single environment variable
if that is desired, but it will require another round of porting to
remove all the '-D' prefixes in CMake-style options, and just use
regular variable assignment which configure supports.
e.g. -DQT_BUILD_EXAMPLES=ON becomes QT_BUILD_EXAMPLES=ON, which can be
mixed in-between configure-style args.
2) Configure is more strict in that it doesn't allow passing
unknown options. Due to that, we can't pass non-qtbase configure
options via NON_QTBASE_CONFIGURE_ARGS. qt-configure-module would
error out in the repos where the configure option is unknown.
Because we don't have a Coin configure variable for each repo,
we circumvent the issue by continuing to pass CMake-style options via
NON_QTBASE_CMAKE_ARGS instead, which does not do validation checks.
In the future, we could introduce a configure flag that disables
the validation checks.
Pick-to: 6.2 6.3
Task-number: QTQAINFRA-4357
Task-number: QTQAINFRA-4815
Change-Id: I72d8ba0b3a543b42982e22ae8d6566c0e885c446
Reviewed-by: Jörg Bornemann <joerg.bornemann@qt.io>
Reviewed-by: Toni Saario <toni.saario@qt.io>
2022-02-15 12:59:33 +00:00
|
|
|
|
2020-05-27 13:24:24 +00:00
|
|
|
- type: AppendToEnvironmentVariable
|
coin: Use configure and qt-configure-module in instructions
We want to use configure and qt-configure-module when building in
Coin, rather than pure cmake and qt-cmake.
There are a few benefits:
- CI tests the scripts, making sure we don't introduce regressions
- CI uses the same scripts that we mention in our documentation for
developers to use
- The platform configurations become a bit less verbose and easier to
read due to less shouty-case CMake options
To ensure a more gradual porting, Coin will only use the new
instructions if the 'UseConfigure' feature is set on a platform
configuration in qt5.git. This allows going back to the old
instructions in case if something isn't working properly.
Due the opt-in, we need to support both old and new instructions in
the implementation.
The change strives to remove as much duplicate code as possible,
by moving it into common includes.
The README.md is updated to mention the overview of how the different
environment variables are used.
There are a few important things to point out.
1) Because during the porting we have to allow mixing of the old style
and new style, platform configs have to separate CMake-style options
from configure-style options in different environment variables.
Otherwise the instructions wouldn't be able to create a valid
configure call, where all CMake-style options have to go at the end
after a double dash --.
After all platform configs are ported to the new style, it should be
possible to combine all the options in a single environment variable
if that is desired, but it will require another round of porting to
remove all the '-D' prefixes in CMake-style options, and just use
regular variable assignment which configure supports.
e.g. -DQT_BUILD_EXAMPLES=ON becomes QT_BUILD_EXAMPLES=ON, which can be
mixed in-between configure-style args.
2) Configure is more strict in that it doesn't allow passing
unknown options. Due to that, we can't pass non-qtbase configure
options via NON_QTBASE_CONFIGURE_ARGS. qt-configure-module would
error out in the repos where the configure option is unknown.
Because we don't have a Coin configure variable for each repo,
we circumvent the issue by continuing to pass CMake-style options via
NON_QTBASE_CMAKE_ARGS instead, which does not do validation checks.
In the future, we could introduce a configure flag that disables
the validation checks.
Pick-to: 6.2 6.3
Task-number: QTQAINFRA-4357
Task-number: QTQAINFRA-4815
Change-Id: I72d8ba0b3a543b42982e22ae8d6566c0e885c446
Reviewed-by: Jörg Bornemann <joerg.bornemann@qt.io>
Reviewed-by: Toni Saario <toni.saario@qt.io>
2022-02-15 12:59:33 +00:00
|
|
|
variableName: TARGET_CMAKE_ARGS
|
2020-05-27 13:24:24 +00:00
|
|
|
variableValue: " -DQT_HOST_PATH={{.AgentWorkingDir}}/install"
|
|
|
|
|
disable_if:
|
|
|
|
|
condition: property
|
|
|
|
|
property: platformDependency
|
|
|
|
|
equals_value: null
|
|
|
|
|
- type: AppendToEnvironmentVariable
|
coin: Use configure and qt-configure-module in instructions
We want to use configure and qt-configure-module when building in
Coin, rather than pure cmake and qt-cmake.
There are a few benefits:
- CI tests the scripts, making sure we don't introduce regressions
- CI uses the same scripts that we mention in our documentation for
developers to use
- The platform configurations become a bit less verbose and easier to
read due to less shouty-case CMake options
To ensure a more gradual porting, Coin will only use the new
instructions if the 'UseConfigure' feature is set on a platform
configuration in qt5.git. This allows going back to the old
instructions in case if something isn't working properly.
Due the opt-in, we need to support both old and new instructions in
the implementation.
The change strives to remove as much duplicate code as possible,
by moving it into common includes.
The README.md is updated to mention the overview of how the different
environment variables are used.
There are a few important things to point out.
1) Because during the porting we have to allow mixing of the old style
and new style, platform configs have to separate CMake-style options
from configure-style options in different environment variables.
Otherwise the instructions wouldn't be able to create a valid
configure call, where all CMake-style options have to go at the end
after a double dash --.
After all platform configs are ported to the new style, it should be
possible to combine all the options in a single environment variable
if that is desired, but it will require another round of porting to
remove all the '-D' prefixes in CMake-style options, and just use
regular variable assignment which configure supports.
e.g. -DQT_BUILD_EXAMPLES=ON becomes QT_BUILD_EXAMPLES=ON, which can be
mixed in-between configure-style args.
2) Configure is more strict in that it doesn't allow passing
unknown options. Due to that, we can't pass non-qtbase configure
options via NON_QTBASE_CONFIGURE_ARGS. qt-configure-module would
error out in the repos where the configure option is unknown.
Because we don't have a Coin configure variable for each repo,
we circumvent the issue by continuing to pass CMake-style options via
NON_QTBASE_CMAKE_ARGS instead, which does not do validation checks.
In the future, we could introduce a configure flag that disables
the validation checks.
Pick-to: 6.2 6.3
Task-number: QTQAINFRA-4357
Task-number: QTQAINFRA-4815
Change-Id: I72d8ba0b3a543b42982e22ae8d6566c0e885c446
Reviewed-by: Jörg Bornemann <joerg.bornemann@qt.io>
Reviewed-by: Toni Saario <toni.saario@qt.io>
2022-02-15 12:59:33 +00:00
|
|
|
variableName: TARGET_CMAKE_ARGS
|
2020-05-27 13:24:24 +00:00
|
|
|
variableValue: " -DQT_HOST_PATH={{.InstallDir}}/host"
|
|
|
|
|
enable_if:
|
|
|
|
|
condition: property
|
|
|
|
|
property: platformDependency
|
|
|
|
|
equals_value: null
|
coin: Use configure and qt-configure-module in instructions
We want to use configure and qt-configure-module when building in
Coin, rather than pure cmake and qt-cmake.
There are a few benefits:
- CI tests the scripts, making sure we don't introduce regressions
- CI uses the same scripts that we mention in our documentation for
developers to use
- The platform configurations become a bit less verbose and easier to
read due to less shouty-case CMake options
To ensure a more gradual porting, Coin will only use the new
instructions if the 'UseConfigure' feature is set on a platform
configuration in qt5.git. This allows going back to the old
instructions in case if something isn't working properly.
Due the opt-in, we need to support both old and new instructions in
the implementation.
The change strives to remove as much duplicate code as possible,
by moving it into common includes.
The README.md is updated to mention the overview of how the different
environment variables are used.
There are a few important things to point out.
1) Because during the porting we have to allow mixing of the old style
and new style, platform configs have to separate CMake-style options
from configure-style options in different environment variables.
Otherwise the instructions wouldn't be able to create a valid
configure call, where all CMake-style options have to go at the end
after a double dash --.
After all platform configs are ported to the new style, it should be
possible to combine all the options in a single environment variable
if that is desired, but it will require another round of porting to
remove all the '-D' prefixes in CMake-style options, and just use
regular variable assignment which configure supports.
e.g. -DQT_BUILD_EXAMPLES=ON becomes QT_BUILD_EXAMPLES=ON, which can be
mixed in-between configure-style args.
2) Configure is more strict in that it doesn't allow passing
unknown options. Due to that, we can't pass non-qtbase configure
options via NON_QTBASE_CONFIGURE_ARGS. qt-configure-module would
error out in the repos where the configure option is unknown.
Because we don't have a Coin configure variable for each repo,
we circumvent the issue by continuing to pass CMake-style options via
NON_QTBASE_CMAKE_ARGS instead, which does not do validation checks.
In the future, we could introduce a configure flag that disables
the validation checks.
Pick-to: 6.2 6.3
Task-number: QTQAINFRA-4357
Task-number: QTQAINFRA-4815
Change-Id: I72d8ba0b3a543b42982e22ae8d6566c0e885c446
Reviewed-by: Jörg Bornemann <joerg.bornemann@qt.io>
Reviewed-by: Toni Saario <toni.saario@qt.io>
2022-02-15 12:59:33 +00:00
|
|
|
|
|
|
|
|
- type: EnvironmentVariable
|
|
|
|
|
variableName: COIN_CONFIGURE_ARGS
|
|
|
|
|
variableValue: "{{.Env.TARGET_CONFIGURE_ARGS}}"
|
|
|
|
|
- type: EnvironmentVariable
|
|
|
|
|
variableName: COIN_CMAKE_ARGS
|
|
|
|
|
# Use unix separators even on Windows, to avoid escaping issues in the configure script.
|
2022-03-29 06:48:44 +00:00
|
|
|
variableValue: "{{.Env.TARGET_CMAKE_ARGS}} {{.Env.COMMON_TARGET_CMAKE_ARGS}} -DCMAKE_STAGING_PREFIX:PATH={{unixPathSeparators .InstallDir}}/target"
|
coin: Use configure and qt-configure-module in instructions
We want to use configure and qt-configure-module when building in
Coin, rather than pure cmake and qt-cmake.
There are a few benefits:
- CI tests the scripts, making sure we don't introduce regressions
- CI uses the same scripts that we mention in our documentation for
developers to use
- The platform configurations become a bit less verbose and easier to
read due to less shouty-case CMake options
To ensure a more gradual porting, Coin will only use the new
instructions if the 'UseConfigure' feature is set on a platform
configuration in qt5.git. This allows going back to the old
instructions in case if something isn't working properly.
Due the opt-in, we need to support both old and new instructions in
the implementation.
The change strives to remove as much duplicate code as possible,
by moving it into common includes.
The README.md is updated to mention the overview of how the different
environment variables are used.
There are a few important things to point out.
1) Because during the porting we have to allow mixing of the old style
and new style, platform configs have to separate CMake-style options
from configure-style options in different environment variables.
Otherwise the instructions wouldn't be able to create a valid
configure call, where all CMake-style options have to go at the end
after a double dash --.
After all platform configs are ported to the new style, it should be
possible to combine all the options in a single environment variable
if that is desired, but it will require another round of porting to
remove all the '-D' prefixes in CMake-style options, and just use
regular variable assignment which configure supports.
e.g. -DQT_BUILD_EXAMPLES=ON becomes QT_BUILD_EXAMPLES=ON, which can be
mixed in-between configure-style args.
2) Configure is more strict in that it doesn't allow passing
unknown options. Due to that, we can't pass non-qtbase configure
options via NON_QTBASE_CONFIGURE_ARGS. qt-configure-module would
error out in the repos where the configure option is unknown.
Because we don't have a Coin configure variable for each repo,
we circumvent the issue by continuing to pass CMake-style options via
NON_QTBASE_CMAKE_ARGS instead, which does not do validation checks.
In the future, we could introduce a configure flag that disables
the validation checks.
Pick-to: 6.2 6.3
Task-number: QTQAINFRA-4357
Task-number: QTQAINFRA-4815
Change-Id: I72d8ba0b3a543b42982e22ae8d6566c0e885c446
Reviewed-by: Jörg Bornemann <joerg.bornemann@qt.io>
Reviewed-by: Toni Saario <toni.saario@qt.io>
2022-02-15 12:59:33 +00:00
|
|
|
- type: EnvironmentVariable
|
|
|
|
|
variableName: CONFIGURE_ENV_PREFIX
|
|
|
|
|
variableValue: "{{.Env.TARGET_ENV_PREFIX}}"
|
|
|
|
|
- !include "{{qt/qtbase}}/call_configure_qtbase.yaml"
|
|
|
|
|
|
2019-10-11 13:13:48 +00:00
|
|
|
- type: ExecuteCommand
|
coin: Use configure and qt-configure-module in instructions
We want to use configure and qt-configure-module when building in
Coin, rather than pure cmake and qt-cmake.
There are a few benefits:
- CI tests the scripts, making sure we don't introduce regressions
- CI uses the same scripts that we mention in our documentation for
developers to use
- The platform configurations become a bit less verbose and easier to
read due to less shouty-case CMake options
To ensure a more gradual porting, Coin will only use the new
instructions if the 'UseConfigure' feature is set on a platform
configuration in qt5.git. This allows going back to the old
instructions in case if something isn't working properly.
Due the opt-in, we need to support both old and new instructions in
the implementation.
The change strives to remove as much duplicate code as possible,
by moving it into common includes.
The README.md is updated to mention the overview of how the different
environment variables are used.
There are a few important things to point out.
1) Because during the porting we have to allow mixing of the old style
and new style, platform configs have to separate CMake-style options
from configure-style options in different environment variables.
Otherwise the instructions wouldn't be able to create a valid
configure call, where all CMake-style options have to go at the end
after a double dash --.
After all platform configs are ported to the new style, it should be
possible to combine all the options in a single environment variable
if that is desired, but it will require another round of porting to
remove all the '-D' prefixes in CMake-style options, and just use
regular variable assignment which configure supports.
e.g. -DQT_BUILD_EXAMPLES=ON becomes QT_BUILD_EXAMPLES=ON, which can be
mixed in-between configure-style args.
2) Configure is more strict in that it doesn't allow passing
unknown options. Due to that, we can't pass non-qtbase configure
options via NON_QTBASE_CONFIGURE_ARGS. qt-configure-module would
error out in the repos where the configure option is unknown.
Because we don't have a Coin configure variable for each repo,
we circumvent the issue by continuing to pass CMake-style options via
NON_QTBASE_CMAKE_ARGS instead, which does not do validation checks.
In the future, we could introduce a configure flag that disables
the validation checks.
Pick-to: 6.2 6.3
Task-number: QTQAINFRA-4357
Task-number: QTQAINFRA-4815
Change-Id: I72d8ba0b3a543b42982e22ae8d6566c0e885c446
Reviewed-by: Jörg Bornemann <joerg.bornemann@qt.io>
Reviewed-by: Toni Saario <toni.saario@qt.io>
2022-02-15 12:59:33 +00:00
|
|
|
command: "{{.Env.CONFIGURE_ENV_PREFIX}} cmake --build . --parallel -v"
|
2019-10-11 13:13:48 +00:00
|
|
|
maxTimeInSeconds: 6000
|
2021-11-15 12:19:38 +00:00
|
|
|
maxTimeBetweenOutput: 4800
|
2019-10-11 13:13:48 +00:00
|
|
|
userMessageOnFailure: >
|
2022-03-17 07:26:16 +00:00
|
|
|
Failed to build sources.
|
2020-05-15 09:38:53 +00:00
|
|
|
- type: EnvironmentVariable
|
Move Some of the Private CMake Helper Scripts from `bin/` to `libexec/`
After this change, private CMake scripts are mostly live in
`libexec/`, except the `qt-cmake` which will stay in `bin/`.
This doesn't affect the Windows configuration.
- `qt-cmake` stays in `bin/`
- `qt-configure-module` moves into `libexec/`
- `qt-cmake-private` moves into `libexec/`
- `qt-cmake-private-install.cmake` moves into `libexec/`
- `qt-cmake-standalone-test` moves into `libexec/`
- `qt-internal-configure-test` moves into `libexec/`
In cases where `QT_GENERATE_WRAPPER_SCRIPTS_FOR_ALL_HOSTS` is set to
ON, e.g., ANDROID, WASM, both Batch and Bash files will be generated
and placed in `bin/` and `libexec/` accordingly; in both cases,
qt-cmake and qt-cmake.bat will be in `bin/` anyway.
[ChangeLog][CMake] The private Qt CMake scripts, i.e.,
qt-configure-module, qt-cmake-private, qt-cmake-private-install.cmake,
qt-cmake-standalone-test and qt-internal-configure-test were moved
into $prefix/libexec on Unix platforms.
Fixes: QTBUG-107621
Change-Id: Ic4f4ec85f64d2ede0e208bca928959e30be906a6
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
2022-10-17 13:50:18 +00:00
|
|
|
variableName: COIN_CMAKE_BUILD_DIR
|
2020-05-15 09:38:53 +00:00
|
|
|
variableValue: "{{.BuildDir}}"
|
Move Some of the Private CMake Helper Scripts from `bin/` to `libexec/`
After this change, private CMake scripts are mostly live in
`libexec/`, except the `qt-cmake` which will stay in `bin/`.
This doesn't affect the Windows configuration.
- `qt-cmake` stays in `bin/`
- `qt-configure-module` moves into `libexec/`
- `qt-cmake-private` moves into `libexec/`
- `qt-cmake-private-install.cmake` moves into `libexec/`
- `qt-cmake-standalone-test` moves into `libexec/`
- `qt-internal-configure-test` moves into `libexec/`
In cases where `QT_GENERATE_WRAPPER_SCRIPTS_FOR_ALL_HOSTS` is set to
ON, e.g., ANDROID, WASM, both Batch and Bash files will be generated
and placed in `bin/` and `libexec/` accordingly; in both cases,
qt-cmake and qt-cmake.bat will be in `bin/` anyway.
[ChangeLog][CMake] The private Qt CMake scripts, i.e.,
qt-configure-module, qt-cmake-private, qt-cmake-private-install.cmake,
qt-cmake-standalone-test and qt-internal-configure-test were moved
into $prefix/libexec on Unix platforms.
Fixes: QTBUG-107621
Change-Id: Ic4f4ec85f64d2ede0e208bca928959e30be906a6
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
2022-10-17 13:50:18 +00:00
|
|
|
- type: EnvironmentVariable
|
|
|
|
|
variableName: COIN_CMAKE_BUILD_LIBEXEC_DIR
|
|
|
|
|
variableValue: "{{.Env.COIN_CMAKE_BUILD_DIR}}{{.Env.CI_PATH_SEP}}libexec"
|
|
|
|
|
disable_if:
|
|
|
|
|
condition: and
|
|
|
|
|
conditions:
|
|
|
|
|
- condition: property
|
|
|
|
|
property: host.os
|
|
|
|
|
equals_value: Windows
|
|
|
|
|
- condition: property
|
|
|
|
|
property: target.osVersion
|
|
|
|
|
not_in_values: [WebAssembly, Android_ANY]
|
|
|
|
|
- type: EnvironmentVariable
|
|
|
|
|
variableName: COIN_CMAKE_BUILD_LIBEXEC_DIR
|
|
|
|
|
variableValue: "{{.Env.COIN_CMAKE_BUILD_DIR}}{{.Env.CI_PATH_SEP}}bin"
|
|
|
|
|
enable_if:
|
|
|
|
|
condition: and
|
|
|
|
|
conditions:
|
|
|
|
|
- condition: property
|
|
|
|
|
property: host.os
|
|
|
|
|
equals_value: Windows
|
|
|
|
|
- condition: property
|
|
|
|
|
property: target.osVersion
|
|
|
|
|
not_in_values: [WebAssembly, Android_ANY]
|
2020-05-15 09:38:53 +00:00
|
|
|
- !include "{{qt/qtbase}}/call_target_install.yaml"
|
2019-11-14 10:51:11 +00:00
|
|
|
- type: EnvironmentVariable
|
|
|
|
|
variableName: DESTDIR
|
|
|
|
|
variableValue: "{{.InstallRoot}}"
|
2020-05-15 09:38:53 +00:00
|
|
|
- !include "{{qt/qtbase}}/call_target_install.yaml"
|
2019-11-14 10:51:11 +00:00
|
|
|
- type: EnvironmentVariable
|
|
|
|
|
variableName: DESTDIR
|
|
|
|
|
variableValue: ""
|
|
|
|
|
- type: UploadArtifact
|
|
|
|
|
archiveDirectory: "{{.InstallRoot}}/{{.AgentWorkingDir}}"
|
|
|
|
|
transferType: UploadModuleBuildArtifact
|
|
|
|
|
maxTimeInSeconds: 1200
|
|
|
|
|
maxTimeBetweenOutput: 1200
|
2020-08-18 16:13:03 +00:00
|
|
|
- type: EnvironmentVariable
|
|
|
|
|
variableName: COIN_CONFIG_TYPE
|
|
|
|
|
variableValue: "Target"
|
|
|
|
|
- !include "{{qt/qtbase}}/qmake/get_qmake_location_target.yaml"
|
|
|
|
|
- !include "{{qt/qtbase}}/qmake_examples/build_qmake_examples_instructions.yaml"
|
