[Development] Getting build flags for platforms without pkg-config
Jake.Petroules at qt.io
Mon Oct 30 18:37:19 CET 2017
> On Oct 30, 2017, at 9:11 AM, Konstantin Tokarev <annulen at yandex.ru> wrote:
> 30.10.2017, 18:53, "Konstantin Tokarev" <annulen at yandex.ru>:
>> 30.10.2017, 18:43, "Thiago Macieira" <thiago.macieira at intel.com>:
>>> On segunda-feira, 30 de outubro de 2017 08:27:02 PDT Konstantin Tokarev wrote:
>>>> >> $ cmake --find-package -DNAME=Qt5Core -DCOMPILER_ID=GNU -DLANGUAGE=CXX
>>>> >> -DMODE=COMPILE
>>>> >> -I/home/apol/devel/kde5/include/
>>>> >> -I/home/apol/devel/kde5/include/QtCore
>>>> >> -I/home/apol/devel/kde5/lib64//mkspecs/linux-g++
>>>> > -DQT_CORE_LIB is missing. Any volunteers to add it to the cmake files?
>>>> It is already set:
>>> If it's already set, why is it missing?
>> Apparently because cmake's imitation of pkg-config is half-assed.
> So, it seems to me that the most reasonable way to support more build systems
> without duplicating data between them is to enhance pkg-config support. In fact,
> .pc files can be as rich as our .pri modules, containing extra data in custom
> variables, and build systems can rely on original pkg-config tool or parse .pc files
> directly (it's a simple declarative format, if variable substitutions are not used).
> AFAIK there no technical reason why providing .pc files for MSVC and macOS
> frameworks would be impossible.
Providing pkg-config files for Qt modules is something that's high on our list for the Qbs port of Qt; it's currently being worked on.
>>> Thiago Macieira - thiago.macieira (AT) intel.com
>>> Software Architect - Intel Open Source Technology Center
>>> Development mailing list
>>> Development at qt-project.org
>> Development mailing list
>> Development at qt-project.org
> Development mailing list
> Development at qt-project.org
Jake Petroules - jake.petroules at qt.io
The Qt Company - Silicon Valley
Qbs build tool evangelist - qbs.io
More information about the Development