CGAL users discussion list

["Hongbo Fu" <>]

Wrong setting of runtime library (under projection properties | C/C++
| Code Generation) often leads to such errors.
You can check if multi-threaded debug dll (/MDd) is used for the debug mode.

On 12/8/06, Keith Ealanta 
<>
 wrote:
> Andreas Fabri wrote:
> > 
>
>  wrote:
> >> Can anyone give me any advice on how to set-up Visual Studio 2005 to
> >> use CGAL.
> >> I'm sure if I can hack at it for a while I can get it to happen, but
> >> hopefully someone out-there has already done this and can make it easy
> >> for me.
> >>
> >> Ideally, can someone post a nice zipped up minimal project that
> >> compiles VS8?
> >>
> >> Yours hopefully,
> >>
> >> Keith Ealanta
> >>
> >>
> >
> >
> > For VC++ you should install CGAL with the selfextracting archive and not
> > use the tar.gz
> >
> > The cgal.lib is precompiled with VC7. In order to recompile go in
> > the directoy CGAL-3.2./src/CGAL, open the vcprof file and click
> > on rebuild. The same for Core, and CGALQt, if you need them (and
> > have Qt 3 for Windows).
> >
> > In the examples and demo directory, you find the .vcproj files.
> > That is clicking on it and clicking on build solution, should do it.
> >
> > There is one thing that needs attention for VC8.  Visual 8 now comes
> > with the
> > Dinkumware STL implementation. You currently have to disable two
> > checking features
> > of this STL In the IDE go to Project-> ...
> > properties->C/C++->Preprocessor and
> > add _SECURE_SCL=0 _HAS_ITERATOR_DEBUGGING=0 to "Preprocessor Definitions".
> >
> > The first define avoids warnings, the second one assertions at runtime.
> > Whereas the first one concerns a non portable "improvement" of the STL
> > which makes it less "S" (which after all stands for Standard), we work
> > on the second one.
> >
> > best regards,
> >
> > andreas
> >
> Thanks heaps for this.
> Once I'm all done I might try to throw together a quick howto you could
> put up somewhere.
>
> One issue I'm having.  I built the libraries (release and debug versions)
> When I compile a debug version of one of the examples I get the linker
> warning... (in this case I was building the Nef_2 Simple_Intersection
> example)
>
> simple_intersection.obj : error LNK2019: unresolved external symbol
> __imp___CrtDbgReportW referenced in function "public: class
> std::list<class CGAL::Extended_segment<class CGAL::Gmpz>,class
> std::allocator<class CGAL::Extended_segment<class CGAL::Gmpz> >
>  >::_Const_iterator<1> & __thiscall std::list<class
> CGAL::Extended_segment<class CGAL::Gmpz>,class std::allocator<class
> CGAL::Extended_segment<class CGAL::Gmpz> >
>  >::_Const_iterator<1>::operator--(void)"
> (??F?$_Const_iterator@$00@?$list@V?$Extended_segment@VGmpz@CGAL@@@CGAL@@V?$allocator@V?$Extended_segment@VGmpz@CGAL@@@CGAL@@@std@@@std@@QAEAAV012@XZ)
>
>
> I don't get this when I build in release, but of course that rather
> limits my debugging. Am I just doing something dumb or is there some
> other detail I've missed?
>
> Again, many thanks,
>
> Keith Ealanta


--
--------------------------------------------------------
Homepage: http://ihome.ust.hk/~fuhb
Department of Computer Science and Engineering
Hong Kong University of Science and Technology
--------------------------------------------------------