Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[mysterycoder]

Now that the minor dependencies are in /etc,
should the projects for WGE point to their include directories?

or should they be copied to dependencies/includes?

or maybe should we move their headers to dependencies/includes?

[pjcast]

I think, they should point the the /etc path (all projects, except Linux CB files), as linux will mainly use pkgconfig paths.

[mysterycoder]

Sweet, its working well, I'll send you the dependencies pretty soon. Some changes in the headers might break your project files a bit in linux   But, it should only take a minute or two to fix. I would change it, but I have no internet access in Linux.

[pjcast]

Don;t worry about breaking the Linux port.. SqPlus is still not very cooperative there. And, I have little time to debug SqPlus. So, I am more interested in the windows version at this point anyway

[mysterycoder]

Ouch, with the Ogre debug dlls, the dependencies for Ringo are 300mb.

Should I leave the directory structute in-tact, and just write a wiki entry, or an install.txt on how to install the Ogre SDK and copy over the necessary files to the Ringo directories.

[pjcast]

Hmm, why do you need to have them downlaod Ogre SDK.

As for debug dll's. We don't need em. We can just stick to release builds of all our dependencies for linking to our debug build. It will decrease the download size, and make our debug build run faster. We only need to debug WGE at this point.

[mysterycoder]

If I remember correctly I had problems using dlls built against release versions of stlport, and then have the rest of the project be built against a debug stlport. As far as I know I can't link against both of them. Unless I should do a manual build of Ogre, and just remove the debugging symbols from the debug versions.

[pjcast]

Hmm.. that is an interesting point. IIRC, Stlport detects debug builds and links with the debug stlport.. So, that is a big problem... I just don't want to have to host a 300mb dependency download... That would eat away at my servers bandwidth resources. And, would take forever to upload/downlaod anyway.

Only option I can think of is, do not build WGE in debug mode on CodeBlocks + MinGW. unfortunate, but most of the debugging is done with Log's anyway, since scripts are hard to run through the visual debugger. And, in any case, there is a squirrel script debugger that can be plugged into eclipse for that.

[mysterycoder]

Is there a problem with me compiling Ogre in debug mode without the debugging symbols? It would take the size down a lot.

[pjcast]

Well, if you can get it under 20 MBs for the WGE/Ringo (or, at least +- %2 of the size of the VC depend package) CB dependencies, then go ahead...

[mysterycoder]

Sure, I'll give it a shot  

[mysterycoder]

Ok, I can't get it down low enough  , I'll leave in the option to use debug mode incase someone wants to, and they want to use their own Ogre Dlls, but I'll make the default be release

[pjcast]

Out of curiousity, how low did you get it? (And, you built with -s for strip debug symbols).

[mysterycoder]

I ended up stopping after building the Main Ogre dlls, and the debug dll alone was 10Mb. So I decided it was pretty pointless to continue, since theres no way I could get everything at 20Mb.

edit: Yup, I stripped the symbols too

[pjcast]

Hmm, that sucks, gcc on Linux can build Ogre at ~3MB with symbols tripped. Oh well.