Re: [Interest] Is still possible to build Qt 5.15.15 with macOS 14.7 and Xcode 15.2?
Hi Nuno,
> I don’t need this module. I usually clone the repo from git and only fetch
> the modules I need.
> I don’t know how to disable a module that I don’t need when all the source is
> available.
> Maybe I need to tweak the configure call.
You need to use "-skip " option from the configure script.
Note that in 5.15 in order to skip QtLocation, you actually have to skip
QtPositioning as well,
because they're in the same repo. So the correct command would look like:
configure -skip qtpositioning
Note that you can also run
./configure --help
to see the full list of available options.
Hope this helps.
--
Ivan
From: Interest on behalf of Nuno Santos via
Interest
Sent: Thursday, November 21, 2024 1:18 PM
To: Tor Arne Vestbø
Cc: interestqt-project. org
Subject: Re: [Interest] Is still possible to build Qt 5.15.15 with macOS 14.7
and Xcode 15.2?
Tor,
I’ve tried to build 5.15.18 from the maintenance sources. It is failing with an
error on what seems to be the qtlocation module. (See below)
I don’t need this module. I usually clone the repo from git and only fetch the
modules I need. I don’t know how to disable a module that I don’t need when all
the source is available. Maybe I need to tweak the configure call.
Best,
Nuno
In file included from include/mbgl/style/layer.hpp:4:
include/mbgl/util/unique_any.hpp:51:31: error: no member named 'move' in
namespace 'std'
vtable->move(std::move(rhs.storage), storage);
~^
include/mbgl/util/unique_any.hpp:69:25: error: no member named 'move' in
namespace 'std'
unique_any(std::move(rhs)).swap(*this);
~^
include/mbgl/util/unique_any.hpp:91:33: error: no type named 'move' in
namespace 'std'
unique_any tmp(std::move(rhs));
~^
include/mbgl/util/unique_any.hpp:94:39: error: no member named 'move' in
namespace 'std'
rhs.vtable->move(std::move(storage), rhs.storage);
~^
include/mbgl/util/unique_any.hpp:98:35: error: no member named 'move' in
namespace 'std'
vtable->move(std::move(tmp.storage), storage);
~^
include/mbgl/util/unique_any.hpp:154:41: error: no member named 'move' in
namespace 'std'; did you mean simply 'move'?
new (&dest.stack)
ValueType(std::move(reinterpret_cast(src.stack)));
^
move
include/mbgl/util/unique_any.hpp:153:14: note: 'move' declared here
void move(Storage&& src, Storage& dest) override {
^
include/mbgl/util/unique_any.hpp:257:49: error: no member named 'move' in
namespace 'std'
auto retValue = static_cast(std::move(*temp));
~^
include/mbgl/util/unique_any.hpp:259:17: error: no member named 'move' in
namespace 'std'
return std::move(retValue);
~^
8 errors generated.
8 errors generated.
make[6]: *** [.obj/release/src/mbgl/renderer/layers/render_circle_layer.o]
Error 1
make[5]: *** [release-all] Error 2
make[5]: *** Waiting for unfinished jobs
make[6]: *** [.obj/debug/src/mbgl/renderer/layers/render_circle_layer.o] Error 1
8 errors generated.
make[6]: *** [.obj/debug/src/mbgl/renderer/layers/render_custom_layer.o] Error 1
make[5]: *** [debug-all] Error 2
make[4]: *** [sub---3rdparty-mapbox-gl-native-make_first] Error 2
make[3]: *** [sub-geoservices-make_first] Error 2
make[2]: *** [sub-plugins-make_first] Error 2
make[1]: *** [sub-src-make_first] Error 2
make: *** [module-qtlocation-make_first] Error 2
On 19 Nov 2024, at 12:55, Nuno Santos wrote:
Tor,
Sources are available for 5.15.18 through the installer. I will try again with
this one and should have feedback soon.
Thank You!
Best regards,
Nuno
On 19 Nov 2024, at 11:39, Tor Arne Vestbø wrote:
5.15.18 is available through the installer with an appropriate commercial
license.
On Nov 19, 2024, at 12:30, Nuno Santos wrote:
Hi Tor,
I’ve only tried with Qt 5.15.15
Is 5.15.16, 5.15.17, 5.15.18 available in any other place?
Thx!
Regards,
Nuno
On 19 Nov 2024, at 10:37, Tor Arne Vestbø wrote:
Does this reproduce with Qt 5.15.18 ? If so please file a bug
On Nov 19, 2024, at 10:13, Nuno Santos via Interest
wrote:
Hi,
Qt 5.X.Y platform notes says:
macOS 10.13, macOS 10.14, macOS 10.15, macOS 11, macOS 12, macOS 13, macOS 14
x86_64 and x86_64h and arm64 Xcode 14 (13 SDK), or Xcode 15 (14 SDK)
But when try to compile from source it says:
Project ERROR: failed to parse default search paths from compiler output
How do I see the reason of
Re: [Interest] Is still possible to build Qt 5.15.15 with macOS 14.7 and Xcode 15.2?
On Thursday 21 November 2024 04:18:01 Pacific Standard Time Nuno Santos via Interest wrote: > In file included from include/mbgl/style/layer.hpp:4: > include/mbgl/util/unique_any.hpp:51:31: error: no member named 'move' in > namespace 'std' vtable->move(std::move(rhs.storage), storage); That's an error in a third-party source that has long since been fixed: it's a missing #include. You'll probably need to patch it yourself. You're using a compiler that is much newer than the sources in question. But if you don't need qtlocation, you shouldn't build it. -- Thiago Macieira - thiago.macieira (AT) intel.com Principal Engineer - Intel DCAI Platform & System Engineering smime.p7s Description: S/MIME cryptographic signature ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Is still possible to build Qt 5.15.15 with macOS 14.7 and Xcode 15.2?
Tor,
I’ve tried to build 5.15.18 from the maintenance sources. It is failing with an
error on what seems to be the qtlocation module. (See below)
I don’t need this module. I usually clone the repo from git and only fetch the
modules I need. I don’t know how to disable a module that I don’t need when all
the source is available. Maybe I need to tweak the configure call.
Best,
Nuno
In file included from include/mbgl/style/layer.hpp:4:
include/mbgl/util/unique_any.hpp:51:31: error: no member named 'move' in
namespace 'std'
vtable->move(std::move(rhs.storage), storage);
~^
include/mbgl/util/unique_any.hpp:69:25: error: no member named 'move' in
namespace 'std'
unique_any(std::move(rhs)).swap(*this);
~^
include/mbgl/util/unique_any.hpp:91:33: error: no type named 'move' in
namespace 'std'
unique_any tmp(std::move(rhs));
~^
include/mbgl/util/unique_any.hpp:94:39: error: no member named 'move' in
namespace 'std'
rhs.vtable->move(std::move(storage), rhs.storage);
~^
include/mbgl/util/unique_any.hpp:98:35: error: no member named 'move' in
namespace 'std'
vtable->move(std::move(tmp.storage), storage);
~^
include/mbgl/util/unique_any.hpp:154:41: error: no member named 'move' in
namespace 'std'; did you mean simply 'move'?
new (&dest.stack)
ValueType(std::move(reinterpret_cast(src.stack)));
^
move
include/mbgl/util/unique_any.hpp:153:14: note: 'move' declared here
void move(Storage&& src, Storage& dest) override {
^
include/mbgl/util/unique_any.hpp:257:49: error: no member named 'move' in
namespace 'std'
auto retValue = static_cast(std::move(*temp));
~^
include/mbgl/util/unique_any.hpp:259:17: error: no member named 'move' in
namespace 'std'
return std::move(retValue);
~^
8 errors generated.
8 errors generated.
make[6]: *** [.obj/release/src/mbgl/renderer/layers/render_circle_layer.o]
Error 1
make[5]: *** [release-all] Error 2
make[5]: *** Waiting for unfinished jobs
make[6]: *** [.obj/debug/src/mbgl/renderer/layers/render_circle_layer.o] Error 1
8 errors generated.
make[6]: *** [.obj/debug/src/mbgl/renderer/layers/render_custom_layer.o] Error 1
make[5]: *** [debug-all] Error 2
make[4]: *** [sub---3rdparty-mapbox-gl-native-make_first] Error 2
make[3]: *** [sub-geoservices-make_first] Error 2
make[2]: *** [sub-plugins-make_first] Error 2
make[1]: *** [sub-src-make_first] Error 2
make: *** [module-qtlocation-make_first] Error 2
> On 19 Nov 2024, at 12:55, Nuno Santos wrote:
>
> Tor,
>
> Sources are available for 5.15.18 through the installer. I will try again
> with this one and should have feedback soon.
>
> Thank You!
>
> Best regards,
>
> Nuno
>
>> On 19 Nov 2024, at 11:39, Tor Arne Vestbø wrote:
>>
>> 5.15.18 is available through the installer with an appropriate commercial
>> license.
>>
>>> On Nov 19, 2024, at 12:30, Nuno Santos wrote:
>>>
>>> Hi Tor,
>>>
>>> I’ve only tried with Qt 5.15.15
>>>
>>> Is 5.15.16, 5.15.17, 5.15.18 available in any other place?
>>>
>>> Thx!
>>>
>>> Regards,
>>>
>>> Nuno
>>>
On 19 Nov 2024, at 10:37, Tor Arne Vestbø wrote:
Does this reproduce with Qt 5.15.18 ? If so please file a bug
> On Nov 19, 2024, at 10:13, Nuno Santos via Interest
> wrote:
>
> Hi,
>
> Qt 5.X.Y platform notes says:
>
> macOS 10.13, macOS 10.14, macOS 10.15, macOS 11, macOS 12, macOS 13,
> macOS 14 x86_64 and x86_64h and arm64 Xcode 14 (13 SDK), or Xcode 15 (14
> SDK)
>
> But when try to compile from source it says:
>
> Project ERROR: failed to parse default search paths from compiler output
>
> How do I see the reason of this error?
>
> ➜ src git:(v5.15.15-lts-lgpl) ✗ ./configure -confirm-license -recheck
> -prefix /Users/nsantos/Qt/5.15.15/clang_64_static -platform macx-clang
> -device-option QMAKE_APPLE_DEVICE_ARCHS="x86_64 arm64" -commercial
> -debug-and-release -static -nomake examples -nomake tests -opengl desktop
> -no-securetransport -openssl-linked
> -I/Users/nsantos/Qt-Utils/openssl/include
> OPENSSL_LIBS="/Users/nsantos/Qt-Utils/openssl/lib/libssl.a
> /Users/nsantos/Qt-Utils/openssl/lib/libcrypto.a" -qtnamespace
> com_imaginando_qt_5_15_15
> + cd qtbase
> + /Users/nsantos/Qt/5.15.15/src/qtbase/configure -top-level
> -confirm-license -recheck -prefix
> /Users/nsantos/Qt/5.15.15/clang_64_static -platform macx-clang
> -device-option QMAKE_APPLE_DEVICE_ARCHS=x86_64 arm64 -commercial
> -debug-and-release -static -nomake examples -nomake tests -opengl desktop
> -no-securetransport -ope
Re: [Interest] Is still possible to build Qt 5.15.15 with macOS 14.7 and Xcode 15.2?
Tor, Sources are available for 5.15.18 through the installer. I will try again with this one and should have feedback soon. Thank You! Best regards, Nuno > On 19 Nov 2024, at 11:39, Tor Arne Vestbø wrote: > > 5.15.18 is available through the installer with an appropriate commercial > license. > >> On Nov 19, 2024, at 12:30, Nuno Santos wrote: >> >> Hi Tor, >> >> I’ve only tried with Qt 5.15.15 >> >> Is 5.15.16, 5.15.17, 5.15.18 available in any other place? >> >> Thx! >> >> Regards, >> >> Nuno >> >>> On 19 Nov 2024, at 10:37, Tor Arne Vestbø wrote: >>> >>> Does this reproduce with Qt 5.15.18 ? If so please file a bug >>> On Nov 19, 2024, at 10:13, Nuno Santos via Interest wrote: Hi, Qt 5.X.Y platform notes says: macOS 10.13, macOS 10.14, macOS 10.15, macOS 11, macOS 12, macOS 13, macOS 14 x86_64 and x86_64h and arm64 Xcode 14 (13 SDK), or Xcode 15 (14 SDK) But when try to compile from source it says: Project ERROR: failed to parse default search paths from compiler output How do I see the reason of this error? ➜ src git:(v5.15.15-lts-lgpl) ✗ ./configure -confirm-license -recheck -prefix /Users/nsantos/Qt/5.15.15/clang_64_static -platform macx-clang -device-option QMAKE_APPLE_DEVICE_ARCHS="x86_64 arm64" -commercial -debug-and-release -static -nomake examples -nomake tests -opengl desktop -no-securetransport -openssl-linked -I/Users/nsantos/Qt-Utils/openssl/include OPENSSL_LIBS="/Users/nsantos/Qt-Utils/openssl/lib/libssl.a /Users/nsantos/Qt-Utils/openssl/lib/libcrypto.a" -qtnamespace com_imaginando_qt_5_15_15 + cd qtbase + /Users/nsantos/Qt/5.15.15/src/qtbase/configure -top-level -confirm-license -recheck -prefix /Users/nsantos/Qt/5.15.15/clang_64_static -platform macx-clang -device-option QMAKE_APPLE_DEVICE_ARCHS=x86_64 arm64 -commercial -debug-and-release -static -nomake examples -nomake tests -opengl desktop -no-securetransport -openssl-linked -I/Users/nsantos/Qt-Utils/openssl/include OPENSSL_LIBS=/Users/nsantos/Qt-Utils/openssl/lib/libssl.a /Users/nsantos/Qt-Utils/openssl/lib/libcrypto.a -qtnamespace com_imaginando_qt_5_15_15 = /Users/nsantos/Qt/5.15.15/src/qtbase = /Users/nsantos/Qt/5.15.15/src/qtbase = /Users/nsantos/Qt/5.15.15/src/qtbase Creating qmake... .Done. Project ERROR: failed to parse default search paths from compiler output Thanks in advance! Regards, Nuno ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest >>> >> > ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Is still possible to build Qt 5.15.15 with macOS 14.7 and Xcode 15.2?
On Tuesday 19 November 2024 03:30:20 Pacific Standard Time Nuno Santos via Interest wrote: > Is 5.15.16, 5.15.17, 5.15.18 available in any other place? 5.15.16 is available. -- Thiago Macieira - thiago.macieira (AT) intel.com Principal Engineer - Intel DCAI Platform & System Engineering smime.p7s Description: S/MIME cryptographic signature ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Is still possible to build Qt 5.15.15 with macOS 14.7 and Xcode 15.2?
Hi Tor, I’ve only tried with Qt 5.15.15 Is 5.15.16, 5.15.17, 5.15.18 available in any other place? Thx! Regards, Nuno > On 19 Nov 2024, at 10:37, Tor Arne Vestbø wrote: > > Does this reproduce with Qt 5.15.18 ? If so please file a bug > >> On Nov 19, 2024, at 10:13, Nuno Santos via Interest >> wrote: >> >> Hi, >> >> Qt 5.X.Y platform notes says: >> >> macOS 10.13, macOS 10.14, macOS 10.15, macOS 11, macOS 12, macOS 13, macOS >> 14 x86_64 and x86_64h and arm64 Xcode 14 (13 SDK), or Xcode 15 (14 SDK) >> >> But when try to compile from source it says: >> >> Project ERROR: failed to parse default search paths from compiler output >> >> How do I see the reason of this error? >> >> ➜ src git:(v5.15.15-lts-lgpl) ✗ ./configure -confirm-license -recheck >> -prefix /Users/nsantos/Qt/5.15.15/clang_64_static -platform macx-clang >> -device-option QMAKE_APPLE_DEVICE_ARCHS="x86_64 arm64" -commercial >> -debug-and-release -static -nomake examples -nomake tests -opengl desktop >> -no-securetransport -openssl-linked >> -I/Users/nsantos/Qt-Utils/openssl/include >> OPENSSL_LIBS="/Users/nsantos/Qt-Utils/openssl/lib/libssl.a >> /Users/nsantos/Qt-Utils/openssl/lib/libcrypto.a" -qtnamespace >> com_imaginando_qt_5_15_15 >> + cd qtbase >> + /Users/nsantos/Qt/5.15.15/src/qtbase/configure -top-level -confirm-license >> -recheck -prefix /Users/nsantos/Qt/5.15.15/clang_64_static -platform >> macx-clang -device-option QMAKE_APPLE_DEVICE_ARCHS=x86_64 arm64 -commercial >> -debug-and-release -static -nomake examples -nomake tests -opengl desktop >> -no-securetransport -openssl-linked >> -I/Users/nsantos/Qt-Utils/openssl/include >> OPENSSL_LIBS=/Users/nsantos/Qt-Utils/openssl/lib/libssl.a >> /Users/nsantos/Qt-Utils/openssl/lib/libcrypto.a -qtnamespace >> com_imaginando_qt_5_15_15 >> = /Users/nsantos/Qt/5.15.15/src/qtbase >> = /Users/nsantos/Qt/5.15.15/src/qtbase >> = /Users/nsantos/Qt/5.15.15/src/qtbase >> Creating qmake... >> .Done. >> Project ERROR: failed to parse default search paths from compiler output >> >> >> Thanks in advance! >> >> Regards, >> >> Nuno >> ___ >> Interest mailing list >> Interest@qt-project.org >> https://lists.qt-project.org/listinfo/interest > ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Is still possible to build Qt 5.15.15 with macOS 14.7 and Xcode 15.2?
5.15.18 is available through the installer with an appropriate commercial license. On Nov 19, 2024, at 12:30, Nuno Santos wrote: Hi Tor, I’ve only tried with Qt 5.15.15 Is 5.15.16, 5.15.17, 5.15.18 available in any other place? Thx! Regards, Nuno On 19 Nov 2024, at 10:37, Tor Arne Vestbø wrote: Does this reproduce with Qt 5.15.18 ? If so please file a bug On Nov 19, 2024, at 10:13, Nuno Santos via Interest wrote: Hi, Qt 5.X.Y platform notes says: macOS 10.13, macOS 10.14, macOS 10.15, macOS 11, macOS 12, macOS 13, macOS 14 x86_64 and x86_64h and arm64 Xcode 14 (13 SDK), or Xcode 15 (14 SDK) But when try to compile from source it says: Project ERROR: failed to parse default search paths from compiler output How do I see the reason of this error? ➜ src git:(v5.15.15-lts-lgpl) ✗ ./configure -confirm-license -recheck -prefix /Users/nsantos/Qt/5.15.15/clang_64_static -platform macx-clang -device-option QMAKE_APPLE_DEVICE_ARCHS="x86_64 arm64" -commercial -debug-and-release -static -nomake examples -nomake tests -opengl desktop -no-securetransport -openssl-linked -I/Users/nsantos/Qt-Utils/openssl/include OPENSSL_LIBS="/Users/nsantos/Qt-Utils/openssl/lib/libssl.a /Users/nsantos/Qt-Utils/openssl/lib/libcrypto.a" -qtnamespace com_imaginando_qt_5_15_15 + cd qtbase + /Users/nsantos/Qt/5.15.15/src/qtbase/configure -top-level -confirm-license -recheck -prefix /Users/nsantos/Qt/5.15.15/clang_64_static -platform macx-clang -device-option QMAKE_APPLE_DEVICE_ARCHS=x86_64 arm64 -commercial -debug-and-release -static -nomake examples -nomake tests -opengl desktop -no-securetransport -openssl-linked -I/Users/nsantos/Qt-Utils/openssl/include OPENSSL_LIBS=/Users/nsantos/Qt-Utils/openssl/lib/libssl.a /Users/nsantos/Qt-Utils/openssl/lib/libcrypto.a -qtnamespace com_imaginando_qt_5_15_15 = /Users/nsantos/Qt/5.15.15/src/qtbase = /Users/nsantos/Qt/5.15.15/src/qtbase = /Users/nsantos/Qt/5.15.15/src/qtbase Creating qmake... .Done. Project ERROR: failed to parse default search paths from compiler output Thanks in advance! Regards, Nuno ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Is still possible to build Qt 5.15.15 with macOS 14.7 and Xcode 15.2?
Does this reproduce with Qt 5.15.18 ? If so please file a bug > On Nov 19, 2024, at 10:13, Nuno Santos via Interest > wrote: > > Hi, > > Qt 5.X.Y platform notes says: > > macOS 10.13, macOS 10.14, macOS 10.15, macOS 11, macOS 12, macOS 13, macOS 14 > x86_64 and x86_64h and arm64 Xcode 14 (13 SDK), or Xcode 15 (14 SDK) > > But when try to compile from source it says: > > Project ERROR: failed to parse default search paths from compiler output > > How do I see the reason of this error? > > ➜ src git:(v5.15.15-lts-lgpl) ✗ ./configure -confirm-license -recheck > -prefix /Users/nsantos/Qt/5.15.15/clang_64_static -platform macx-clang > -device-option QMAKE_APPLE_DEVICE_ARCHS="x86_64 arm64" -commercial > -debug-and-release -static -nomake examples -nomake tests -opengl desktop > -no-securetransport -openssl-linked -I/Users/nsantos/Qt-Utils/openssl/include > OPENSSL_LIBS="/Users/nsantos/Qt-Utils/openssl/lib/libssl.a > /Users/nsantos/Qt-Utils/openssl/lib/libcrypto.a" -qtnamespace > com_imaginando_qt_5_15_15 > + cd qtbase > + /Users/nsantos/Qt/5.15.15/src/qtbase/configure -top-level -confirm-license > -recheck -prefix /Users/nsantos/Qt/5.15.15/clang_64_static -platform > macx-clang -device-option QMAKE_APPLE_DEVICE_ARCHS=x86_64 arm64 -commercial > -debug-and-release -static -nomake examples -nomake tests -opengl desktop > -no-securetransport -openssl-linked -I/Users/nsantos/Qt-Utils/openssl/include > OPENSSL_LIBS=/Users/nsantos/Qt-Utils/openssl/lib/libssl.a > /Users/nsantos/Qt-Utils/openssl/lib/libcrypto.a -qtnamespace > com_imaginando_qt_5_15_15 > = /Users/nsantos/Qt/5.15.15/src/qtbase > = /Users/nsantos/Qt/5.15.15/src/qtbase > = /Users/nsantos/Qt/5.15.15/src/qtbase > Creating qmake... > .Done. > Project ERROR: failed to parse default search paths from compiler output > > > Thanks in advance! > > Regards, > > Nuno > ___ > Interest mailing list > Interest@qt-project.org > https://lists.qt-project.org/listinfo/interest ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Is still possible to build Qt 5.15.15 with macOS 14.7 and Xcode 15.2?
Hi, > On 19. Nov 2024, at 10:13, Nuno Santos via Interest > wrote: > > Project ERROR: failed to parse default search paths from compiler output I think this answer will be helpful: https://stackoverflow.com/questions/77136519/qmake-failing-with-sdk-14-ventura-13-5-2 ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
