OpenViBE forum

Good catch - the INSTALL file had gone a bit out of date. Anything about linux-init-env-command can be ignored. Fixed the file. If you want to build only some specific subtree, first build the whole OpenViBE with your component included. CMake should be able to discover your added items by browsing....

Hi xcom, the linux init env script no longer exists in the SVN version, nor is a build order txt file generated anymore. The build system has heavily changed. At the moment, the building instructions about the SVN version can be read from the INSTALL file. Let us know if you have further problems wi...

By default, the 0.15.0 build (win32-build.cmd) basically reads through the OpenViBE_build_order.txt in a loop and then tries to execute cmake+nmake for each listed directory. Perhaps echo has slipped to the build order .txt, somehow? This file is generated by win32-init_env_command.cmd If you're fee...

The file expat.h should be in dependencies/expat/Source/lib folder on Windows. Is it? I'm a bit sceptical if a driver can be added without compiling OpenViBE. Its not clear why the installer doesn't work on your machine. As far as we know, it should work. Do you have access to any other, non-identic...

This is a bit curious. Might there be a firewall on the way, blocking the .exe somehow? If you open the corresponding .nsi file in a text editor, you should be able to see which URLs it tries to download from. Can you access these locations normally from a browser? I assume you're trying the 0.15.0 ...

In principle you should be able to run the processing and BCI data-acquisition on a desktop computer or a laptop, and direct the output to a VRPN server box in OpenViBE. Then, on the remote mobile platform, you'd have just to get a VRPN client working, and make it connect to the computer where you h...

Hi, that sounds definitely a cool project to me! Just to be clear about it, by Rover do you mean http://www.robotshop.com/dagu-rover-5-2wd-tracked-chassis.html or something like http://www.carsession.com/photos/range-rover/range-rover-2wd-and-range-e-0.jpg.html If its the latter, I'd be very very ca...

Thats good to know. If python3 is interfering we may need to figure out how to ignore it.


Cheers,
Jussi

There could be something funny in your build environment. MSVCR80.DLL doesn't really sound like something OpenVibe would install. Instead, it sounds like a standard Microsoft component. Google might help here...


Good luck,
Jussi

Hello Karthiks, if you look at the error report you see that a header from Mathworks (not provided by OpenViBE) is conflicting with a header from Microsoft (not provided by OpenViBE). You might try removing <mex.h> include line from the Matlab box cpp files and see what happens, or disable building ...

Hi xcom,

you might want to try out our current SVN version. jlegeny patched the Fedora 18 build yesterday. Let us know if it doesn't work for you and we'll patch some more.


Cheers,
Jussi

Glad that you could solve your problem. As a late reply, the errors shown in the images suggest that matlab wasn't able to find the three .m files in question. Current SVN has a bit more debug output on that.


Cheers,
Jussi

There's a matlab tutorial here,

http://openvibe.inria.fr/tutorial-using ... -openvibe/

If the tutorial scenarios work for you, possibly you can start by customizing the first tutorial.


Happy hacking,
Jussi

In 0.15.0 prepackaged distributions its in dependencies\ under the openvibe install folder and called set-env.cmd. For source packages the file is created by the dependency installer .exe and is located in scripts\. We're currently working on related parts so expect SVN version to be possibly a litt...

Good catch! I'll integrate your fix to the SVN. Thank you for the patch.

Problems with ogre.h solved now? If it was unrelated, let us know. People have had some curious difficulties with it in the past.


Cheers,
Jussi