[SOLVED] Is there a way to download/compile CELstart 1.4?

[Kriss]

Greetings! Is there any way to get it (compile/download/etc).
Because there were changes in the XML structure of the level(s) and it won't be a good idea to create something for old version of the engine.

I downloaded CS 1.4 from SVN and cs-win32libs-1.3_004 but what version of CEL do I need? CEL 1.2 or trunk?

[jorrit]

Neither. You need CEL 1.4. Always use same version of CEL with CS.

Greetings,

[Kriss]

Ooh... As usually it was my mistake that I wasn't able to find it... X)
It seems I still need a good kick to be able to do something...
Got them from here:
CS 1.4   https://crystal.svn.sourceforge.net/svnroot/crystal/CS/branches/release/V1.4/
CEL 1.4  https://cel.svn.sourceforge.net/svnroot/cel/cel/branches/release/V1.4/
Are these locations correct? Probably it will be Ok if I add them to the Subversion page?

But still I have the main question: How to compile CELstart and not just CS+CEL (if it's not too hard to do)?

[jorrit]

Yes, those locations are ok.

CELstart is included with CEL. So if you build CEL then you will have CELstart too.

Greetings,

[Kriss]

Ouch, it was too long ago when I compiled it by myself (version 0.99 or somewhere around that), so I probably didn't notice it was there...
Thanks for your answers, Jorrit!

[Kriss]

Ahem...
So I used MSVC 8 and compiled CS (static, debug) first, then did the same for CEL (also static and debug)...
But I think I should have used "release" and not "debug"...
Also, CELstart_static.exe is only 164K (for the past versions it was like 20Mb for CELstart.exe)...
And without installed python (if it's needed, then what version? 2.5.x?)
Is this wrong?

P.S. It works. I'm just curious...

[res]

Are there some DLLs with 'celstart' in the name? If so, check if celstart.exe references them (with Dependency Walker). If so, that would explain why the exe is so small.

Tho the 'static' configurations should really produce a single executable...

[Kriss]

Here's what it looks like (only what I need for CELstart to run):

Code:

   <DIR>   data
   <DIR>   test
   167 936 celstart_static.exe
 4 653 056 celstart_static_plugins-1.3-vc8_d.dll
11 857 920 celstart_static_plugins_CRYSTAL-1.3-vc8_d.dll
   290 816 celtool-1.3-vc8_d.dll
 2 719 744 cg.dll
   303 104 cgGL.dll
 4 956 160 crystalspace-1.4-vc8_d.dll
   147 456 crystalspace_directx-1.4-vc8_d.dll
   278 528 crystalspace_opengl-1.4-vc8_d.dll
    86 016 crystalspace_windows-1.4-vc8_d.dll
   110 592 lib3ds-cs.dll
    14 336 libcaca-cs.dll
 1 417 216 libcal3d-csvc8_d.dll
   258 048 libfreetype2-cs.dll
   114 688 libjpeg-cs.dll
   225 280 libmng-cs.dll
   540 672 libode-cs.dll
    17 408 libogg-cs.dll
   143 360 libpng-cs.dll
   163 840 libvorbis-cs.dll
   974 848 libvorbisenc-cs.dll
    26 624 libvorbisfile-cs.dll
    73 728 libz-cs.dll
     4 222 vfs.cfg

celstart_static.exe requires both "celstart-*" dlls and "crystal-*" dlls
That's why I asked, what I've got differs from what I've seen in "normal" CELstart.
And I compiled it without python BTW... X_X
But since it works, then I got what I wanted, though now I want to reveal the mystery of new genmesh/genmeshfact structure (I'll start another topic for this)

[res]

Just to make sure: you selected the build configuration "Debug (with static libs)", right?

[Kriss]

I chose these solution files: for CS ".\mk\msvc8\wksstatic.sln" and for CEL ".\msvc\8\wksstatic.sln"
Then the only thing I did was adding paths for includes and libraries...
As for explicitly defining "with static libs"... I'm afraid I didn't do that (used "Debug (With DLLs)")... I'll re-build CS and CEL with static libs right now, thanks for explaining... =)

BTW, what about python? I downloaded 2 versions 2.6.1 and 2.5.4 just in case...

[res]

I think right now most people still use Python 2.5.x. It's known to be working so using that you'll be on the safe side.

[Kriss]

Err... What I'd like to know is how to do that...
There's a solution file "wkspytypical.sln", for CS as an example (but I thought that "static" solutions was the way to go, besides it's for CS, not for CEL)...
There's an article (which I think can be outdated): http://www.crystalspace3d.org/main/Compiling_Python_binding_MSVC

It's not important for me actually (since I won't use python anyway), it's just since I'm compiling it anyway it won't hurt if I do it good...
Although I think this version is not final anyway...
That's what I got this time (very close to what I expected, just without python)...
http://nasa.kuz.ru/files/celstart-v1.4-static.zip (will be there for a week or two...)

[res]

Coming to think of it, there is no workspace for python + static as that would not necessarily mix well.

In particular, the python bindings build multiple native Python modules (which are DLLs). These modules need access to CS classes, so libcrystalspace needs to be linked against. Now, if a static libcrystalspace would be linked in, it would mean that each python module as well as the celstart binary would have copies of libcrystalspace in them. That can work, but it can also just as well make problems (eg data exists in multiple copied between all these modules and binaries but is not properly synchronized). Using a DLL libcrystalspace on the other hand is rather likely to work.
So on the downside, you'll have to ship the bunch of DLLs you've shown before; but on the upside, things are safer from a "will it work" perspective.

(Side note: you can cut down the number of support libraries by using the "static" version of cs-win32libs, see http://crystalspace3d.org/downloads/cs-win32libs/static/)

[res]

It's not important for me actually (since I won't use python anyway),

So you can just as well leave things as they are. If you ever want to use python you'll know what to do.

Independent of that, you may still want to check out the static cs-win32libs package.

If you distribute binaries built with VC8 don't forget the runtime DLLs. This document:
http://trac.crystalspace3d.org/trac/CS/browser/CSlibs/tags/1.3_003/Deploying%20Applications%20Built%20Against%20cs-win32libs.rtf, section "Microsoft Visual C++ 8.0 Runtime" says what you can do. (This file is also contained in the cs-win32libs package and contains other information, like what from cs-win32libs needs distributing when).

[Kriss]

Thank you for the explanations! =)