Didn't want to make that main building thread even longer. I wrote a quick tutorial about how to build OC from source.
It's meant as an entry point for absolute beginners, so it leaves out everything that's not strictly necessary. It uses OpenGL from deps instead of DirectX, for example.
It would be interesting to get some feedback from non-developers about how easy this is to follow.
It's meant as an entry point for absolute beginners, so it leaves out everything that's not strictly necessary. It uses OpenGL from deps instead of DirectX, for example.
It would be interesting to get some feedback from non-developers about how easy this is to follow.

That's obviously because Günther has optimized everything for Linux usage!11 Seriously, it's not that much easier - you need to install even more stuff and most likely will have to use the command line, which is not something the target audience of this article shouldn't need to understand.
(And yes, I'm fully aware I have opened myself to about a million different flamewars right now.)
(And yes, I'm fully aware I have opened myself to about a million different flamewars right now.)

As for me, I still didn't get TortoiseHG for Nautilus working - might be because the Mercurial version that can be installed via apt-get for Ubuntu is too old. And because I didn't know how to build a newer one from source, I gave up.
But I don't think, you need TortoiseHG on a linux-system. The console of linux is much better than the one in windows, imho.
I'm using the shell version of hg exclusively. Also, my OS is a Windows. My point being, there's people who like shells, and there's people who are discouraged from doing things when they have to remember some cryptic (or not) CLI commands.
Okay, what kind of weaknesses has cmd.exe, compared to a UNIX shell? Let's see.
[Edit Isilkor: Nipping this in the bud. Don't encourage flame wars.]
[Edit Isilkor: Nipping this in the bud. Don't encourage flame wars.]

Of course, it assumes you know how to operate a shell. One could make a tutorial which pastes those commands into a shell script and shows how to execute that by marking it as executable with a file manager, but...
Install the devel-versions of the libraries,cmake,make and gcc, run a console, type "cd Your/Clonk/Folder" then "cmake ." and "make". Then make an symbolic link or an copy of clonk into the planet folder and run it. Thats all.


The resulting build however has some problems: it doesn't start in fullscreen, and when I tried to exit the scenario, it crashed.
> The resulting build however has some problems: it doesn't start in fullscreen,
That's working as intended, if you've built in debug configuration.
> and when I tried to exit the scenario, it crashed.
Known bug, but we're not quite sure yet what's caused that.
> It doesn't start in fullscreen
Good find, this is the kind of thing you get so used to as a developer that you don't even notice it... ;)
Hm, the question is, of course, whether we want newbies to build a release build. When I find the time I would like to give some additional hints about how to explore the engine, and this is obviously easier if the audience already had a debug build ready.

So yeah, if you could have a tutorial for compiling with MinGW or somesuch that would be great.
You could try the offline install... Could help. Though a MinGW tuto would be good.


Apparently all I need now is 'aclocal' 'autoheader' 'autoconf' and 'automake'. At least those were the missing commands MSYS said it couldn't get.

Hu? Good old Microsoft is always good for surprises. What is this "second" installation step? If it's downloading the actual packages, then you must have managed to somehow block the installer from the Internet (proxy?). See Cäsar, use the offline installer then.

This is what I'm referring to:

Well, that's not very specific as the installer is downloading and installing a lot of stuff in that step. Doesn't the installer give any indication what it's doing at the point?

I'd be interesting to know whether it stopped when downloading the package... or while installing it. Maybe you had some application running in the background that blocked it?
Either way it seems most likely that your system setup is somehow at fault. If you want to find out why the installer fails, I'd suggest you try monitoring it with the Process Monitor.
Either way it seems most likely that your system setup is somehow at fault. If you want to find out why the installer fails, I'd suggest you try monitoring it with the Process Monitor.

CMake Error: CMake was unable to find a build program corresponding to "Visual Studio 9 2008". CMAKE_MAKE_PROGRAM is not set. You probably need to select a different build tool.
CMake Error: Could not find cmake module file:C:/Program Files (x86)/OpenClonk/planet/CMakeFiles/CMakeCXXCompiler.cmake
CMake Error: Could not find cmake module file:C:/Program Files (x86)/OpenClonk/planet/CMakeFiles/CMakeCCompiler.cmake


EDIT: Though you will probably not have cmake command available there...
Updated for Windows 10 and MSVC 2015. Because we really shouldn't have a build guide that just doesn't work.
... yes, that's a good reason to reply to a 2216 days old thread.
... yes, that's a good reason to reply to a 2216 days old thread.
Powered by mwForum 2.29.7 © 1999-2015 Markus Wichitill