OpenViBE forum

The OpenViBE community
It is currently Wed Feb 20, 2019 8:13 pm

All times are UTC




Post new topic Reply to topic  [ 7 posts ] 
Author Message
PostPosted: Mon Jan 08, 2018 1:05 pm 
Offline

Joined: Tue Jan 03, 2017 7:12 am
Posts: 7
Dear all,

Hello. Now I want your helps with building OpenViBE 2.0.0 on windows

Here's my environment

OS: Windows 10 64 bit
Visual Studio 2013 Community

I followed the instruction on the webpage (Instructions for Building OpenViBE - Windows compilation)

Installed Openvibe files are located in C:\openvibe-src

I launched install_dependencies.cmd and installed jinja2 and finally executed build --vsbuild-all, but several errors occured

and finally it said,

Generating meta project
Parsing C:\openvibe-src\build\sdk\OpenVIBE.sln
C:\openvibe-src\build\designer\Designer.sln does not exist !
C:\openvibe-src\build\extras\OpenVIBE.sln does not exist !
Project [C:\openvibe-src\\build\OpenViBE-Meta.sln] generated

C:\openvibe-src\sdk\unit-test\openvibe-module-fs\uoFilesTestUTF.cpp : warning C4819: The file contains a character that cannot be represented in the current code page (949). Save the file in Unicode format to prevent data loss [C:\openvibe-src\build\sdk\unit-test\openvibe-module-fs\openvibe-module-fs-test-utf.vcxproj]
C:\openvibe-src\sdk\unit-test\openvibe-module-fs\uoFilesTestUTF.cpp(9): error C2001: newline in constant [C:\openvibe-src\build\sdk\unit-test\openvibe-module-fs\openvibe-module-fs-test-utf.vcxproj]

above is the errors mainly appeared.

Below URL: all text output when build --vsbuild-all was executed

https://drive.google.com/open?id=1IhiKnLW5Fmn4xGpCsMMXPg35SBgASfJQ

I don't know what I missed in the instruction.

Thank you.


Top
 Profile  
Reply with quote  
PostPosted: Tue Jan 09, 2018 8:29 am 
Offline

Joined: Tue Dec 04, 2012 3:53 pm
Posts: 777
Location: INRIA Rennes, FRANCE
Hi,

it appears that the community edition of VS doesn't handle asian unicode characters on your system. We haven't really tried VS2013 CE here; many people work with the commercial (pro) edition, or Express.

You could try to address the issue by skipping the compilation of the unit tests. Replace file sdk/unit-test/CMakeLists.txt with an empty file and try to build again.

Let us know if it works. Or if not, please paste the remaining errors here and we'll see what we can do.


Best,
Jussi


Top
 Profile  
Reply with quote  
PostPosted: Tue Jan 09, 2018 8:52 am 
Offline

Joined: Tue Jan 03, 2017 7:12 am
Posts: 7
Dear Jussi,

Hello. Thank you for your advise.

I just followed your instruction (skipping unit-test) by replacing file sdk/unit-test/CMakeLists.txt with an empty file and trying to build again.

It said that all builds were succeeded, but an error occured during building process.

Result output is attaced in the URL: https://drive.google.com/open?id=1BnC3eHtKwvwWGZsrH7vcJ_BZXJY0U5j0

I tested it with the same system (VS 2013 community).

Code:
Time Elapsed 00:00:03.08
""
Building designer
Build type is set to: MultiType.
Visual Studio 2017 detection skipped as requested
Visual Studio 2015 detection skipped as requested
Found VS120 tools at "C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\Tools\../../VC/vcvarsall.bat" ...
SDK is located at C:\openvibe-src\\dist\sdk
Microsoft (R) Build Engine version 12.0.31101.0
[Microsoft .NET Framework, version 4.0.30319.42000]
Copyright (C) Microsoft Corporation. All rights reserved.

MSBUILD : error MSB1009: Project file does not exist.
Switch: Designer.sln
An error occured during building process
""
Build type is set to: MultiType.
Visual Studio 2017 detection skipped as requested
Visual Studio 2015 detection skipped as requested
Found VS120 tools at "C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\Tools\../../VC/vcvarsall.bat" ...
SDK is located at C:\openvibe-src\\dist\sdk
Microsoft (R) Build Engine version 12.0.31101.0
[Microsoft .NET Framework, version 4.0.30319.42000]
Copyright (C) Microsoft Corporation. All rights reserved.

MSBUILD : error MSB1009: Project file does not exist.
Switch: Designer.sln
An error occured during building process
""
Building extras
No script specified. Default will be used.
Build type is set to: MultiType.
Init-env Script to be called: win32-init_env_command.cmd.
Found VS120 tools at "C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\Tools\" ...
SDK is located at C:\openvibe-src\\dist\sdk
Designer is located at C:\openvibe-src\\dist\designer

