Closed Aneoshun closed 3 years ago
Hello @Aneoshun! Thanks!
Can you give us the code of your experiment? I think that this might have to do with the order of the include headers.
Hi
I think the issue is from Sferes: we have a namespace named stat
and it conflicts with the stat function (system call) or a stat structure (struct stat stat1,
). I have run in this issue a few times already and I played with includes (e.g. including #include <sys/stat.h>
or things like #undef stat, etc.). The issue is here:
https://github.com/sferes2/sferes2/issues/103
It is clear to me that boost.process is likely to include a call to stat at some point, which would explain the issue.
I have a nsga-2 + robot_dart that works.
About the boost.process: it is currently optional. If we do not have it, we can still record videos but it is using classic unix pipes (slightly less portable and less elegant).
=> I think we should rename the namespace in sferes...
@Aneoshun can you verify that the issue is not coming from robot_dart to close this issue?
@Aneoshun can you verify that the issue is not coming from robot_dart to close this issue?
@costashatz Sorry for the delay. I agree with @jbmouret, the issue is likely to come from Sferes. Robot_dart works well on its own. I will close the issue.
Hi all,
I am trying the latest version of Robot_dart in our dev pipeline and so far everything seems to work well. Thanks for all the new features!
The only thing that is causing issues at the moment is the boost.process part in camera.hpp. While robot_dart compiles without problem, my sferes experiment (a basic MAP-Elites hexapod one) does not compile. I am using ubuntu 20.04, boost 1.71, current sferes.QD branch, yesterday's Robot_Dart master branch.
Have you observed the same issue on your side? Commenting out the #ifdef that defines ROBOT_DART_HAS_BOOST_PROCESS makes it compile, but that is not satisfactory.
Here is the config messages and compilation errors: