[Ves] Webinar Kiwiviewer Relesae 2.0. Feedbak
Carlos
ves at calculoandamios.com
Mon Mar 25 07:47:03 EDT 2013
Thank you for your help
I have successfully compiled and running some of the test in Visual Studio
2010 using CMake
I have needed to add some small hardcode modifications to include glew,
freeglut and compile against VTK 5.8 that is the version I’m using it but
now everything is fine.
An small step for VES but a big one for me J
Carlos
De: Joachim Pouderoux [mailto:joachim.pouderoux at kitware.com]
Enviado el: domingo, 24 de marzo de 2013 12:00
Para: Carlos
CC: Pat Marion; ves at public.kitware.com
Asunto: Re: [Ves] Webinar Kiwiviewer Relesae 2.0. Feedbak
Carlos,
The branch is on the stage repo, here:
http://vtk.org/gitweb?p=stage/VES.git;a=shortlog;h=refs/heads/fix-windows-ho
st-build
Good luck!
Joachim
Le 23 mars 2013 à 21:19, Carlos <ves at calculoandamios.com> a écrit :
Hi Joachim,
I think you are right and I’m not using the proper patch for these errors. I
have not found any reference in the downloaded code to the glew.h include.
I downloaded the versionVES-f958731 that is in the master branch that it is
related with “Fix VTK host compilation on windows.”, not VES and created by
you on 2013/03/05. This modification was added to the master branch by Pat
the following day and I assumed that it was the right one. I reach to this
snapshot through the link to github in the Kiwiviewer page
http://vtk.org/gitweb?p=VES.git;a=commit;h=f95873101e94e44560c019722c095d065
c3e07cc
This patch has a modification on the ves-superbuild.cmake
My problem is that I’m not able to find the branch you mention. In the link
from the kiwiviewer.org page I only can find three branches (master / next
/hooks). Could you please give some hints how to find this branch?
Best regards,
Carlos
De: Joachim Pouderoux [mailto:joachim.pouderoux at kitware.com]
Enviado el: viernes, 22 de marzo de 2013 23:20
Para: Carlos
CC: Pat Marion; ves at public.kitware.com
Asunto: Re: [Ves] Webinar Kiwiviewer Relesae 2.0. Feedbak
Carlos,
It seems like you are not working one the branch I mention. Type 'git
status' in the VES directory to check this. My patch requires glew and fixes
the error you mention...
Joachim
Le 22 mars 2013 à 16:19, Carlos <ves at calculoandamios.com> a écrit :
Hi,
I just set the GLUT variable in the ves-host Cmakecache.txt so this problem
is already overpassed.
No when I open the VES.Sln in the suggested folder and try to build the
projects, there are a bunch of other problems that appears (more than 800
for the Ves project). Most of them are related to the gl.h header and are:
Error 27 error C2086: 'int APIENTRY' : redefinition
c:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\include\GL\gl.h 1155
1 ves
Error 108 error C2086: 'int WINGDIAPI' : redefinition
c:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\include\GL\gl.h 1167
1 ves
After a google search, it seems that these can be solved adding #include
<windows.h>in vesgl.h before calling gl/gl.h.
At this point, the error number is reduced to 49 with three main types:
Error 29 error C1083: Cannot open include file: 'tr1/memory':
No such file or directory
c:\users\carlos\ves_windows\ves-4a31e6c\src\ves\vesSharedPtr.h 25
1 ves
Error 17 error C1083: Cannot open include file: 'GL/glext.h':
No such file or directory
c:\users\carlos\ves_windows\ves-4a31e6c\src\ves\vesGL.h 32 1
ves
Error 14 error C2719: 'matrix': formal parameter with
__declspec(align('16')) won't be aligned
C:\Users\Carlos\VES_windows\VES-4a31e6c\src\ves\vesEigen.cpp 97
1 ves
Glext.h can be downloaded from www.opengl.org, but I do not know how to fix
the other two errors.
In vestesthelper.h in line 35 there is this sentence: #ifdef FREEGLUT.
CMake does not stablish this definition in the project so at the moment the
project does not use gl/freeglut.h. I have tried to set this variable but
the errors are maintained.
As far as I know, the tr1/memory include can be found in the Android ndk
package, that is supposed not included in the windows version and I can
found it on the branch downloaded.
Joachim in a previous post has stated that also the glew library is needed
for compiling in windows but until now I do not see any reference to it.
I do not understand either the other error in vesEigen.cpp. It could be
related with the warning from Joachim as I use Visual Studio 2010 instead as
2012.
Any help will be appreciate.
Regards,
Carlos
De: Pat Marion [mailto:pat.marion at kitware.com]
Enviado el: viernes, 22 de marzo de 2013 13:32
Para: Carlos
CC: Joachim Pouderoux; ves at public.kitware.com
Asunto: Re: [Ves] Webinar Kiwiviewer Relesae 2.0. Feedbak
VES uses a superbuild. From the build directory, you should edit:
CMakeExternals/Build/ves-host/CMakeCache.txt and set the variables for GLUT
there. You can stop using the top level visual studio sln file, instead use
the sln file in CMakeExternals/Build/ves-host in order to see the ves
targets.
We can fix our cmake scripts so that you can pass the GLUT library variables
at the top level so you can avoid your issue in the future.
Pat
On Fri, Mar 22, 2013 at 10:24 PM, Carlos <ves at calculoandamios.com> wrote:
Hi,
Thank you for your guiding.
I have downloaded the fix-windows-host-build tree and perform the following
steps:
1. Use CMake to create a Visual Studio 2010 project. It works well and
it creates a solution without any error. (I have selected the
VES_Host_Superbuild option).
2. Open the .sln project and try to compile the three projects created
(eigen, vtk-host and ves-host).
3. In this step the first problem is that the eigen .gz file can not
be downloaded. Visual studio creates the 3.1.2.tar.gz file with 0 kb. As in
the output window appears the link to the compressed file it can be
downloaded and after rename it the process can continue.
4. Then, the output window gives a message saying that Doxigen is not
found. Just to be sure that the problem I have installed doxygen and after
create again the solution with CMake this error disappears.
Now the problem is that the compiler is asking for the freeglut library. I
have downloaded binaries for this library but I do not know how to set the
GLUT_glut_LIBRARY (ADVANCED) variable to point to freeglut.lib. I have made
a try modifying the CMakeCache.txt including the line:
GLUT_glut_LIBRARY:STATIC=C:/Users/Carlos/VES_windows/VES-4a31e6c/freeglut/li
b/freeglut.lib
But the error still persists.
I must mention that CMake does not ask for this variable during the
configure stage.
When I try to build eigen and vtk-host, the result is successful but I’m
thinking that this message related to the downloading / configuration
process of the project but not for the compile itself as I have not found
any library and the time needed is quit short.
The messages when I try to build ves-host are the following:
1>------ Build started: Project: ZERO_CHECK, Configuration: Debug Win32
------
2>------ Build started: Project: eigen, Configuration: Debug Win32 ------
3>------ Build started: Project: vtk-host, Configuration: Debug Win32 ------
3> Performing update step (git fetch) for 'vtk-host'
4>------ Build started: Project: ves-host, Configuration: Debug Win32 ------
4> Creating directories for 'ves-host'
4> Building Custom Rule
C:/Users/Carlos/VES_windows/VES-4a31e6c/CMakeLists.txt
4> CMake does not need to re-run because
C:\Users\Carlos\VES_windows\VES-4a31e6c\build\CMakeFiles\generate.stamp is
up-to-date.
4> No download step for 'ves-host'
4> No update step for 'ves-host'
4> No patch step for 'ves-host'
4> Performing configure step for 'ves-host'
4> -- Eigen found (include:
C:/Users/Carlos/VES_windows/VES-4a31e6c/build/CMakeExternals/Install/eigen)
4> -- Configuring incomplete, errors occurred!
4>CUSTOMBUILD : CMake error : The following variables are used in this
project, but they are set to NOTFOUND.
4> Please set them or make sure they are set and tested correctly in the
CMake files:
4> GLUT_glut_LIBRARY (ADVANCED)
4> linked by target "TestDrawPlane" in directory
C:/Users/Carlos/VES_windows/VES-4a31e6c/src/ves/Testing
4> linked by target "TestMatrix" in directory
C:/Users/Carlos/VES_windows/VES-4a31e6c/src/ves/Testing
4> linked by target "TestCap" in directory
C:/Users/Carlos/VES_windows/VES-4a31e6c/src/kiwi/Testing
4> linked by target "TestClipPlane" in directory
C:/Users/Carlos/VES_windows/VES-4a31e6c/src/kiwi/Testing
4> linked by target "TestGradientBackground" in directory
C:/Users/Carlos/VES_windows/VES-4a31e6c/src/kiwi/Testing
4> linked by target "TestKiwiViewer" in directory
C:/Users/Carlos/VES_windows/VES-4a31e6c/src/kiwi/Testing
4> linked by target "TestNoContext" in directory
C:/Users/Carlos/VES_windows/VES-4a31e6c/src/kiwi/Testing
4> linked by target "TestPointCloud" in directory
C:/Users/Carlos/VES_windows/VES-4a31e6c/src/kiwi/Testing
4> linked by target "TestTexture" in directory
C:/Users/Carlos/VES_windows/VES-4a31e6c/src/kiwi/Testing
4> linked by target "TestTexturedBackground" in directory
C:/Users/Carlos/VES_windows/VES-4a31e6c/src/kiwi/Testing
4> linked by target "TestWireframe" in directory
C:/Users/Carlos/VES_windows/VES-4a31e6c/src/kiwi/Testing
4>
========== Build: 3 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
Best regards,
Carlos
De: Joachim Pouderoux [mailto:joachim.pouderoux at kitware.com]
Enviado el: viernes, 22 de marzo de 2013 10:54
Para: Carlos
CC: Pat Marion; ves at public.kitware.com
Asunto: Re: [Ves] Webinar Kiwiviewer Relesae 2.0. Feedbak
Carlos,
If you want to compile VES for Windows you will have to fetch the branch
fix-windows-host-build I pushed in the VES stage repository one week ago.
Under Windows, VES will require the freeglut library and the glew library.
Do not hesitate to ask you you have compilation issues (I personnally
compiled it with VS2012, you may have some template issues with eigen on an
older version...)
Joachim
Le 21 mars 2013 à 17:16, Carlos <ves at calculoandamios.com> a écrit :
Hi Pat,
This sounds really well. I will try to compile on Windows next week and I
will give you some feedback.
Carlos
De: Pat Marion [mailto:pat.marion at kitware.com]
Enviado el: jueves, 21 de marzo de 2013 9:46
Para: Carlos
CC: ves at public.kitware.com
Asunto: Re: [Ves] Webinar Kiwiviewer Relesae 2.0. Feedbak
Hi Carlos,
Thank you for your feedback, it is very much appreciated.
Regarding debugging code: if you use the current version of master, there is
now support for compiling ves/kiwi on the desktop using desktop GL instead
of GLES2. There are test programs in src/kiwi/Testing that use GLUT to open
GL windows and run ves and kiwi code on the desktop. While I haven't tried
compiling these tests on Windows, I can verify that it works well on Linux
and OSX. I believe you can build freeglut on Windows and use that.
When I develop kiwi apps, I try to put as much logic as possible in the C++
layer and use Java or Objective-C only for native user interface code. This
way, you can test most of your app code using your preferred IDE and
debugger using your desktop's native architecture. Of course, this is not a
perfect substitute for testing the app on a real iOS or Android device, but
the compile/run/debug cycle is much more efficient.
As a start, you could look at the test file
src/kiwi/Testing/TestKiwiViewer.cpp. For build instructions, I updated the
README in Apps/iOS to describe how to do an out-of-source build. Just
create a build directory, configure with cmake, and enable
VES_HOST_SUPERBUILD to get a build that uses desktop GL.
Pat
On Thu, Mar 21, 2013 at 6:22 PM, Carlos <ves at calculoandamios.com> wrote:
Hi,
I would like to thank you the presentation you made last Thursday about the
new version of Kiwiviewer. I really appreciate it and I also would like to
give you some comments just in case they can be useful.
· The new features are cool and the look of the Kiwi version for the
Ipad is really nice, much better than the previous version.
· I consider that it can be used without or with minor modifications
as a VTK viewer for mobile devices even for commercial purposes.
· The connection with paraview shown in the webinar and the
possibility of using it as a remote viewer are also very interesting.
· I previously had downloaded the Ipad version but I think that a 20
min. webinar is quite short for showing all the capabilities of the app. for
the general audience.
· A new webinar showing technical details as it was mentioned would
be really interesting. I suggest to present the VES structure and also some
tools to use it.
· I think that the documentation available will be greatly improved
with the recorded webinar and the related presentation. Additionally it
would be really helpful if the documentation you are preparing for the GTC
2013 will be available.
Personally I’m a VTK user / developer in Windows and I would like to port
some features to mobile devices. I think that the App. is really great and
can be used as a viewer created with VTK in an easy and professional way.
But if you want to create a customized app using VES there are three main
points to solve:
1. Learn java / eclipse for android apps.
2. Buy a Mac and repeat point Nº1 for IOS
3. Manage for debugging VES code.
I find point Nº 3 as the most difficult (not tried Nº 2 yet). Actually I’m
able to compile VES in windows following the instructions on the web and
create some android apps, but I do not know how to debug C code on eclipse.
I take some inputs returning control points in variables, but it is
something painful and if something crash is almost impossible to guess the
cause. In this case, adding new features is difficult.
I understood in the webinar that this situation could be overpassed using
Xcode in IOS as it should be possible to compile and debug. This can be an
option as it is a must to create apps. for iOS. I assume that it would be
also possible to do it in the same way using eclipse as it also has C++
compiler capabilities, but I’m not been able to create a working eclipse
project with CMake in windows.
Again I appreciate the effort and support from the Kitware’s VES team and
I’m sure that in the near future more and more people will be interested on
this framework.
Best regards,
Carlos
_______________________________________________
Ves mailing list
Ves at public.kitware.com
http://public.kitware.com/cgi-bin/mailman/listinfo/ves
_______________________________________________
Ves mailing list
Ves at public.kitware.com
http://public.kitware.com/cgi-bin/mailman/listinfo/ves
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/ves/attachments/20130325/12851a64/attachment-0001.html>
More information about the Ves
mailing list