CGAL users discussion list

[David Doria <>]

On Wed, Oct 14, 2009 at 6:18 PM, Laurent Rineau (GeometryFactory) <> wrote:

Le mercredi 14 octobre 2009 23:38:54, David Doria a écrit :

> I tried to compile the Surface_reconstruction_points_3 example, and on this
> line:
> unsigned char ind[3] = {(in+1)&3,(in+2)&3,(in+3)&3};

I thought that syntax was only usable when the values in { } were constant
expressions. I do not understand why you get the following error message, but
it may be related.

> I received the error:
> error: narrowing conversion of '(((int)in1) & 3)' from 'int' to 'unsigned
> char' inside { }

> Also, I am linking to libCGAL and libtaucs but still getting lots of
>  linking errors
>
> SurfaceReconstruction.cpp:(.text.__gmpq_neg[__gmpq_neg]+0x1c): undefined
> reference to `__gmpq_set'
>
> Which other libraries do I need to link to?

gmp

--
Laurent Rineau, PhD

1) You are correct that only constants are allowed in  { } - that's why I'm confused that non-constants appear in the { } in the code I downloaded (cgal)!

2) I had to link to: CGAL, taucs, lapack, and metis. Could there be a line added to each example (or even better, each class) that says
//Required libraries: CGAL, taucs, lapack, and metis

where those libraries are clearly replaced with the libraries needed for the particular case.

3) On the "preliminaries" page: http://www.cgal.org/Manual/3.4/doc_html/cgal_manual/Preliminaries/Chapter_main.html
it says: "CAUTION: Since version 3.3.1, CGAL is no longer compatible with the official release of TAUCS (currently 2.2). Make sure to use the modified version provided in the download section. "

However, on the download page: http://www.cgal.org/cgi-bin/cgal_download.pl
It says "You can download the official release from http://www.tau.ac.il/~stoledo/taucsor download a slightly customized variant, which is simpler to install. " with no such warning. I think the warning should definitely be stated there too. In fact, is there a reason that taucs is not included in the release and needs to be installed separately? This type of thing could be an option to install in the cmake configuration file.

Thanks,

David