As it says, "when using a system SDK". If you just compile for your current system, with no SDK options, you don't need to do this.
I suppose this should be removed, since I was aiming for simple current system builds in the instructions. On Aug 2, 2012, at 11:44 PM, Noli Sicad wrote: > My QtSDK for Mac OS X is installed in: > > /Users/nsicad/QtSDK/Desktop/Qt/474/gcc/ > > See screenshot attached. > > What i am going to do inorder that qt library, include, etc can be > founded during compilation? > > This is copied (below) from Building QGIS for Mac OS ... > > ############################## > Leopard note: Qt includes a couple non-framework libraries in /usr/lib. > When using a system SDK these libraries will not be found. To fix this > problem, > add symlinks to /usr/local: > > sudo ln -s /usr/lib/libQtUiTools.a /usr/local/lib/ > sudo ln -s /usr/lib/libQtCLucene.dylib /usr/local/lib/ > > These should then be found automatically. Earlier systems > may need some help by adding '-L/usr/local/lib' to CMAKE_SHARED_LINKER_FLAGS, > CMAKE_MODULE_LINKER_FLAGS and CMAKE_EXE_LINKER_FLAGS in the cmake build. > > ################## > > From the above statements what I am going to do with my QtSDK > installation? What need to copy to /usr/lib or link? > > Thanks. > > Noli > <Screen Shot 2012-08-03 at 2.23.31 PM.png> ----- William Kyngesburye <kyngchaos*at*kyngchaos*dot*com> http://www.kyngchaos.com/ "Mon Dieu! but they are all alike. Cheating, murdering, lying, fighting, and all for things that the beasts of the jungle would not deign to possess - money to purchase the effeminate pleasures of weaklings. And yet withal bound down by silly customs that make them slaves to their unhappy lot while firm in the belief that they be the lords of creation enjoying the only real pleasures of existence.... - the wisdom of Tarzan _______________________________________________ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
