[Development] Getting build flags for platforms without pkg-config

[jeandet]

Le lundi 30 octobre 2017 à 19:11 +0300, Konstantin Tokarev a écrit :
> 
> 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.
I agree, I would add that and even without pkg-config parsing pc files
seems more reasonable than parsing pri files.
> 
> > 
> > >  --
> > >  Thiago Macieira - thiago.macieira (AT) intel.com
> > >    Software Architect - Intel Open Source Technology Center
> > > 
> > >  _______________________________________________
> > >  Development mailing list
> > >  Development at qt-project.org
> > >  http://lists.qt-project.org/mailman/listinfo/development
> > 
> > --
> > Regards,
> > Konstantin
> > _______________________________________________
> > Development mailing list
> > Development at qt-project.org
> > http://lists.qt-project.org/mailman/listinfo/development
> 
>