A Rookie Problem Of Building Tundra With Cmake

[Chuck]

Hi,

I am a new user of RealXtend (using Unity before). I have been trying to build Tundra with prebuilt deps for few days. I followed every step in http://doc.meshmoon.com/doxygen/_build_on_windows.html, but I kept stuck in the Cmake. I chose the source code folder to C:\TundraGitTrunk, using VS2008 compiler, with Window7 64bit. But the Cmake (2.8.10.2) showed the following errors every time I tried to configure:

CMake Error at CMakeLists.txt:211 (include):

include could not find load file:

Sagase

CMake Error at CMakeLists.txt:212 (include):

include could not find load file:

ModuleSetup

CMake Error at CMakeLists.txt:213 (include):

include could not find load file:

ConfigurePackages

CMake Error at CMakeLists.txt:214 (include):

include could not find load file:

TundraInstall

CMake Error at CMakeLists.txt:215 (include):

include could not find load file:

FindOgre

CMake Error at CMakeLists.txt:216 (include):

include could not find load file:

FindDirectX

CMake Error at CMakeLists.txt:241 (setup_clean_install_step):

Unknown CMake command "setup_clean_install_step".

Configuring incomplete, errors occurred!

I have learnt a lot during these few days but I really need some instructions now, please help~

Thank you for your precious time!!

Br,

Chuck

[Jonne Nauha]

Sorry that the doxygen instructions are so out of date. We (quite) recently updated the build process for windows to build (almost) every dependency from sources. There is also a option to use prebuilt dependencies package, however am not sure if that is up to date at this point. Let me know if you have build problems with them and I'll wrap my current deps and update the scripts.

Anyways the build steps are a lot simpler now (compared to the doxygen page): https://github.com/realXtend/naali#compiling-from-sources The main Tundra readme is the place to go.

You will essentially be working with two scripts:

• tools/windows-build-deps.cmd for building all the dependencies and tools/windows-run-cmake.cmd to run the cmake with all env variables pointing to the built dependencies
• OR
• tools/windows-fetch-prebuilt-deps.cmd for fetching, unpacking the deps and running cmake with all env variables pointing to the prebuilt dependencies.

If you have hard disk space and the patience to wait for 2-3 hours I suggest you go with the full build with windows-build-deps.cmd. It will take about 25 gigs and 2-3h on a ~high end PC. Or try first with the prebuild deps, but I'm fairly sure those are out of date and the current head wont build with them. We should fix that :)

Actually there is one url bug in the build deps script, the jom download fails as its pointing to old Nokia Qt ftp. I'll fix that now so you might want to pull in latest sources.

Best regards,
Jonne Nauha
Adminotech developer

--
http://groups.google.com/group/realxtend-dev
http://wiki.realxtend.org
http://dev.realxtend.org

[Jonne Nauha]

Here https://github.com/realXtend/naali/commit/5a5a84f5d1670cc70ad127fe9730b64f2530432a

Make sure to pull that before starting the build script :) Also read and follow the instructions in the script carefully before running it https://github.com/realXtend/naali/blob/tundra2/tools/windows-build-deps.cmd#L62 They will be printed to the console when you execute it. Hit ctrl+c to abort and start setting up the tools it needs.

Best regards,
Jonne Nauha
Adminotech developer

[Chuck]

Hi Jonne,

Thank you so much for your quickly and kindly reply!! I will try it now. If there is any further problem, I will let you know~!

Br,

Chuck

[Chuck]

Hi Jonne,

I followed the instructions in the script and then run the script. But after downloading the Qt, this error jumped up;

