Re: Issues compiling on Ubuntu 13.04

On Mon, Jul 1, 2013 at 8:50 PM, Andrew Vineyard <[email protected]> wrote:
> I've been trying to get the SDK compiled many times, most recently being
> successful on Windows with Python Support, and have been taking a shot at
> compiling it on Linux. However, the instructions on the website didn't help
> out all that much.

Which website instructions were you reading? Also, which version of
CS? CS 2.0 is rather old by now. There were discussions perhaps six
months ago about releasing a newer version, but that has not yet
happened. Since releases are so infrequent, the bleeding-edge version
(directly from the SVN repository) often is the best choice. It is
common that problems in the released version are already fixed in the
bleeding-edge version.

> The instructions gave me a good place to start, but it wasn't updated for
> some of the newer versions of the prerequisites. One such prerequisite
> happens to be Assimp, which is up to version 3.
>
> The SDK however is either configured for an older version, or the configure
> file needed to be updated. I'm uncertain as I was able to compile the assimp
> plugins after editing the file, among other things.
>
> Anyways, I've had to make tweaks to the source code to make it compile up to
> the bullet plugin successfully. I've never used a mailing list before, so
> I'm unsure if I'm able to add an attachment. I didn't have to tweak the
> source code for Windows, but it appears Linux is a bit more fickle about the
> code. Luckily GCC is nice enough to give a suggestion to some the problems,
> which happen to work.

Generally speaking, if you run into trouble, the mailing list is a
good place to discuss the difficulties. If an issue turns out to be an
actual problem which needs to be fixed, or if you have a patch, it is
a good idea to open a ticket at
http://trac.crystalspace3d.org/trac/CS. (Read
http://trac.crystalspace3d.org/trac/CS/wiki/Reporting%20bugs for
instructions and create an account for yourself at the CS website.) If
you do need to submit issues or patches to the tracker, place each
distinct issue in its own ticket so that it can be handled separately
from the other issues. Do not lump a bunch of unrelated fixes into a
monster problem report. Also, in order to support discussion on a
particular ticket, please use an email address for the "Reporter"
field.

-- ES

------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev