|
From: Daniel J S. <dan...@ie...> - 2012-08-27 22:19:54
|
On 08/27/2012 04:38 PM, Mojca Miklavec wrote: > On Mon, Aug 27, 2012 at 11:13 PM, Daniel J Sebald wrote: >> On 08/27/2012 04:02 PM, Mojca Miklavec wrote: >>> >>>> That should find the proper header files, but you may want to >>>> check that is in fact the case. >>> >>> >>> What exactly should I look for? >> >> >> When the actual compile commands appear on the screen during "make", check >> where the -I directories point to and that the header files in that >> directory(ies) agree with the library(ies) eventually being linked to. If >> there is some slight mismatch between those two, the routines will be found >> and run but behave erratically. > > It looks correct to me (duplicates removed): > > -L/opt/local/lib -lz -lpangocairo-1.0 -lcairo -lpangoft2-1.0 > -lpango-1.0 -lm -lfreetype -lfontconfig -lgobject-2.0 -lglib-2.0 > -lintl -framework Cocoa > > -I/opt/local/include -I/opt/local/include/glib-2.0 > -I/opt/local/lib/glib-2.0/include -I/opt/local/include/pixman-1 > -I/opt/local/include/freetype2 -I/opt/local/include/libpng14 > -I/opt/local/include/pango-1.0 -I/opt/local/include/cairo > -I/opt/local/include/QtCore -I/opt/local/include/QtGui > -I/opt/local/include/QtNetwork -I/opt/local/include/QtSvg > > Is there any function to check? Not sure. You are seeing both glib errors and pango errors. glib-2.0 looks consistent. As for pango, is there a difference between "pangocairo-1.0" and "pango-1.0", or is there some header file withing "pango-1.0" that addresses that? If you can create a Qt terminal plot using a command that doesn't have labels or text, then I would assume Qt headers/library match. I do see one small discrepancy. The header file indicates "freetype2", while the library linked in is "freetype" without the 2. Now, if there is a different library "-lfreetype2" that can be linked to, that might be where the problem resides, i.e., slightly different font definitions with a different number of descriptive variables. (I know little about Windows freetype.) I don't see how that would account for the glib errors though. Anyway, look into that: freetype2 vs. freetype library. Dan |