CMake patch

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

CMake patch

Leopold Palomo-Avellaneda
Dear people,

I send you a path (some added files and some includes) to compile openrave
with cmake. After the patch is applied, then you could do:

GNU/Linux & Mac
--------------
cd openrave
mkdir buildCMake
cd buildCMake
cmake ../
make


Windows
-----------

Run cmake and open the folder where is the openrave directory. Then create the
visual (6,7,8) project in some folder. After open Visual.


Questions
-------------

The job is NOT FINISHED. It's just a prototype to work on. I have had to add
some includes in some files. (ex. ravep.h) I have some question that I would
like to ask because I don't understand:

- Why do you use the -fno-strict-aliasing flag?
- and -fomit-frame-pointer?

are they necessary?

- I have not be able to compile the plugin playerrave. Probably because has
the libplayer dependency. Can you confirm it?

- do openrave need boost? where?

- and the ffmpeg lib?

- The idea of Openrave is to have a visual viewer, no? so _always_ is needed a
qtviewer no?


By now no more questions.

Leo


patch_cmake.zip (9K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: CMake patch

Rosen Diankov-2
hi leo,

great! Tell me when you think you are satisfied with the cmake files so I can start looking at putting them in the sf repo.

As for your questions:

-fno-strict-aliasing flag stops gcc from doing a very stupid optimization which basically introduces bugs
-fomit-frame-pointer is probably not necessary

in playerrave you have to check a couple of things, you can leave out the cmake file for now and i can pick it up later

ffmpeg is optional if users want video recordings

OpenRAVE is divided into 3 components: the core, the gui, and the scripts
Users should have the option of compiling openrave without visualization (if they want to run batch experiments). And in the future we will *probably* have the GUI be compiled as a separate module from the core.

rosen,

2008/10/22 Leopold Palomo-Avellaneda <[hidden email]>
Dear people,

I send you a path (some added files and some includes) to compile openrave
with cmake. After the patch is applied, then you could do:

GNU/Linux & Mac
--------------
cd openrave
mkdir buildCMake
cd buildCMake
cmake ../
make


Windows
-----------

Run cmake and open the folder where is the openrave directory. Then create the
visual (6,7,8) project in some folder. After open Visual.


Questions
-------------

The job is NOT FINISHED. It's just a prototype to work on. I have had to add
some includes in some files. (ex. ravep.h) I have some question that I would
like to ask because I don't understand:

- Why do you use the -fno-strict-aliasing flag?
- and -fomit-frame-pointer?

are they necessary?

- I have not be able to compile the plugin playerrave. Probably because has
the libplayer dependency. Can you confirm it?

- do openrave need boost? where?

- and the ffmpeg lib?

- The idea of Openrave is to have a visual viewer, no? so _always_ is needed a
qtviewer no?


By now no more questions.

Leo


Reply | Threaded
Open this post in threaded view
|

Re: CMake patch

Leopold Palomo-Avellaneda
A Dimecres 22 Octubre 2008, Rosen Diankov va escriure:
> hi leo,
>
> great! Tell me when you think you are satisfied with the cmake files so I
> can start looking at putting them in the sf repo.

Ok, I will try to finish it tomorrow.

> As for your questions:
>
> -fno-strict-aliasing flag stops gcc from doing a very stupid optimization
> which basically introduces bugs

ok, so added

> -fomit-frame-pointer is probably not necessary

ok, not included.

> in playerrave you have to check a couple of things, you can leave out the
> cmake file for now and i can pick it up later

Ok

> ffmpeg is optional if users want video recordings

but in the build.sh script is not used. I have not searched it, but this part
is separated?

> OpenRAVE is divided into 3 components: the core, the gui, and the scripts
> Users should have the option of compiling openrave without visualization
> (if they want to run batch experiments). And in the future we will
> *probably* have the GUI be compiled as a separate module from the core.

How about to have:
openrave/src/core
openrave/src/gui
openrave/src/scripts

I suppose that the scripts were some octave stuff, no?

Regards,

Leo


PS OTOH I need testers of the Cmakefiles, so please, if someone would like to
test it could be useful.

> rosen,
>
> 2008/10/22 Leopold Palomo-Avellaneda <[hidden email]>
>
> > Dear people,
> >
> > I send you a path (some added files and some includes) to compile
> > openrave with cmake. After the patch is applied, then you could do:
> >
> > GNU/Linux & Mac
> > --------------
> > cd openrave
> > mkdir buildCMake
> > cd buildCMake
> > cmake ../
> > make
> >
> >
> > Windows
> > -----------
> >
> > Run cmake and open the folder where is the openrave directory. Then
> > create the
> > visual (6,7,8) project in some folder. After open Visual.
> >
> >
> > Questions
> > -------------
> >
> > The job is NOT FINISHED. It's just a prototype to work on. I have had to
> > add
> > some includes in some files. (ex. ravep.h) I have some question that I
> > would
> > like to ask because I don't understand:
> >
> > - Why do you use the -fno-strict-aliasing flag?
> > - and -fomit-frame-pointer?
> >
> > are they necessary?
> >
> > - I have not be able to compile the plugin playerrave. Probably because
> > has the libplayer dependency. Can you confirm it?
> >
> > - do openrave need boost? where?
> >
> > - and the ffmpeg lib?
> >
> > - The idea of Openrave is to have a visual viewer, no? so _always_ is
> > needed a
> > qtviewer no?
> >
> >
> > By now no more questions.
> >
> > Leo




Reply | Threaded
Open this post in threaded view
|

Re: CMake patch

Leopold Palomo-Avellaneda
In reply to this post by Rosen Diankov-2
A Dimecres 22 Octubre 2008, Rosen Diankov va escriure:
> hi leo,
>
> great! Tell me when you think you are satisfied with the cmake files so I
> can start looking at putting them in the sf repo.

Hi,

I send a new version of the cmake patch. For who you want to test it:

- create a folder (ex. openrave)
$ cd folder
$ svn co https://openrave.svn.sourceforge.net/svnroot/openrave openrave
- copy the patch to the the folder
$ cd openrave
(the directory where is the co)
- apply it
$ patch -p0 < ../patch_cmake

create a temporally build dir (ex build-cmake)
$ mkdir build-cmake
$ cd build-cmake
$ ccmake ../
configure &
Chose the cmake_install_prefix that is where openrave will be installed
make
make install

the openrave compiles and install. The core and the plugins. Still needs some
work with:

- the matlab/octave stuff
- the examples
- rave-config
- the documentation (doxyfile)

But at least in my box can run.

Please, test it in windows and mac.

Regards,

Leo


patch_cmake.zip (9K) Download Attachment