Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

If we want to add the Eigen library to a PROS project, we can just unzip the release version under"/include" folder.

And if you are using that, the error will occur:

Actually the error may be differ, because the function you are using is not the same as mine. But there should be an error look like this:

That means there have some type conflicts.

What’s happening is that Eigen is using the optimized vector processing provided by the Neon processor that the V5 has, that’s part of a system header file, arm_neon.h. There’s a mismatch between what that header thinks is an int32_t and what the VEX sdk thinks is an int32_t, it may be a clang/gcc difference, not sure. Anyway, for now turn off Neon detection like this and it will build.

As shown in https://www.vexforum.com/t/eigen-integration-issue/61474/6


  • No labels