Discussion:
[Crystal-develop] Issues compiling on Ubuntu 13.04
Andrew Vineyard
2013-07-02 00:50:02 UTC
Permalink
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.

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.

Getting to the point of this, I'm unable to compile a few plugins. bullet.o
fails to compile, which in turn makes bullet.so fail, then shadow_psm,
unshadowed, and deferred, 4 target plugins fail.

First time posting on a mailing list, so please excuse my noob behavior.
Have a good day.

-----

The edits and tweaks made by me will be stored inside my Dropbox account in
the public folder. The link is at the bottom of this message. It's written
in a code style using comments. Hopefully nobody will have trouble reading
it the first time through. Those tweaks adjust it to handle the latest
versions of all the prerequisites mentioned on the CS SDK site for external
libraries, especially for Assimp, which according to
link<http://permalink.gmane.org/gmane.comp.lib.assimp.general/71>,
has been changed. Again, these tweaks only seem to be required for Linux.
Windows doesn't show any issues when compiling.

Configure and source tweaks:
editlog<https://dl.dropboxusercontent.com/u/58330973/editlog>
Eric Sunshine
2013-07-02 01:54:10 UTC
Permalink
Post by Andrew Vineyard
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.
Post by Andrew Vineyard
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
Christian Van Brussel
2013-07-02 12:59:57 UTC
Permalink
Post by Andrew Vineyard
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 Assimp plugin that resides in the trunk branch of CS is supposed to
work on both Assimp 2 and 3 (and supposedly with their development
branch too).

I guess here that you were running CS 2.0, is it?
Post by Andrew Vineyard
Anyways, I've had to make tweaks to the source code to make it
compile up to the bullet plugin successfully.
I've just updated the documentation in the manual for the supported
versions of the Bullet library (although the version of the manual that
is online on the CS website will not get updated before tomorrow).

We noticed previously with Frank that the Bullet library introduced some
API breakage between version 2.80 and 2.81, and that those breaks were
not easy to manage correctly in the CS plugins, and we haven't made it
yet.

So currently the version 2.81 of Bullet is to be avoided, and the
version 2.80 is the recommended one.
Post by Andrew Vineyard
Getting to the point of this, I'm unable to compile a few plugins.
bullet.o fails to compile, which in turn makes bullet.so fail, then
shadow_psm, unshadowed, and deferred, 4 target plugins fail.
As mentioned by Eric, you can open some tickets for each specific
problem if you keep having some.
Andrew Vineyard
2013-07-02 13:54:20 UTC
Permalink
I was trying to compile version 2 of CS, but as suggested, I've downloaded
the SVN of CS. Will try again.


On Tue, Jul 2, 2013 at 7:59 AM, Christian Van Brussel <
Post by Christian Van Brussel
Post by Andrew Vineyard
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 Assimp plugin that resides in the trunk branch of CS is supposed to
work on both Assimp 2 and 3 (and supposedly with their development
branch too).
I guess here that you were running CS 2.0, is it?
Post by Andrew Vineyard
Anyways, I've had to make tweaks to the source code to make it
compile up to the bullet plugin successfully.
I've just updated the documentation in the manual for the supported
versions of the Bullet library (although the version of the manual that
is online on the CS website will not get updated before tomorrow).
We noticed previously with Frank that the Bullet library introduced some
API breakage between version 2.80 and 2.81, and that those breaks were
not easy to manage correctly in the CS plugins, and we haven't made it
yet.
So currently the version 2.81 of Bullet is to be avoided, and the
version 2.80 is the recommended one.
Post by Andrew Vineyard
Getting to the point of this, I'm unable to compile a few plugins.
bullet.o fails to compile, which in turn makes bullet.so fail, then
shadow_psm, unshadowed, and deferred, 4 target plugins fail.
As mentioned by Eric, you can open some tickets for each specific
problem if you keep having some.
------------------------------------------------------------------------------
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Crystal-develop mailing list
https://lists.sourceforge.net/lists/listinfo/crystal-develop
Continue reading on narkive:
Loading...