On sábado, 14 de abril de 2012 10.09.56, Uwe Rathmann wrote: > On 04/13/2012 06:41 PM, Thiago Macieira wrote: > > Therefore, *ALL* Qt libraries must be either static or shared. Mixed > > builds will not be supported > > Maybe this is a silly question, but what makes a library to be a Qt > library ? > Or asking the other way round: what is the difference between a module > like QtSvg and 3rd party libraries like Qwt or Qxt - beside where they > are hosted ?
I'd say:
1) where they are installed
2) whether they use qt_module_config.prf or equivalent or a future replacement
3) whether they follow Qt conding conventions -- including headers and macros
to be used, like QT_STATIC
4) library and API naming
5) development workflow and other Qt Project rules
> As far as I understand one of the ideas behind the modularization is to
> develop modules more independent, what makes these modules sooner or
> later very similar to 3rd party libraries.
All Qt libraries are first-party: they come from the Qt Project.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-6027
Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
