Re: [Development] -developer-build (was: [5.7-beta] compile error with xcode-6.4
> On May 4, 2016, at 7:10 PM, Mark De Wit <mark.de...@iesve.com> wrote: > > Hmm, is that proving my point, though? My understanding was that compiling > Qt in a namespace and with unique filename was recommended to avoid > (minimise) the likelihood of conflicting Qt versions in a single process. > > Is there documentation that states how one should build Qt for release with > their own software? The trial & error approaches I have witnessed in the > past have not been a positive experience. I think this lists the configure flags that we use for the Qt binary releases ourselves for the different platforms: http://code.qt.io/cgit/qtsdk/qtsdk.git/tree/packaging-tools/releases/release-56 Br, Eike > Mark > > -Original Message- > From: Development > [mailto:development-bounces+mark.dewit=iesve@qt-project.org] On Behalf Of > Thiago Macieira > Sent: 04 May 2016 17:43 > To: development@qt-project.org > Subject: Re: [Development] -developer-build (was: [5.7-beta] compile error > with xcode-6.4 > > On quarta-feira, 4 de maio de 2016 07:46:41 PDT Mark De Wit wrote: >> The configure flags are poorly documented, and options like qtlibinfix >> (which I understood to be a recommended best practice) isn't even mentioned >> on the configure flag page. > > Because it isn't a recommended best practice. > > -- > Thiago Macieira - thiago.macieira (AT) intel.com > Software Architect - Intel Open Source Technology Center > > ___ > Development mailing list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development > ___ > Development mailing list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development -- Eike Ziller Principal Software Engineer The Qt Company GmbH Rudower Chaussee 13 D-12489 Berlin eike.zil...@qt.io +123 45 6789012 http://qt.io Geschäftsführer: Mika Pälsi, Juha Varelius, Tuula Haataja Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] -developer-build (was: [5.7-beta] compile error with xcode-6.4
On Wed, May 04, 2016 at 07:46:41AM +, Mark De Wit wrote: > Having tried to do this myself last week, I cannot find any "official" > documentation > on how to build Qt myself for an official release with our software. Doing > our own > build has proven frustrating enough that we abandoned the current attempt to > update > our version of Qt. > > The configure flags are poorly documented, and options like qtlibinfix (which > I > understood to be a recommended best practice) isn't even mentioned on the > configure > flag page. .../qt-5/qtbase$ ./configure --help | grep libinfix -qtlibinfix Renames all libQt*.so to libQt*.so. Andre' ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] -developer-build (was: [5.7-beta] compile error with xcode-6.4
On quarta-feira, 4 de maio de 2016 17:10:30 PDT Mark De Wit wrote: > Hmm, is that proving my point, though? My understanding was that compiling > Qt in a namespace and with unique filename was recommended to avoid > (minimise) the likelihood of conflicting Qt versions in a single process. That is true, but why are you worried about this in the first place? Are you loading random plugins from other sources that may or may not be linked to Qt? If so, that's not a common use-case (hence no BKM for this). The only case that may be relevant is to deal with plugins installed by the system Linux distribution. But Qt should refuse to load plugins linked to newer versions of itself, not to mention that this is now enforced by the dynamic linker itself since Qt 5.6. In any case, the situation is often reversed, as user applications often come with Qt versions newer than the system installation. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] -developer-build (was: [5.7-beta] compile error with xcode-6.4
Hmm, is that proving my point, though? My understanding was that compiling Qt in a namespace and with unique filename was recommended to avoid (minimise) the likelihood of conflicting Qt versions in a single process. Is there documentation that states how one should build Qt for release with their own software? The trial & error approaches I have witnessed in the past have not been a positive experience. Mark -Original Message- From: Development [mailto:development-bounces+mark.dewit=iesve@qt-project.org] On Behalf Of Thiago Macieira Sent: 04 May 2016 17:43 To: development@qt-project.org Subject: Re: [Development] -developer-build (was: [5.7-beta] compile error with xcode-6.4 On quarta-feira, 4 de maio de 2016 07:46:41 PDT Mark De Wit wrote: > The configure flags are poorly documented, and options like qtlibinfix > (which I understood to be a recommended best practice) isn't even mentioned > on the configure flag page. Because it isn't a recommended best practice. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] -developer-build (was: [5.7-beta] compile error with xcode-6.4
On quarta-feira, 4 de maio de 2016 07:46:41 PDT Mark De Wit wrote: > The configure flags are poorly documented, and options like qtlibinfix > (which I understood to be a recommended best practice) isn't even mentioned > on the configure flag page. Because it isn't a recommended best practice. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] -developer-build (was: [5.7-beta] compile error with xcode-6.4
Having tried to do this myself last week, I cannot find any "official" documentation on how to build Qt myself for an official release with our software. Doing our own build has proven frustrating enough that we abandoned the current attempt to update our version of Qt. The configure flags are poorly documented, and options like qtlibinfix (which I understood to be a recommended best practice) isn't even mentioned on the configure flag page. Kind regards, Mark -Original Message- From: Development [mailto:development-bounces+mark.dewit=iesve@qt-project.org] On Behalf Of Thiago Macieira Sent: 03 May 2016 18:09 To: development@qt-project.org Subject: Re: [Development] -developer-build (was: [5.7-beta] compile error with xcode-6.4 Em terça-feira, 3 de maio de 2016, às 19:01:30 PDT, Harri Porten escreveu: > I've seen my Qt users use -developer-build because > >http://wiki.qt.io/Building_Qt_5_from_Git > > proposes it and the impact not clear to everyone. Qt users naturally > consider themselves to be developers I've seen people on IRC come with those errors and I've asked them to update the wiki page they found the instructions in to remove the -developer-build option. Either they've never done it or the option came back. > The negative impact I have seen: the lack of a following "make install" > leads to a different layout of the files on disk. Still, companies are > sharing such builds within their team and develop their application > against it. That implies adding a -prefix option to configure. > If noone minds I'll make the wording more precise. Thanks, that would be most welcome. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] -developer-build (was: [5.7-beta] compile error with xcode-6.4
Em terça-feira, 3 de maio de 2016, às 19:01:30 PDT, Harri Porten escreveu: > I've seen my Qt users use -developer-build because > >http://wiki.qt.io/Building_Qt_5_from_Git > > proposes it and the impact not clear to everyone. Qt users naturally > consider themselves to be developers I've seen people on IRC come with those errors and I've asked them to update the wiki page they found the instructions in to remove the -developer-build option. Either they've never done it or the option came back. > The negative impact I have seen: the lack of a following "make install" > leads to a different layout of the files on disk. Still, companies are > sharing such builds within their team and develop their application > against it. That implies adding a -prefix option to configure. > If noone minds I'll make the wording more precise. Thanks, that would be most welcome. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] -developer-build (was: [5.7-beta] compile error with xcode-6.4
I got reminded of something: On Tue, 3 May 2016, Thiago Macieira wrote: Still, note that this is not an error. It's a warning turned to error because of the -Werror, which means that you used -developer-build. In that case, please send a patch. :-) I've seen my Qt users use -developer-build because http://wiki.qt.io/Building_Qt_5_from_Git proposes it and the impact not clear to everyone. Qt users naturally consider themselves to be developers :) The negative impact I have seen: the lack of a following "make install" leads to a different layout of the files on disk. Still, companies are sharing such builds within their team and develop their application against it. If noone minds I'll make the wording more precise. Harri. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
