2015-01-05 10:22 GMT-02:00 Alfredo Palhares <masterk...@masterkorp.net>:
> Excerpts from René J.V. Bertin's message of 2015-01-03 11:30:01 +0100: > > On Saturday January 03 2015 03:13:41 Alfredo Palhares wrote: > > > > >But qmake calls is it with all those macro definitions: > > >- QT_GUI_LIB > > >- QT_CORE_LIB > > >- QT_SHARED > > > > > >What do these macros do ? I've tried to google the terms but no luck. > > > > Those are likely Qt internal macros, as Guido said. My guess is that > they serve to activate select parts in the headers, depending on the > application's requirements. In this case, that would be an application that > uses QtGui in addition to QtCore (not sure if you can have a Qt application > without that...) and that either uses Qt shared libraries (as opposed to > static builds) or uses Qt classes for sharing data among applications > (QSharedMemory and friends). > > > > As Guido also said: no need to worry about these. Or, AFAIK, about > "black magic" formulas involving moc and friends ... until you're really > running into failures that have no other explanation. (Which they usually > will have, just as a seemingly inexplicable bug is rarely ever due to a > compiler bug.) > I should have have stated this before, but I am moving the build system > from qmake to waf. > > Do I still have to worry about this ? Or just moc ? > > -- > Regards, > Alfredo Palhares > _______________________________________________ > Interest mailing list > Interest@qt-project.org > http://lists.qt-project.org/mailman/listinfo/interest > Try this: http://doc.qt.io/qt-5/qmake-manual.html Best Regards, Francisco
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
