Hm, not sure why CMake can find your FreeType lib, but not the header.
Anyhow, fix up the include dirs for FreeType in CMake, and regenerate the
sln/proj files. osgdb_freetype should then show up as a project in VS.
   -Paul
 


  _____  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of David
Spilling
Sent: Tuesday, May 06, 2008 3:58 PM
To: OpenSceneGraph Users
Subject: [osg-users] Freetype plugin doesn't appear in project list
(OSG2.4.0, Cmake 2.4.8, Vista, Vis C++ express)


Dear OSGers,

I downloaded OSG 2.4.0 as well as the zip of Mike Weiblen's pre-built 3rd
party dependencies and used CMake 2.4.8 to generate the build "makefiles"
for Vis C++ Express on Vista. Unfortunately, there is no freetype plugin in
the project list, so, for example, the "ALL BUILD" route does not build the
freetype plugin.

I'm new to Vista, but not to OSG, and I'm a bit of a CMake newbie, but I
imagine that this is something to do with the CMake script.

As far as freetype goes, it detects the following:

FREETYPE_INCLUDE_DIR="D:/Code/3rdparty/include"
(correct, but for incorrect capitalisation of 3rdParty)

FREETYPE_INCLUDE_DIR_freetype2 ="FREETYPE_INCLUDE_DIR_freetype2-NOTFOUND"
FREETYPE_INCLUDE_DIR_ft2build  ="FREETYPE_INCLUDE_DIR_ft2build-NOTFOUND"

FREETYPE_LIBRARY="D:/Code/3rdParty/lib/freetype235.lib"
(correct)

FREETYPE_LIBRARY_DEBUG="D:/Code/3rdParty/lib/freetype235_D.lib"
(correct)


The overall build is succesfull (hence presumably freetype is located), but,
obviously, without the freetype plugin.

Does anybody have any ideas as to where I should look to see what's going
on?

Thanks in advance,

David

PS : very very minor note: Mike's extremely helpful prebuilt 3rd party
libraries contain "zlib1" and "libpng13", wheras the project settings for
the png plugin try to link to "zlib" and "libpng". Don't know which is
correct.







_______________________________________________
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Reply via email to