connection between OpenVibe

[yannick]

In fact when i click on your msdos exe, it disappears.
For the snapshot, i would like to know how i can compile vrpn openvibe with an older version 6.07 exactly?
Because vrpn client version of virtools is 6.07 and vrpn openvibe is 7.13, it's a very dangerous or not for the future application (functions, option ......)?

thanks

[yrenard]

Dear yannick,

In fact when i click on your msdos exe, it disappears.

This is why I told you to open a console use Start > Run Command > cmd

For the snapshot, i would like to know how i can compile vrpn openvibe with an older version 6.07 exactly?

First, you will have to work from sources with OpenViBE. Avoid the precompiled windows version.
Then, go on the VRPN website, download & compile the version that fits your need (e.g. 6.07). Then replace the files located in dependencies/vrpn with the files you will collect from the build.

If you don't know how to do that and need further assistance, please wait for the next release.

Because vrpn client version of virtools is 6.07 and vrpn openvibe is 7.13, it's a very dangerous or not for the future application (functions, option ......)?

It would be better if you could use the latest version... But latest version if 7.26 so even OpenViBE is not up to date

Best regards,
Yann

[yannick]

Thanks for your help, but i don't understand several things.
1)Actually, i downloaded "openvibe-0.5.0-svn1827-src.zip", i extracted the fold.
After that, i followed the instructions on openvibe website about installation (http://openvibe.inria.fr/documentation/ ... stall.html) . I lauched win32-init_env_command.cmd, so it build a lot of files.
At this moment, i would like to know :

1) Is it possible to work with the GUI ?If not, how i can work with my scenario or ho i can write a scenario?

After that, i can change vrpn to send data to virtools.

Please help me

[yrenard]

Dear yannick,

you can launch the designer from the newly created dist folder.

Yann

[yannick]

Thanks for your help yann,
In fact, i don't know how i can lauch the designer after the compilation of openvibe?

This situation is may be stupide but i have never used Openvibe in developer side.

[yrenard]

Dear yannick,

let's say you uncompressed the source archive in a folder named openvibe-src. Then after the build is complete, a folder named dist is created under the openvibe-src folder. Go in this dist folder and you'll find several .cmd scripts to launch the designer or other OpenViBE applications.

Hope this helps,
Yann

[yannick]

Sorry but i have a problem with the trunc folder.
When i try to compile with win32-build.cmd i have this message.
Can you help me to understand why i have this message, because i followed exactly that is said in the openvibe webpage.

Thanks

[yannick]

I forgot CMakefilelist.txt is in openvibe-src/openvibe/tags/

[yrenard]

Dear yannick,

thank you for your feedback. You discovered a mistake in the source archive.

Here is what you should do to get 0.5.0 compiled on windows : copy your win32-init_env_command.cmd-skeleton script to win32-init_env_command.cmd. Then edit the win32-init_env_command.cmd file and replace the line

Code: Select all

SET OpenViBE_default_branch=

by this line

Code: Select all

SET OpenViBE_default_branch=tags\0.5.0

then use win32-build.cmd to build the whole software.

Hope this helps,
Yann

[yannick]

If i can help you

In fact, i test it and i have an another error ( see this picture)

After exploration, i see this file "OpenViBE_build_order.txt", if you can see, all the lines aren't true if i understood.
See this please:
(*) modifications in the win32-init_env_command.cmd
C:\openvibe-src\scripts\..\openvibe\tags\0.5.0 ( *)
C:\openvibe-src\scripts\..\openvibe-applications\id-generator\tags\0.5.0 (*)
C:\openvibe-src\scripts\..\openvibe-modules\ebml\trunc
C:\openvibe-src\scripts\..\openvibe-modules\fs\trunc
C:\openvibe-src\scripts\..\openvibe-modules\socket\trunc
C:\openvibe-src\scripts\..\openvibe-modules\system\trunc
C:\openvibe-src\scripts\..\openvibe-modules\stream\trunc
C:\openvibe-src\scripts\..\openvibe-modules\xml\trunc
C:\openvibe-src\scripts\..\openvibe-modules\automaton\trunc
C:\openvibe-src\scripts\..\openvibe-kernel-omk\trunc
C:\openvibe-src\scripts\..\openvibe-toolkit\trunc
C:\openvibe-src\scripts\..\openvibe-plugins\acquisition\trunc
C:\openvibe-src\scripts\..\openvibe-plugins\classification\trunc
C:\openvibe-src\scripts\..\openvibe-plugins\classification-gpl\trunc
C:\openvibe-src\scripts\..\openvibe-plugins\feature-extraction\trunc
C:\openvibe-src\scripts\..\openvibe-plugins\file-io\trunc
C:\openvibe-src\scripts\..\openvibe-plugins\samples\trunc
C:\openvibe-src\scripts\..\openvibe-plugins\signal-processing\trunc
C:\openvibe-src\scripts\..\openvibe-plugins\signal-processing-gpl\trunc
C:\openvibe-src\scripts\..\openvibe-plugins\simple-visualisation\trunc
C:\openvibe-src\scripts\..\openvibe-plugins\stimulation\trunc
C:\openvibe-src\scripts\..\openvibe-plugins\stream-codecs\trunc
C:\openvibe-src\scripts\..\openvibe-plugins\streaming\trunc
C:\openvibe-src\scripts\..\openvibe-plugins\tools\trunc
C:\openvibe-src\scripts\..\openvibe-plugins\vrpn\trunc
C:\openvibe-src\scripts\..\openvibe-applications\designer\trunc
C:\openvibe-src\scripts\..\openvibe-applications\acquisition-server\trunc
C:\openvibe-src\scripts\..\openvibe-applications\plugin-inspector\trunc
C:\openvibe-src\scripts\..\openvibe-scenarios\trunc

[yrenard]

Dear yannick,

your OpenViBE_build_order.txt should contain tags\0.5.0 instead of trunc branches ! This file is generated so do no try to change is by hand. Do what I told you in the previous post !

Yann

[yannick]

In fact, i do what you said in the previous post and the result is on the screenshot (Jan 18, 2010 4:28 pm).

But after that i don't understand what is the problem exactly.

[yrenard]

Dear yannick,

please do the following :

• - double check that win32-init_env_command.cmd is correctly configured
  - run win32-clean.cmd
  - run win32-build.cmd and save the output to a log file
  - send us the win32-init_env_command.cmd file and log file of the build !

Thank you,
Yann

[yannick]

Sorry, but i cannot saved the result of .cmd command, do you know the manner to do it?
So, i send you the .cmd .
Thanks

[yannick]

Hi, this is the log file of win-build.cmd before the error.

thanks