Subject: CGAL users discussion list
List archive
- From: "LoadCom" <>
- To: "cgal-discuss" <>
- Subject: [cgal-discuss]lib naming of CGAL 3.3
- Date: Wed, 13 Jun 2007 20:42:09 +0800
- Organization: LoadCom
Hello,
I've found that, since v3.3, CGAL uses a new naming scheme which is in line
with that
used by boost. It's good.
But I also found that the lib names are not created by the VS.net solutions
automatically.
Instead, they are 'hard coded' in the project properties settings.
One of the result of this arrangement is that CGAL cannot automatically name
the libs for
builds that are using STLport - the lib names generated have no 'p' flag.
When I'm building my own app's that is using CGAL and also STLport
afterwards, problem will arise
because accoding the _STLPORT_VERSION macro is defined by STLport headers,
CGAL will try to
find libs with 'p' in their names.
LoadCom
2007-06-13
- [cgal-discuss]lib naming of CGAL 3.3, LoadCom, 06/13/2007
Archive powered by MHonArc 2.6.16.