On Tue, Feb 4, 2014 at 10:45 AM, Jure Varlec <jure.var...@ki.si> wrote:
> On Tuesday 04 of February 2014 09:56:01 Marcus D. Hanwell wrote:
>> Are you building with Eigen 2 or 3? I just looked at master, and
>> libavogadro/src/CMakeLists.txt adds it to the include directories, the
>> same is not true for Eigen 3. There are still a number of rough edges
>> with the Eigen 3 support, we should take a pass at getting that to
>> build consistently. A lot of people (myself included) have Eigen
>> installed and can miss this.
>>
>> I also don't see anything that defines EIGEN_INCLUDE_DIR, both
>> variants have the major version number. Hope that helps.
>
> I'm building with both. Although Eigen is a header-only library, I'm running
> Gentoo so both versions need to be installed as build-time dependencies of
> various packages, they are at /usr/include/eigen{2,3}
>
> Actually, when I touched one of CMakeLists and caused a reconfiguration, the
> problem popped out elsewhere, then disappeared later. It seems that, starting
> with an empty build directory, I have to run CMake twice, then it builds
> successfully. This behaviour seems to be consistent.
>
It is, I will see if I can reproduce. I don't even see where
EIGEN_INCLUDE_DIR would get defined, and how it would solve any
problem. A git grep for it in the source tree turns up nothing, and we
should consistently choose Eigen 2 or 3 - mixing the two would not end
well.

Thanks for your feedback, I will try to dig a little deeper when I
have some time and see if we can clean things up a little more.

Marcus

------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
_______________________________________________
Avogadro-devel mailing list
Avogadro-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/avogadro-devel

Reply via email to