_______________________________________________________________________________

Generating makefiles for Visual Studio 12.
Building to C:\openvibe-src\\build\extras ...
-- Appending compilation flags...
-- Found Debug of sdk at C:/openvibe-src/dist/sdk/Debug
-- Found Release of sdk at C:/openvibe-src/dist/sdk/Release
CMake Error at cmake-modules/FindOVDesigner.cmake:33 (message):
  Did not find any valid build of OpenViBE Designer
Call Stack (most recent call first):
  CMakeLists.txt:98 (include)


-- Configuring incomplete, errors occurred!
See also "C:/openvibe-src/build/extras/CMakeFiles/CMakeOutput.log".

An error occured during building process

""
No script specified. Default will be used.
Build type is set to: MultiType.
Init-env Script to be called: win32-init_env_command.cmd.
Found VS120 tools at "C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\Tools\" ...
SDK is located at C:\openvibe-src\\dist\sdk
Designer is located at C:\openvibe-src\\dist\designer

_______________________________________________________________________________

Generating makefiles for Visual Studio 12.
Building to C:\openvibe-src\\build\extras ...
-- Appending compilation flags...
-- Found Debug of sdk at C:/openvibe-src/dist/sdk/Debug
-- Found Release of sdk at C:/openvibe-src/dist/sdk/Release
CMake Error at cmake-modules/FindOVDesigner.cmake:33 (message):
  Did not find any valid build of OpenViBE Designer
Call Stack (most recent call first):
  CMakeLists.txt:98 (include)


-- Configuring incomplete, errors occurred!
See also "C:/openvibe-src/build/extras/CMakeFiles/CMakeOutput.log".

An error occured during building process

""
Generating meta project
Parsing C:\openvibe-src\build\sdk\OpenVIBE.sln
C:\openvibe-src\build\designer\Designer.sln does not exist !
C:\openvibe-src\build\extras\OpenVIBE.sln does not exist !
Project [C:\openvibe-src\\build\OpenViBE-Meta.sln] generated
C:\openvibe-src>build --vsbuild-all > result.txt
CMake Error at cmake-modules/FindOVDesigner.cmake:33 (message):
  Did not find any valid build of OpenViBE Designer
Call Stack (most recent call first):
  CMakeLists.txt:98 (include)


CMake Error at cmake-modules/FindOVDesigner.cmake:33 (message):
  Did not find any valid build of OpenViBE Designer
Call Stack (most recent call first):
  CMakeLists.txt:98 (include)


Thank you.

Regards,

Kyungho Won


Top
 Profile  
Reply with quote  
PostPosted: Tue Jan 09, 2018 9:04 am 
Offline

Joined: Tue Dec 04, 2012 3:53 pm
Posts: 777
Location: INRIA Rennes, FRANCE
It looks better, but still fails for some reason. Did you try to make a clean build? To get that, either rename or delete both folders 'dist' and 'build' and after that, run again

build.cmd --vsbuild-all

Do you get the same result?

Best,
Jussi


Top
 Profile  
Reply with quote  
PostPosted: Tue Jan 09, 2018 9:25 am 
Offline

Joined: Tue Jan 03, 2017 7:12 am
Posts: 7
Oh, I forgot to make a clean build.

So I tried to make a clean build this time, and it works even though lots of warnings related to Unicode (C4819)

Can I use the whole function using the build without unit-test?

Great thanks.

Regards,

Kyungho Won


Top
 Profile  
Reply with quote  
PostPosted: Tue Jan 09, 2018 9:29 am 
Offline

Joined: Tue Dec 04, 2012 3:53 pm
Posts: 777
Location: INRIA Rennes, FRANCE
I think so. The unit tests are not needed for 'normal' use of openvibe, they just test the codebase and are only executed on demand.

The main thing to check is that designer and acquisition server that appear installed under dist/ seem to be normally functional; just try using them and see if you run into any trouble (for example related to unicode).

Cheers,
Jussi


Top
 Profile  
Reply with quote  
PostPosted: Tue Jan 09, 2018 11:01 am 
Offline

Joined: Tue Jan 03, 2017 7:12 am
Posts: 7
Sorry for late reply.

I tested basic functionals working in /dist/extras/Release.

Tested scenario:

acquisition-server - generic oscillator
designer - acquisiton client, signal display

Great thanks!

Regards,

Kyungho Won.


Top
 Profile  
Reply with quote  
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 7 posts ] 

All times are UTC


Who is online

Users browsing this forum: No registered users and 3 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group
Americanized by Maƫl Soucaze.