I'm trying to build the latest svn version of OSG 2.8.0 on OS/X, and I'm having
a problem when building osgdb_freetype, specifically the header file ft2build.h
cannot be located:
Scanning dependencies of target osgdb_freetype
[ 98%] Building CXX object
src/osgPlugins/freetype/CMakeFiles/osgdb_fr
Robert,
as you can see, from my original post, there's no FREETYPE_INCLUDE_DIRS defined
in CMakeCache.txt, just the envvars for the two sub-paths, and the
FREETYPE_LIBRARY envvar for the library.
I'm using cmake 2.6.3, which is the most recent version.
btw, I should point out that all I'm doin
The system cmake file for FreeType on OS/X is /Applications/CMake\
2.6-3.app/Contents/share/cmake-2.6/Modules/FindFreetype.cmake
and it does set the variables:
# set the user variables
IF(FREETYPE_INCLUDE_DIR_ft2build AND FREETYPE_INCLUDE_DIR_freetype2)
SET(FREETYPE_INCLUDE_DIRS
"${FREETYPE
btw, I just noticed, the spelling of the two files is different, where you
guys capitalize the middle T.
The system file: FindFreetype.cmake
OSG: FindFreeType.cmake
would that be a problem ??
--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=8644#
the workaround of setting FREETYPE_FOUND to NO works, so CMake is definitely
picking the local version of FindFreeType.cmake
--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=8645#8645
___
osg-users mai
Robert,
I put debugging messages in FindFreeType.cmake, and the behavior is as expected
within that cmake file, i.e. FREETYPE_INCLUDE_DIRS gets set correctly.
The issue, as far as I can tell, is why cmake on os/x either isn't exporting
FREETYPE_INCLUDE_DIRS, or there's a typo somewhere outside
fyi.. the command I used to grab the svn release was:
svn checkout http://www.openscenegraph.org/svn/osg/OpenSceneGraph/trunk
OpenSceneGraph
I'm pretty certain it's the latest, as installing it creates a
/usr/local/lib/osgPlugins-2.9.1 directory.
--
Read this topic online here:
Hi,
the SWIG bindings are so useful, that it seems like a good idea to include them
with the main release, predicated with -DBUILD_SWIG_BINDINGS &
-DBUILD_PYTHON_SWIG_BINDINGS or -DBUILD_RUBY_SWIG_BINDINGS (etc..) flags.
Including them would ensure that they are kept up to date, and that any
b
Hi,
thanks for the replies.. I'd just like to state that the aim of my request is
to get the basic swig prototypes/bindings in place, to ensure their
correctness. I think that process could be automated, somewhat.
Even though the automatically generated bindings would be unwieldy for end
use
9 matches
Mail list logo