CMake Windows build

[Doug McCorkle]

Hello,

What would be the most appropriate way to start to migrate at least the windows build towards using CMake? I know there are a number of issues on the google code page related to building on Windows and currently with the new Visual Studio releases VR Juggler is very difficult to build. I know that Ryan has this github branch:

https://github.com/rpavlik/vrjuggler/tree/cmake-master

but I have not used it. It is my understanding that some components of the build still need to be developed but I am not sure which components. Should we clone what Ryan has done as a starting place for a VR Juggler branch to start the Windows CMake migration? Ryan, is your CMake branch in sync with the VR Juggler master or does it have additional changes in it? Anyway, our team would like to figure out a way to get the Windows build in a little bit better shape than its current state. Thanks.

Doug

[Ryan Pavlik]

It's effectively complete, except for the Java parts. (The main impact to me is it can't build vrjconfig yet.) I've been using it exclusively on Linux for some time, and now that I'm looking at newer/different compilers on Windows (like vc11) I'm using it there too. (Have successfully built using vc11's v110_xp "xp-compatible" toolset, with Boost 1.54, my 1.2-branch git of cppdom, and the latest gmtl headers just copied over - see https://github.com/rpavlik/vrjuggler-windows-binaries/tree/install/vc110_xp/vrjuggler-3.0-with-deps )

My primary work is on the 3.0 branch. My workflow tends to be that I develop things on the "revised-cmake-3.0" branch, then when I get time to upstream patches, I'll go through and cherry-pick them over to topic branches and submit bugs.  (For building on Windows, I kept a branch called 3.0-improvements with those improvements merged into it, along with the occasional bug fix found when using the old build system on Windows.) I keep a tag called "last-ported-to-cmake-master" to indicate where I need to resume cherrypicking from revised-cmake-3.0 to cmake-master: the builds are pretty similar and most of the differences have been accommodated already, so that goes pretty smoothly.

Folks have been using the issues list on my github repo for build system issues.

Ryan

Doug

--

---
You received this message because you are subscribed to the Google Groups "vrjuggler-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vrjuggler-dev...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Doug McCorkle]

OK, so what are you saying would need to be done to migrate your cmake build system into the VR Juggler master?

Doug

[Doug McCorkle]

Do you have an idea of what the next step would be to migrate your cmake build system into VR Juggler master?

Doug