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:[email protected]] On Behalf Of Thiago Macieira Sent: 04 May 2016 17:43 To: [email protected] 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 [email protected] http://lists.qt-project.org/mailman/listinfo/development _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
