C1083: Cannot open include file: 'Eigen/Eigen': No such file or directory #4265
Comments
|
@fyoda indeed this was an error in the previous release... now it's fixed in |
|
@vigsterkr Should I rebuild shogun starting from |
|
@fyoda you should be able to use eigen 3.3.4 and put there manually.. .note that you should use |
|
btw which header includes |
|
@vigsterkr I'm building the lib with MSVC 2015, the |
|
@fyoda oh so you are having this error while you are building shogun? i thought when you are using it. if it's build time problem, then there's a bug indeed |
|
I'm getting this error in both cases, when I build shogun but also when I'm using it. |
|
i'm just checking the headers and none of the external headers include the mentioned eigen3.h so you shouldn't have this problem while using shogun externally. but of course the build problem (when you try to build the library) should still be fixed... i remember that you were having some custom build mechanism. note the generated MSVC 2015 works by default - see our appveyor builds. |
|
@vigsterkr I don't have standard MSVC 2015 build mechanism. The problem with me was the debug and release build. I solved by changing manually the Runtime lib used for the debug, because it doesn't switch automatically in visual studio. |
|
@fyoda can you provide me the compiler flags for the shogun.sln? |
|
@vigsterkr In the following you can find all options for the libshogun solution:
Additional options are: |
|
ok so basically this:
should make sure that eigen is available. that dir is being created by cmake and by adding eigen to your project. check if eigen is actually there. |
|
@vigsterkr No there is no eigen folder there. The build process downloads the 3.3.4 but then it's not copied there automatically. I can try rebuilding shogun putting the eigen in that folder. |
|
mmm that's weird as this should be autogenerated by cmake. are you sure you are checking it under |
|
I'm sure, in |
|
for the sake of argument, could you create a new build directory, say |
|
Ok, I created a new
|
|
mmm that is super interesting.... so then i guess this is a bug - that i couldn't reproduce yet... could you put there ( |
|
By putting |
|
@vigsterkr Now the build process fails. Here is the error list of visual studio. shogun.lib is not generated.
|
|
doh... i dont really get why it cannot find |
|
@vigsterkr Where it should be located? |
|
@fyoda this should be in C:\Users\myUser\Downloads\shogun\build\src\shogun\lib\external\eigen |
|
@vigsterkr I'm sorry I forgot to copy that folder. C1083 solved. I still get the other errors LNK1181. |
|
mmm i'm not so sure where the linking error is coming from :( |
|
@vigsterkr By manually adding eigen folder in I still have a problem when using the lib. I cannot use Eigen within my code. If I include |
|
Fixed, the problem is that in |
|
@fyoda if you wanna use yourself Eigen for some reason in your code you need to provide the eigen for yourself. meaning: if you just simply use shogun classes you should not have problems of finding eigen, as it's actually only used during compile time of the library... ok so basically the problem here is mostly about things that got already fixed imo - in develop. i'll test it during the weekend on my windows VM just to make sure, i.e. will leave the ticket open till then |
|
Ok, thanks! Yes basically the problem is about the not copied eigen files within the build directory. |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Hello,
I'm just writing some test code using shogun lib on windows. I'm using dynamic linking against my executable.
However, I get an error when I include:
#include <shogun/mathematics/eigen3.h>The error is:
C1083: Cannot open include file: 'Eigen/Eigen': No such file or directoryWhere should be located the eigen library within the installation folder? Because I couldn't find them.
I couldn't find the eigen directory within
shogun/lib/external.Thanks
The text was updated successfully, but these errors were encountered: