PlaneShift

Development => Development Deliberation => Topic started by: jorrit on July 29, 2004, 12:03:22 pm

Title: Compiling PS with mingw
Post by: jorrit on July 29, 2004, 12:03:22 pm
After some struggling I finally managed to get CVS/PS to compile cleanly using mingw+msys combination WITHOUT tweaking of the generated Jamconfig. The only thing you need to do is \'reimp\' to convert the mysql library for mingw (see docs/compiling-mingw32.txt for instructions) and from that point on you can configure and compile PS like on linux (at least it worked for me).

I put the required changes in CVS about an hour go so anonymous cvs will probably be updated in max 4 hours from now.

Let me know if you have any issues.

Greetings,
Title:
Post by: Kunlock on January 04, 2005, 04:33:27 pm
I know this thread is dated, but this seems to be where I am having my problems.  I followed the compiling-mingw32.txt very closely so far and I have done everything exactly as it has mentioned.  That is untill I got to the compliling of CS.  When I did the ./configure with all the parameters it went through till then end when it was executing the jam.exe commands, but then it gave me this nice little error: failed to build jam, please install manually.  I have tried this multiple times as the document suggested, but that didnt help any.  And I am unsure of what the problem is.  I run on Windows 2000 Prof.  And as far as I can tell I have done everything exactly as it asked for in the documentation so far.
Title:
Post by: jorrit on January 04, 2005, 08:15:04 pm
Quote
Originally posted by Kunlock
I know this thread is dated, but this seems to be where I am having my problems.  I followed the compiling-mingw32.txt very closely so far and I have done everything exactly as it has mentioned.  That is untill I got to the compliling of CS.  When I did the ./configure with all the parameters it went through till then end when it was executing the jam.exe commands, but then it gave me this nice little error: failed to build jam, please install manually.  I have tried this multiple times as the document suggested, but that didnt help any.  And I am unsure of what the problem is.  I run on Windows 2000 Prof.  And as far as I can tell I have done everything exactly as it asked for in the documentation so far.


Hmm... strange.  Can you tell me more precisely how you attempted to install jam? Did you put the jam executable in your path then?

Greetings,
Title:
Post by: Kunlock on January 05, 2005, 12:43:56 am
Quote
C) Use MSYS to compile Crystal Space
------------------------------------

Run MSYS from the start menu to open the shell. And switch to the Crystal
Space source using \'cd /d/Development/cs\'. Now run (note that CS uses the
JAM utility instead of make)

.../configure --enable-debug --with-libcal3d=/d/development/cal3d/ --enable-new-renderer
jam


This will build the whole of Crystal Space with the associated libraries
and demo applications. You may need to run make several times to ensure
that all the dependencies are resolved. When everything has compiled,
try running some of the demo applications to check that everything is OK.

I got to the point where I used the ./configure command that is highlighted above.  I used that command and I let it run for a while and when it finished working, I found it had this error:

http://bellsouthpwp.net/I/n/Inferno4/mingwerror.bmp
http://bellsouthpwp.net/I/n/Inferno4/mingwerror.txt
Title:
Post by: jorrit on January 05, 2005, 08:21:56 am
Quote
Originally posted by Kunlock

This will build the whole of Crystal Space with the associated libraries
and demo applications. You may need to run make several times to ensure
that all the dependencies are resolved. When everything has compiled,
try running some of the demo applications to check that everything is OK.

I got to the point where I used the ./configure command that is highlighted above.  I used that command and I let it run for a while and when it finished working, I found it had this error:

http://bellsouthpwp.net/I/n/Inferno4/mingwerror.bmp
http://bellsouthpwp.net/I/n/Inferno4/mingwerror.txt
[/QUOTE]

But what I want to know is how you installed jam then? Did you put it in the path?

Greetings,
Title:
Post by: Kunlock on January 05, 2005, 11:42:04 pm
Ok it seems to me that I have no idea what the jam executable comes from or is for that matter, as it is not mentioned in the guide except to run the ./configure and the jam command.  Could you please explain so I am not so lost?
Title:
Post by: Krogar on January 06, 2005, 05:06:47 am
Quote
Originally posted by Kunlock
Ok it seems to me that I have no idea what the jam executable comes from or is for that matter, as it is not mentioned in the guide except to run the ./configure and the jam command.  Could you please explain so I am not so lost?


You could download and install ftp://sunsite.dk/projects/crystal/support/win32/cs-win32libs-0.99r0_005.exe (http://ftp://sunsite.dk/projects/crystal/support/win32/cs-win32libs-0.99r0_005.exe) .

This package will install not only most of the libraries needed for the various CS plugin modules, but also installs a pre-built jam.exe.

After installing the above package you may also want to run the msys-support-installer (which is installed with that package), that will add the path to the installed libs and tools to your msys profile, so that all the configure scripts can find the libs/includes and the jam tool.

The only thing you need to do yourself after that is export CRYSTAL,CEL and CSCONFPATH envvars (as is described in the build instructions).

Configure and build should work now.
Title:
Post by: Ikarsik on January 11, 2005, 12:37:22 pm
wow how many mingw32 users are there in ps community

anyway does anyone get the problem where the compiler isnt seeing the header files or isnt using the preprocessor because my compiler is just reading the source files and is spewing out errors on every line that is implementing the classes etc about declaring things without types.

i think it is a problem with jam because on the same cvs i messed around with the jamfile and it only got 14 failed targets which were simple errors but not sure.