Hi,

having next to no experience with 'cmake' (my GenToo system does it for me)
what does Eigen's cmake do?

Is it more than just copying the include directory to a suitable place?

Does it any configuration (depending on the host)?

Many thanks for an info,
Helmut.

CMake does several things, but is absolutely not required in order to just use Eigen.

CMake can install Eigen. That is just copying files to the destination. There is no configuration at that stage, Eigen does not have a "config.h" that depends on the host machine. Eigen does all its own configuration at the moment of the compilation of the code that uses Eigen, with tests like "#ifdef __GNUC__".

CMake also serves to build the documentation if you have LaTex and Doxygen installed. To see the instructions, open the file eigen2/Mainpage.dox at line 113.

CMake also serves to build the unit-tests, and the demos.

Hello
I am trying to compile Eigen and I am having troubles:
So I checked out the stable 2.0 (but same problem with the trunk one).
I do
cmake .
and everything seems to be ok (despite a warning on my cmake version - even though my version is the same as the one asked by the warning ). There I get a Makefile which seems to be ok too.
And now if I do
make
nothing happens. Literally. No error, no warning, and no compiling... I just get a new prompt. Am I missing something?
Thank you.

anthon wrote:Hello
I am trying to compile Eigen and I am having troubles:
So I checked out the stable 2.0 (but same problem with the trunk one).
I do
cmake .
and everything seems to be ok (despite a warning on my cmake version - even though my version is the same as the one asked by the warning ). There I get a Makefile which seems to be ok too.
And now if I do
make
nothing happens. Literally. No error, no warning, and no compiling... I just get a new prompt. Am I missing something?
Thank you.

first of all it is not recommended to use the source dir as the build dir.

now, what you is perfectly normal because Eigen is pure template library, there is nothing to compile ! you can use it right away ! see the the comments of bjacob just above your message, I have not much to say. ok, 3 tips:

once you have run cmake you can do:

Code: Select all

make doc (to generate the doxygen doc)
make install (to copy the header to your installation prefix)

to run the unit tests:

Code: Select all

cmake . -DEIGEN_BUILD_TESTS=on
make
ctest

that's it !

ggael wrote:

Code: Select all

make doc (to generate the doxygen doc)
make install (to copy the header to your installation prefix)

How can I specify an installation path different from /usr/local?

all is explained in the cmake doc, but the option is:

-DCMAKE_INSTALL_PREFIX=blabla

to see all options you can do in the build dir:

ccmake .

which gives you a CLI interface, or, if you have Qt and installed cmake-gui:

cmake-gui .

Spiros wrote:

ggael wrote:

Code: Select all

make doc (to generate the doxygen doc)
make install (to copy the header to your installation prefix)

How can I specify an installation path different from /usr/local?

Thank you.
I was actually expecting the demos to compile with the "make".
I cmake -DEIGEN_BUILD_DEMOS=ON and now it works! thanks again!