2013-01-05 14:17:37 (4,46 MB/s) - `qt-everywhere-opensource-src-4.7.4.zip' saved [249163314]

Building Ogre prebuilt dependencies package. Please be patient, this will take a while.

MSBUILD : error MSB1009: Project file does not exist.

Switch: Dependencies\src\OgreDependencies.VS2008.sln

MSBUILD : error MSB1009: Project file does not exist.

Switch: Dependencies\src\OgreDependencies.VS2008.sln

An error occurred! Aborting!

Press any key to continue . . .

I had checked the script, and there are a lot of other dependencies between Qt and Ogre. Why the script jumped all of them? I had tried many times and I can't solve it. Do you know what is wrong?

Best wishes,

Chuck

 

On Friday, January 4, 2013 3:41:08 PM UTC+2, Jonne Nauha wrote:

[Jonne Nauha]

The script tries to keep rebuilding already built deps at a minimum. However you should in most cases see the "Skipping X, already built.." prints for them. For me it has never jumped like that but I know that editing a .bat/.cmd file and saving it while its running sometimes does similar weirdness.

The problem with doing the deps build in multiple runs is that there are a lot of cross dependencies, the order of the build is important. Many things need Qt, Boost, Ogre to be ready for usage later in the script. And our script cant detect all situations where you would for example delete deps/qt, it would not have any idea that it needs to rebuild the Qt property browser and Qt script generator libraries. You would need to know what depends on what and remove also the depending projects :P

It sounds a bit to me that you didn't get the first run completed successfully and on the next runs you have some kind of weird state that its bugging out. I suggest once you feel your env is ready to start over again by deleting /deps/*. Once you get the deps done in a single successful run you'll "never" have to touch it again, that is wait for hours, some things might get small updates but thats quite rare nowadays.

Are you running the script in the Visual Studio 2008 cmd prompt? With all the needed tools in path: svn, git, perl (this needs to be in path before git etc. or openssl will fail to build!), hg, cmake? You can test those by running the commands before running the main script.

Best regards,
Jonne Nauha
Adminotech developer

[Chuck]

Hi Jonne,

Thank you very much for your kindly reply. I can now build run the windows-build-deps.cmd successfully, cheers( I was happy too early )!! However, after building all dependencies without any errors, I run the windows-run-cmake.cmd, and there is another error that makes me helpless:

-- Could NOT find PROTOBUF (missing:  PROTOBUF_LIBRARY)

-- sagase: PROTOBUF Configure Results.

** MumblePlugin

-- -- using SPEEX

-- -- using CELT

-- -- using PROTOBUF

-- -- using OPENSSL

CMake Error at src/Application/MumblePlugin/CMakeLists.txt:149 (message):

  Protobuf was not found properly, cannot make custom build step for

  Mumble.proto

-- Configuring incomplete, errors occurred!

I can found the protobuf folder under deps, and there is libprotobuf.vcproj file in it, but I can't found any .lib files in protobuf, is it a problem? If it is, what can I do to fix the protobuf?

BTW, it showed that it can find Speex, Celt and OpenSSL.

Thank you again for everything!

Best regards,

Chuck

[Jonne Nauha]

The protobuf has been known to cause errors. The upgrade to VC2008 project files fails on some machines here: https://github.com/realXtend/naali/blob/tundra2/tools/windows-build-deps.cmd#L721

Here is some help how to work around this https://github.com/realXtend/naali/issues/535

To reconfigure after it builds ok remove tundra.sln and run tools/windows-run-cmake.cmd. I think /upgrade is used in some other projects too so you might have had other things missing as well.

Best regards,
Jonne Nauha
Adminotech developer

[Ali Kämäräinen]

Also, if you're not particularly interested in the MumbleVoip functionality, you can comment out the MumbleVoipPlugin in the CMakeBuildConfig.txt.

[Chuck]

Thank you for your help! I will try to fix it now.

Best regards

[Chuck]

Thank you for you kindly reply! Right now, I don't need the MumbleVoip function. Do you mean protobuf is only depended by MumbleVoipPlugin? So that if I comment out Mumble Voip Plugin, I don't have to fix the protobuf bug?

Best regards

[Toni Alatalo]

Chuck <yanch...@gmail.com> kirjoitti Jan 8, 2013 kello 8:58 AM:

Thank you for you kindly reply! Right now, I don't need the MumbleVoip function. Do you mean protobuf is only depended by MumbleVoipPlugin? So that if I comment out Mumble Voip Plugin, I don't have to fix the protobuf bug?

Yes.

We originally considered using protobufs also for the Tundra protocol but as kNet itself also has similar ways to define messages, and the guys were already familiar with that, ended up using kNet messages instead.

-Toni

On Monday, January 7, 2013 3:50:26 PM UTC+2, JaakkoAllander wrote:

Also, if you're not particularly interested in the MumbleVoip functionality, you can comment out the MumbleVoipPlugin in the CMakeBuildConfig.txt.

--

[Chuck]

Thank you Antont! I am trying to develop some applications with Kinect also. And I am very glad that you had shared an OpenNI plugin! After setting up the env, I will go check out your plugin. Hope it will run well~~ Thank you again for everything!

Best regards.