Full pathname to a debug build of the compiled 'xyz' boost library. Full pathname to the compiled 'xyz' Qt4 library Semi-colon separated list of library pathnames implementing the BLAS functions. Asked 16 days ago. Active 16 days ago. Viewed 33 times. In section 1. How can I remedy this? Thank you. I await your responses. Improve this question. Is your vcpkg up to date? In a less ideal world, you might have to install some required tools and third-party libraries.
This is what this page is about. Gathering all this information is called configuration. The end of the process is marked by the generation of a makefile that you can use to install CGAL. CMake maintains configuration parameters in so-called cmake variables. The next sections first present the CMake variables related to CGAL, followed by more generic variables, and finally the configuration and build processes.
CGAL has some optional components. By default all are switched ON , but some have specific dependencies in addition to the essential ones, so if you don't need those, don't hesitate to switch them OFF.
See the page Essential Third Party Libraries for more information. CGAL is distributed with a large collection of examples and demos. Additionally, even when configured with CGAL, they are not automatically built along with the libraries. You must build the examples or demos targets or IDE projects explicitly.
If you do not plan to compile any demos, you may skip some of the dependencies such as Qt , as the corresponding CGAL-libraries will not be used. Note, however, that your own demos might need these CGAL-libraries and thus their dependencies. It accepts the values Debug or Release. Note that the default value is Debug , since it is default value in CMake.
Shared Libraries. Essential Third Party Libraries. Cgal Examples and Demos. Optional Third Party Libraries. Building Cgal. Installing Cgal.
0コメント