[Development] Problem comiling with option -qtnamespace and -qtlibinfix in Mac OS X 10.9.4

Hauke Krüger krueger at ind.rwth-aachen.de
Wed Jul 9 08:01:27 CEST 2014

Hi Oswald

thank you for the response. You were right: It seems that the known bug 
for the -qtlibinfix option
has corrupted my directory when trying it for the first time. Running 
"./configure -qtamespace"
for a second time combined with a "make clean" is not sufficient to 
repair it.

Building from a completely emtpy build dir with qtnamespace this time 
was successful.

Thank you  and best regards


Am 08.07.14 11:22, schrieb Oswald Buddenhagen:
> On Tue, Jul 08, 2014 at 07:12:37AM +0200, Hauke Krüger wrote:
>> I have problems compiling Qt-5.3.1 from the sources in Mac OS X 10.9.4
>> when specifying the option -qtnamespace and -qtlibinfix.
> https://bugreports.qt-project.org/browse/QTBUG-35604
>> 1) Option with unspecified namespace: Running configure without
>> -qtnamespace:
>> [...]
>> 2) Option with specified Option -qtnamespace
>> -> In the terminal, running "./configure -qtnamespace rtproc" -> "make"
>> in the directory qt-everywhere-opensource-src-5.3.1/qtbase does not work:
>> During the compilation of e.g. src/network, I see the following compiler
>> error:
>> [...]
>> The main difference: Instead of
>> "-I../../lib/QtCore.framework/Versions/5/Headers/5.3.1/QtCore",
>> the include path is set to
>> "......./lib/QtCore.framework/Headers/5.3.1/QtCore"
>> where the headers are not located.
> i don't know why compiling with a namespace would do that. i didn't
> think it has any effect except setting a #define.
> did you start with an empty build dir both times? if not, it's more
> likely that this somehow leads to the failure.
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development

More information about the Development mailing list