Re: [Development] Configure command lines of official Qt releases
>> Thanks, Ivan. While this is true for other libs like xcb, Qt does not ship >> icu. It uses either the one provided by the system or a thin replacement >> resulting in a reduced localization feature set according to >> https://wiki.qt.io/Qt_5_ICU#Design_Principles > > Linux binaries are shipped with ICU. It's not possible to use system version, > because > ICU doesn't provide stable ABI. Good point. Indeed, libQtCore.so links to libicui18n.so.56 => /opt/Qt/5.12.3/gcc_64/lib/./libicui18n.so.56 (0x7f457026f000) libicuuc.so.56 => /opt/Qt/5.12.3/gcc_64/lib/./libicuuc.so.56 (0x7f456feb7000) libicudata.so.56 => /opt/Qt/5.12.3/gcc_64/lib/./libicudata.so.56 (0x7f456e4d4000) Now I can see how "-R ." makes sense. By "Qt does not sip icu" I meant that the Qt source package does not ship icu, but would use whatever it finds on the build host. ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Configure command lines of official Qt releases
06.06.2019, 11:12, "Richard Weickelt" : > On 05.06.2019 21:28, Иван Комиссаров wrote: >> AFAIK -R . is used to load that icu libraries I told you about in Gerrit. >> >> Otherwise it will try to load the system ones instead of the shipped ones >> with Qt. > > Thanks, Ivan. While this is true for other libs like xcb, Qt does not ship > icu. It uses either the one provided by the system or a thin replacement > resulting in a reduced localization feature set according to > https://wiki.qt.io/Qt_5_ICU#Design_Principles Linux binaries are shipped with ICU. It's not possible to use system version, because ICU doesn't provide stable ABI. -- Regards, Konstantin ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Configure command lines of official Qt releases
Hi, On Linux/macOS the current directory is not automatically/always an path where the dynamic linker searches implicitly for dependencies. That's only Windows :) Simon From: Development on behalf of Richard Weickelt Sent: Thursday, June 6, 2019 10:10 To: Иван Комиссаров Cc: development@qt-project.org Subject: Re: [Development] Configure command lines of official Qt releases On 05.06.2019 21:28, Иван Комиссаров wrote: > AFAIK -R . is used to load that icu libraries I told you about in Gerrit. > > Otherwise it will try to load the system ones instead of the shipped ones > with Qt. Thanks, Ivan. While this is true for other libs like xcb, Qt does not ship icu. It uses either the one provided by the system or a thin replacement resulting in a reduced localization feature set according to https://wiki.qt.io/Qt_5_ICU#Design_Principles I am a bit confused by "-R .". after reading the documentation: -R Add an explicit runtime library path to the Qt libraries. I thought that "." is always implicitly the first path where the run-time linker looks for (other)libraries. So I don't understand why it is set explicitly. Richard ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Configure command lines of official Qt releases
On 05.06.2019 21:28, Иван Комиссаров wrote: > AFAIK -R . is used to load that icu libraries I told you about in Gerrit. > > Otherwise it will try to load the system ones instead of the shipped ones > with Qt. Thanks, Ivan. While this is true for other libs like xcb, Qt does not ship icu. It uses either the one provided by the system or a thin replacement resulting in a reduced localization feature set according to https://wiki.qt.io/Qt_5_ICU#Design_Principles I am a bit confused by "-R .". after reading the documentation: -R Add an explicit runtime library path to the Qt libraries. I thought that "." is always implicitly the first path where the run-time linker looks for (other)libraries. So I don't understand why it is set explicitly. Richard ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Configure command lines of official Qt releases
AFAIK -R . is used to load that icu libraries I told you about in Gerrit. Otherwise it will try to load the system ones instead of the shipped ones with Qt. > 5 июня 2019 г., в 14:46, Richard Weickelt написал(а): > >> Excellent yes. That was a recent addition to the installer framework, >> very useful for exactly that purpose. > > Thanks for _all_ replies! Actually, the configure command line in the COIN > logs differs from > https://code.qt.io/cgit/qtsdk/qtsdk.git/tree/packaging-tools/bld_config?h=v5.12.3-packaging > so I rather used the ones from the COIN logs. > > Could somebody explain why the Linux release explicitly specifies "-R ." as > configure option? I have never seen that being used before. > > Richard > ___ > Development mailing list > Development@qt-project.org > https://lists.qt-project.org/listinfo/development ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Configure command lines of official Qt releases
Yes, don't use the ones from this packaging-tools/bld_config thing. That's outdated and certainly not used for Qt 5 releases today. Regarding -R . : This specifies the rpath as a relative path, which enables qmake to use origin rpaths (or equivalents on macos) instead of absolute paths, plus the relative path specified (but as that's a dot it's a noop). Simon From: Richard Weickelt Sent: Wednesday, June 5, 2019 14:46 To: Simon Hausmann; Markus Haberlander Cc: development@qt-project.org Subject: Re: [Development] Configure command lines of official Qt releases > Excellent yes. That was a recent addition to the installer framework, > very useful for exactly that purpose. Thanks for _all_ replies! Actually, the configure command line in the COIN logs differs from https://code.qt.io/cgit/qtsdk/qtsdk.git/tree/packaging-tools/bld_config?h=v5.12.3-packaging so I rather used the ones from the COIN logs. Could somebody explain why the Linux release explicitly specifies "-R ." as configure option? I have never seen that being used before. Richard ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Configure command lines of official Qt releases
> Excellent yes. That was a recent addition to the installer framework, > very useful for exactly that purpose. Thanks for _all_ replies! Actually, the configure command line in the COIN logs differs from https://code.qt.io/cgit/qtsdk/qtsdk.git/tree/packaging-tools/bld_config?h=v5.12.3-packaging so I rather used the ones from the COIN logs. Could somebody explain why the Linux release explicitly specifies "-R ." as configure option? I have never seen that being used before. Richard ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Configure command lines of official Qt releases
I think that is important to mention that the Logs components are not provided in the offline installer. It should be. El mar., 4 jun. 2019 a las 8:10, Konstantin Tokarev () escribió: > > > 04.06.2019, 17:01, "Volker Hilsheimer" : > >> 04.06.2019, 16:41, "Volker Hilsheimer" : > On 3 Jun 2019, at 20:15, Elvis Stansvik wrote: > > Den mån 3 juni 2019 kl 20:04 skrev Elvis Stansvik >: > > Hi Richard, > > > > I think this was asked on the interest list back in January [1]. > > > > The answer is here: > > > > > https://code.qt.io/cgit/qtsdk/qtsdk.git/tree/packaging-tools/bld_config > > > > I seem to remember some recent Qt developer thread about making these > > more accessible, but can't find it now. > > Found it, but I remembered somewhat wrong. I was thinking of this note > by Volker in the recent "A monologue about platforms in the Qt world" > thread [1]: > > "Why don’t we make the exact way of turning a clean Linux > distro-install into a "Qt reference configuration" available to > everyone else? The way build machines are provisioned in Coin is > rather opaque, even with some of the respective provisioning scripts > available in the qt5.git repo [1]. Having to document on a > (notoriously outdated) wiki how to set up things to build Qt from > source, when we have that knowledge literally codified somewhere for > Coin, doesn’t seem effective." > > So that was more about making the provisioning process for a > "reference" build machine more transparent. > > Elvis > > [1] > https://lists.qt-project.org/pipermail/development/2019-May/035773.html > >>> > >>> Since I’m being quoted, I might just as well use the opportunity to > announce that I’ve just made the repo where I’ve been tinkinering on a > solution to this problem for a while now public on the Qt gitlab instance, > accompanied by a little blog post: > >>> > >>> https://blog.qt.io/blog/2019/06/04/introducing-minicoin/ > >> > >> Can this project be used to test provisioning changes before submitting > them to the "big" Coin, > >> or there may be behavior differences? > >> > >> Either way, nice job! > > > > Thanks! > > > > Testing provisioning scripts and making sure that they result in a > working setup is definitely one of the use cases for minicoin. I found it > very useful to be able to have a fast loop of “minicoin up/try to build > stuff/minicoin destroy/improve script”, e.g when trying to build Qt for > Android locally. > > > > There are however some key differences in the assumptions Coin and > minicoin make; for example, Coin has a few helper scripts that are used to > download version-pinned packages from a Qt-internal cache, which is the > kind of stuff minicoin doesn’t care about, so scripts at this point don’t > translate 1:1. > > > > But If you run “minicoin status” you see that a bunch of coin-* machines > are defined, which will run the provisioning scripts from > qt5.git/coin/provisioning. So there is some basic scaffolding, and perhaps > stuff that lives in the qt5.git open source repo should be useful by > anyone, even if they don’t run their code within The Qt Company network :) > > I guess it won't be possible to obtain some OS images like Windows or > macOS outside of The Qt Company network because of licensing issues, > however it would be great to have at least Linux and Android. > > BTW, what about supporting KVM? Unlike VirtualBox, it supports > paravirtualized disk I/O which should make very positive impact on build > times. > > > Perhaps minicoin helps making those scripts more "general purpose” over > time. > > > > -- > Regards, > Konstantin > > ___ > Development mailing list > Development@qt-project.org > https://lists.qt-project.org/listinfo/development > ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Configure command lines of official Qt releases
04.06.2019, 17:01, "Volker Hilsheimer" : >> 04.06.2019, 16:41, "Volker Hilsheimer" : On 3 Jun 2019, at 20:15, Elvis Stansvik wrote: Den mån 3 juni 2019 kl 20:04 skrev Elvis Stansvik : > Hi Richard, > > I think this was asked on the interest list back in January [1]. > > The answer is here: > > https://code.qt.io/cgit/qtsdk/qtsdk.git/tree/packaging-tools/bld_config > > I seem to remember some recent Qt developer thread about making these > more accessible, but can't find it now. Found it, but I remembered somewhat wrong. I was thinking of this note by Volker in the recent "A monologue about platforms in the Qt world" thread [1]: "Why don’t we make the exact way of turning a clean Linux distro-install into a "Qt reference configuration" available to everyone else? The way build machines are provisioned in Coin is rather opaque, even with some of the respective provisioning scripts available in the qt5.git repo [1]. Having to document on a (notoriously outdated) wiki how to set up things to build Qt from source, when we have that knowledge literally codified somewhere for Coin, doesn’t seem effective." So that was more about making the provisioning process for a "reference" build machine more transparent. Elvis [1] https://lists.qt-project.org/pipermail/development/2019-May/035773.html >>> >>> Since I’m being quoted, I might just as well use the opportunity to >>> announce that I’ve just made the repo where I’ve been tinkinering on a >>> solution to this problem for a while now public on the Qt gitlab instance, >>> accompanied by a little blog post: >>> >>> https://blog.qt.io/blog/2019/06/04/introducing-minicoin/ >> >> Can this project be used to test provisioning changes before submitting them >> to the "big" Coin, >> or there may be behavior differences? >> >> Either way, nice job! > > Thanks! > > Testing provisioning scripts and making sure that they result in a working > setup is definitely one of the use cases for minicoin. I found it very useful > to be able to have a fast loop of “minicoin up/try to build stuff/minicoin > destroy/improve script”, e.g when trying to build Qt for Android locally. > > There are however some key differences in the assumptions Coin and minicoin > make; for example, Coin has a few helper scripts that are used to download > version-pinned packages from a Qt-internal cache, which is the kind of stuff > minicoin doesn’t care about, so scripts at this point don’t translate 1:1. > > But If you run “minicoin status” you see that a bunch of coin-* machines are > defined, which will run the provisioning scripts from > qt5.git/coin/provisioning. So there is some basic scaffolding, and perhaps > stuff that lives in the qt5.git open source repo should be useful by anyone, > even if they don’t run their code within The Qt Company network :) I guess it won't be possible to obtain some OS images like Windows or macOS outside of The Qt Company network because of licensing issues, however it would be great to have at least Linux and Android. BTW, what about supporting KVM? Unlike VirtualBox, it supports paravirtualized disk I/O which should make very positive impact on build times. > Perhaps minicoin helps making those scripts more "general purpose” over time. -- Regards, Konstantin ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Configure command lines of official Qt releases
04.06.2019, 16:41, "Volker Hilsheimer" mailto:volker.hilshei...@qt.io>>: On 3 Jun 2019, at 20:15, Elvis Stansvik mailto:elvst...@gmail.com>> wrote: Den mån 3 juni 2019 kl 20:04 skrev Elvis Stansvik mailto:elvst...@gmail.com>>: Hi Richard, I think this was asked on the interest list back in January [1]. The answer is here: https://code.qt.io/cgit/qtsdk/qtsdk.git/tree/packaging-tools/bld_config I seem to remember some recent Qt developer thread about making these more accessible, but can't find it now. Found it, but I remembered somewhat wrong. I was thinking of this note by Volker in the recent "A monologue about platforms in the Qt world" thread [1]: "Why don’t we make the exact way of turning a clean Linux distro-install into a "Qt reference configuration" available to everyone else? The way build machines are provisioned in Coin is rather opaque, even with some of the respective provisioning scripts available in the qt5.git repo [1]. Having to document on a (notoriously outdated) wiki how to set up things to build Qt from source, when we have that knowledge literally codified somewhere for Coin, doesn’t seem effective." So that was more about making the provisioning process for a "reference" build machine more transparent. Elvis [1] https://lists.qt-project.org/pipermail/development/2019-May/035773.html Since I’m being quoted, I might just as well use the opportunity to announce that I’ve just made the repo where I’ve been tinkinering on a solution to this problem for a while now public on the Qt gitlab instance, accompanied by a little blog post: https://blog.qt.io/blog/2019/06/04/introducing-minicoin/ Can this project be used to test provisioning changes before submitting them to the "big" Coin, or there may be behavior differences? Either way, nice job! Thanks! Testing provisioning scripts and making sure that they result in a working setup is definitely one of the use cases for minicoin. I found it very useful to be able to have a fast loop of “minicoin up/try to build stuff/minicoin destroy/improve script”, e.g when trying to build Qt for Android locally. There are however some key differences in the assumptions Coin and minicoin make; for example, Coin has a few helper scripts that are used to download version-pinned packages from a Qt-internal cache, which is the kind of stuff minicoin doesn’t care about, so scripts at this point don’t translate 1:1. But If you run “minicoin status” you see that a bunch of coin-* machines are defined, which will run the provisioning scripts from qt5.git/coin/provisioning. So there is some basic scaffolding, and perhaps stuff that lives in the qt5.git open source repo should be useful by anyone, even if they don’t run their code within The Qt Company network :) Perhaps minicoin helps making those scripts more "general purpose” over time. Volker ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Configure command lines of official Qt releases
04.06.2019, 16:41, "Volker Hilsheimer" : >> On 3 Jun 2019, at 20:15, Elvis Stansvik wrote: >> >> Den mån 3 juni 2019 kl 20:04 skrev Elvis Stansvik : >>> Hi Richard, >>> >>> I think this was asked on the interest list back in January [1]. >>> >>> The answer is here: >>> >>> https://code.qt.io/cgit/qtsdk/qtsdk.git/tree/packaging-tools/bld_config >>> >>> I seem to remember some recent Qt developer thread about making these >>> more accessible, but can't find it now. >> >> Found it, but I remembered somewhat wrong. I was thinking of this note >> by Volker in the recent "A monologue about platforms in the Qt world" >> thread [1]: >> >> "Why don’t we make the exact way of turning a clean Linux >> distro-install into a "Qt reference configuration" available to >> everyone else? The way build machines are provisioned in Coin is >> rather opaque, even with some of the respective provisioning scripts >> available in the qt5.git repo [1]. Having to document on a >> (notoriously outdated) wiki how to set up things to build Qt from >> source, when we have that knowledge literally codified somewhere for >> Coin, doesn’t seem effective." >> >> So that was more about making the provisioning process for a >> "reference" build machine more transparent. >> >> Elvis >> >> [1] https://lists.qt-project.org/pipermail/development/2019-May/035773.html > > Since I’m being quoted, I might just as well use the opportunity to announce > that I’ve just made the repo where I’ve been tinkinering on a solution to > this problem for a while now public on the Qt gitlab instance, accompanied by > a little blog post: > > https://blog.qt.io/blog/2019/06/04/introducing-minicoin/ Can this project be used to test provisioning changes before submitting them to the "big" Coin, or there may be behavior differences? Either way, nice job! -- Regards, Konstantin ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Configure command lines of official Qt releases
On 3 Jun 2019, at 20:15, Elvis Stansvik mailto:elvst...@gmail.com>> wrote: Den mån 3 juni 2019 kl 20:04 skrev Elvis Stansvik mailto:elvst...@gmail.com>>: Hi Richard, I think this was asked on the interest list back in January [1]. The answer is here: https://code.qt.io/cgit/qtsdk/qtsdk.git/tree/packaging-tools/bld_config I seem to remember some recent Qt developer thread about making these more accessible, but can't find it now. Found it, but I remembered somewhat wrong. I was thinking of this note by Volker in the recent "A monologue about platforms in the Qt world" thread [1]: "Why don’t we make the exact way of turning a clean Linux distro-install into a "Qt reference configuration" available to everyone else? The way build machines are provisioned in Coin is rather opaque, even with some of the respective provisioning scripts available in the qt5.git repo [1]. Having to document on a (notoriously outdated) wiki how to set up things to build Qt from source, when we have that knowledge literally codified somewhere for Coin, doesn’t seem effective." So that was more about making the provisioning process for a "reference" build machine more transparent. Elvis [1] https://lists.qt-project.org/pipermail/development/2019-May/035773.html Since I’m being quoted, I might just as well use the opportunity to announce that I’ve just made the repo where I’ve been tinkinering on a solution to this problem for a while now public on the Qt gitlab instance, accompanied by a little blog post: https://blog.qt.io/blog/2019/06/04/introducing-minicoin/ Cheers, Volker ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Configure command lines of official Qt releases
Excellent yes. That was a recent addition to the installer framework, very useful for exactly that purpose. Simon From: Markus Haberlander Sent: Tuesday, June 4, 2019 12:47 To: Simon Hausmann Cc: Richard Weickelt; development@qt-project.org Subject: Re: [Development] Configure command lines of official Qt releases Hi, another place worth to mention: There is a component "Logs" in the Qt installer for each Qt version, at least for newer releases like 5.9.8 or 5.12.x. When selecting this, you get a zip file with build and test logs for *all* prebuilt versions of Qt. E.g. for the linux configure line of Qt 5.12.3 (forgive my Windows installation path ...) search for "configure" in the following file: C:\Qt\5.12.3\Logs\All_buildlogs.7z\build_logs\qtbase_buildLogs\Linux-RHEL_7_4-GCC-Linux-RHEL_7_4-X86_64\log.txt.gz\log.txt And not to forget, these files also log many details (like envirinment variables ...) of the build environment ... Best regards Markus Am Di., 4. Juni 2019 um 10:44 Uhr schrieb Simon Hausmann mailto:simon.hausm...@qt.io>>: Hi, It's a little tricky, but you can reverse engineer it :) The releases are spun from qt5.git. So if you take the 5.12.3 release, for example then using git tag -l you can see a v5.12.3 tag in the qt5.git repository. A quick git show on that tag leads you to commit 8337e20fadddf7f9c3407f69e620f96d6c189685 , which is the last commit that went into the release (last submodule update). If you search for that commit in Gerrit, you'll find https://codereview.qt-project.org/c/qt/qt5/+/258282 , the corresponding change. At the bottom of that page you'll find the report from the CI about the successful integration, which leads to https://testresults.qt.io/coin/integration/qt/qt5/tasks/1554952272 . That page shows the builds of all modules, where the build of qtbase is relevant for what you're looking for. For the qtbase build you'll see a lot of configurations, but the ones that have the "Packaging" feature under "Coin Features" are the ones that will be used for the binary ... packages :) If you peek into the build log then you'll see the entire configure line that was used to build the binaries in the CI, which are the same binaries that are packaged and distributed for release. Simon From: Development mailto:development-boun...@qt-project.org>> on behalf of Richard Weickelt mailto:rich...@weickelt.de>> Sent: Monday, June 3, 2019 18:55 To: development@qt-project.org<mailto:development@qt-project.org> Subject: [Development] Configure command lines of official Qt releases Hi, where can I find the configure command lines that have been used for Qt binary releases provided at https://download.qt.io/official_releases/qt/ ? Is there also more information available about the environment they have been built on? I am particularly interested in the Linux release. Thanks ___ Development mailing list Development@qt-project.org<mailto:Development@qt-project.org> https://lists.qt-project.org/listinfo/development ___ Development mailing list Development@qt-project.org<mailto:Development@qt-project.org> https://lists.qt-project.org/listinfo/development ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Configure command lines of official Qt releases
Hi, another place worth to mention: There is a component "Logs" in the Qt installer for each Qt version, at least for newer releases like 5.9.8 or 5.12.x. When selecting this, you get a zip file with build and test logs for *all* prebuilt versions of Qt. E.g. for the linux configure line of Qt 5.12.3 (forgive my Windows installation path ...) search for "configure" in the following file: C:\Qt\5.12.3\Logs\All_buildlogs.7z\build_logs\qtbase_buildLogs\Linux-RHEL_7_4-GCC-Linux-RHEL_7_4-X86_64\log.txt.gz\log.txt And not to forget, these files also log many details (like envirinment variables ...) of the build environment ... Best regards Markus Am Di., 4. Juni 2019 um 10:44 Uhr schrieb Simon Hausmann < simon.hausm...@qt.io>: > Hi, > > It's a little tricky, but you can reverse engineer it :) > > The releases are spun from qt5.git. So if you take the 5.12.3 release, for > example then using git tag -l you can see a v5.12.3 tag in the qt5.git > repository. > > A quick git show on that tag leads you to > > commit 8337e20fadddf7f9c3407f69e620f96d6c189685 > > , which is the last commit that went into the release (last submodule > update). > > If you search for that commit in Gerrit, you'll find > > https://codereview.qt-project.org/c/qt/qt5/+/258282 > > , the corresponding change. At the bottom of that page you'll find the > report from the CI about the successful integration, which leads to > > https://testresults.qt.io/coin/integration/qt/qt5/tasks/1554952272 . > > That page shows the builds of all modules, where the build of qtbase is > relevant for what you're looking for. For the qtbase build you'll see a lot > of configurations, but the ones that have the "Packaging" feature under > "Coin Features" are the ones that will be used for the binary ... packages > :) > > If you peek into the build log then you'll see the entire configure line > that was used to build the binaries in the CI, which are the same binaries > that are packaged and distributed for release. > > > Simon > ------ > *From:* Development on behalf of > Richard Weickelt > *Sent:* Monday, June 3, 2019 18:55 > *To:* development@qt-project.org > *Subject:* [Development] Configure command lines of official Qt releases > > Hi, > > where can I find the configure command lines that have been used for Qt > binary releases provided at https://download.qt.io/official_releases/qt/ ? > > Is there also more information available about the environment they have > been built on? I am particularly interested in the Linux release. > > Thanks > ___ > Development mailing list > Development@qt-project.org > https://lists.qt-project.org/listinfo/development > ___ > Development mailing list > Development@qt-project.org > https://lists.qt-project.org/listinfo/development > ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Configure command lines of official Qt releases
Hi, It's a little tricky, but you can reverse engineer it :) The releases are spun from qt5.git. So if you take the 5.12.3 release, for example then using git tag -l you can see a v5.12.3 tag in the qt5.git repository. A quick git show on that tag leads you to commit 8337e20fadddf7f9c3407f69e620f96d6c189685 , which is the last commit that went into the release (last submodule update). If you search for that commit in Gerrit, you'll find https://codereview.qt-project.org/c/qt/qt5/+/258282 , the corresponding change. At the bottom of that page you'll find the report from the CI about the successful integration, which leads to https://testresults.qt.io/coin/integration/qt/qt5/tasks/1554952272 . That page shows the builds of all modules, where the build of qtbase is relevant for what you're looking for. For the qtbase build you'll see a lot of configurations, but the ones that have the "Packaging" feature under "Coin Features" are the ones that will be used for the binary ... packages :) If you peek into the build log then you'll see the entire configure line that was used to build the binaries in the CI, which are the same binaries that are packaged and distributed for release. Simon From: Development on behalf of Richard Weickelt Sent: Monday, June 3, 2019 18:55 To: development@qt-project.org Subject: [Development] Configure command lines of official Qt releases Hi, where can I find the configure command lines that have been used for Qt binary releases provided at https://download.qt.io/official_releases/qt/ ? Is there also more information available about the environment they have been built on? I am particularly interested in the Linux release. Thanks ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Configure command lines of official Qt releases
Den mån 3 juni 2019 kl 20:29 skrev Richard Weickelt : >> I would expect "Official builds configuration options >> site:lists.qt-project.org" to bring this post up: >> https://lists.qt-project.org/pipermail/interest/2019-January/032221.html >> but it seems like google hasn't even indexed it. Elvis Stansvik (3 June 2019 20:40) wrote: > Strange! Perhaps something for the Qt web server administrators to > look at, I would also expect it to be indexed by now. hmm ... well, I find no https://lists.qt-project.org/robots.txt so at least we're not scaring them off with that [0]. [0] http://www.robotstxt.org/robotstxt.html Can anyone think of anything else that would keep Google from indexing the site ? Eddy. ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Configure command lines of official Qt releases
Den mån 3 juni 2019 kl 20:29 skrev Richard Weickelt : > > > > I think this was asked on the interest list back in January [1]. > > I did search on the Qt mailing lists, but even when I type exactly the > subject of the thread you referred to, google doesn't find it. I would > expect "Official builds configuration options site:lists.qt-project.org" to > bring this post up: > https://lists.qt-project.org/pipermail/interest/2019-January/032221.html but > it seems like google hasn't even indexed it. Strange! Perhaps something for the Qt web server administrators to look at, I would also expect it to be indexed by now. Elvis > > The answer is here: > > > > https://code.qt.io/cgit/qtsdk/qtsdk.git/tree/packaging-tools/bld_config > > Great. Thanks. > > Richard ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Configure command lines of official Qt releases
> I think this was asked on the interest list back in January [1]. I did search on the Qt mailing lists, but even when I type exactly the subject of the thread you referred to, google doesn't find it. I would expect "Official builds configuration options site:lists.qt-project.org" to bring this post up: https://lists.qt-project.org/pipermail/interest/2019-January/032221.html but it seems like google hasn't even indexed it. > The answer is here: > > https://code.qt.io/cgit/qtsdk/qtsdk.git/tree/packaging-tools/bld_config Great. Thanks. Richard ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Configure command lines of official Qt releases
Den mån 3 juni 2019 kl 20:04 skrev Elvis Stansvik : > > Hi Richard, > > I think this was asked on the interest list back in January [1]. > > The answer is here: > > https://code.qt.io/cgit/qtsdk/qtsdk.git/tree/packaging-tools/bld_config > > I seem to remember some recent Qt developer thread about making these > more accessible, but can't find it now. Found it, but I remembered somewhat wrong. I was thinking of this note by Volker in the recent "A monologue about platforms in the Qt world" thread [1]: "Why don’t we make the exact way of turning a clean Linux distro-install into a "Qt reference configuration" available to everyone else? The way build machines are provisioned in Coin is rather opaque, even with some of the respective provisioning scripts available in the qt5.git repo [1]. Having to document on a (notoriously outdated) wiki how to set up things to build Qt from source, when we have that knowledge literally codified somewhere for Coin, doesn’t seem effective." So that was more about making the provisioning process for a "reference" build machine more transparent. Elvis [1] https://lists.qt-project.org/pipermail/development/2019-May/035773.html > > HTH, > Elvis > > [1] https://lists.qt-project.org/pipermail/interest/2019-January/032221.html > > Den mån 3 juni 2019 kl 18:56 skrev Richard Weickelt : > > > > Hi, > > > > where can I find the configure command lines that have been used for Qt > > binary releases provided at https://download.qt.io/official_releases/qt/ ? > > > > Is there also more information available about the environment they have > > been built on? I am particularly interested in the Linux release. > > > > Thanks > > ___ > > Development mailing list > > Development@qt-project.org > > https://lists.qt-project.org/listinfo/development ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Configure command lines of official Qt releases
Hi Richard, I think this was asked on the interest list back in January [1]. The answer is here: https://code.qt.io/cgit/qtsdk/qtsdk.git/tree/packaging-tools/bld_config I seem to remember some recent Qt developer thread about making these more accessible, but can't find it now. HTH, Elvis [1] https://lists.qt-project.org/pipermail/interest/2019-January/032221.html Den mån 3 juni 2019 kl 18:56 skrev Richard Weickelt : > > Hi, > > where can I find the configure command lines that have been used for Qt > binary releases provided at https://download.qt.io/official_releases/qt/ ? > > Is there also more information available about the environment they have > been built on? I am particularly interested in the Linux release. > > Thanks > ___ > Development mailing list > Development@qt-project.org > https://lists.qt-project.org/listinfo/development ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
[Development] Configure command lines of official Qt releases
Hi, where can I find the configure command lines that have been used for Qt binary releases provided at https://download.qt.io/official_releases/qt/ ? Is there also more information available about the environment they have been built on? I am particularly interested in the Linux release. Thanks ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
