Plan for the next release

[TheAncientGoat]

When abouts will the next release be guys? I'm busy writing a Freegamer post on OpenDungeons and I think it would be a nice thing to co-ordinate with a release

[oln]

As soon as we can sort out how to make packages i believe. (Though i could make something quick and dirty with CPack)
I would want to make a few changes to the sound system though before this, so we don't have to package a library as well. (Should be able to do this next week)

[charlie]

Release early, release often!

What changes have happened in the code / models since the last release?

[svenskmand]

Regarding the building of packages, I am currently stuck with this wierd error in pbuilder:

{l Code}: {l Select All Code}

ckr@ckr-laptop:~/Desktop/ogreoggsound-1.18$ sudo pbuilder build ../*.dsc
W: /home/ckr/.pbuilderrc does not exist
I: using fakeroot in build.
I: Current time: Sun Jan 23 14:27:48 CET 2011
I: pbuilder-time-stamp: 1295789268
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/base.tgz]
I: creating local configuration
I: copying local configuration
I: mounting /proc filesystem
I: mounting /dev/pts filesystem
I: Mounting /var/cache/pbuilder/ccache
I: policy-rc.d already exists
I: Obtaining the cached apt archive contents
I: Setting up ccache
I: Installing the build-deps
 -> Attempting to satisfy build-dependencies
 -> Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team <pbuilder-maint@lists.alioth.debian.org>
Description: Dummy package to satisfy dependencies with aptitude - created by pbuilder
 This package was created automatically by pbuilder to satisfy the
 build-dependencies of the package being currently built.
Depends: debhelper (>= 7.0.50~), cmake, pkg-config, libogre-dev, libboost-thread-dev, libopenal-dev
dpkg-deb: building package `pbuilder-satisfydepends-dummy' in `/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously deselected package pbuilder-satisfydepends-dummy.
(Reading database ... 13248 files and directories currently installed.)
Unpacking pbuilder-satisfydepends-dummy (from .../pbuilder-satisfydepends-dummy.deb) ...
dpkg: dependency problems prevent configuration of pbuilder-satisfydepends-dummy:
 pbuilder-satisfydepends-dummy depends on debhelper (>= 7.0.50~); however:
  Package debhelper is not installed.
 pbuilder-satisfydepends-dummy depends on cmake; however:
  Package cmake is not installed.
 pbuilder-satisfydepends-dummy depends on pkg-config; however:
  Package pkg-config is not installed.
 pbuilder-satisfydepends-dummy depends on libogre-dev; however:
  Package libogre-dev is not installed.
 pbuilder-satisfydepends-dummy depends on libboost-thread-dev; however:
  Package libboost-thread-dev is not installed.
 pbuilder-satisfydepends-dummy depends on libopenal-dev; however:
  Package libopenal-dev is not installed.
dpkg: error processing pbuilder-satisfydepends-dummy (--install):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 pbuilder-satisfydepends-dummy
The following NEW packages will be installed:
  bsdmainutils{a} ca-certificates{a} cmake{a} cmake-data{a} debhelper{a}
  emacsen-common{a} file{a} gettext{a} gettext-base{a} groff-base{a}
  html2text{a} intltool-debian{a} libarchive1{a} libcroco3{a} libcurl3{a}
  libcurl3-gnutls{a} libexpat1{a} libgcrypt11{a} libgnutls26{a}
  libgpg-error0{a} libgssapi-krb5-2{a} libidn11{a} libk5crypto3{a}
  libkeyutils1{a} libkrb5-3{a} libkrb5support0{a} libldap-2.4-2{a}
  libmagic1{a} libpopt0{a} libsasl2-2{a} libtasn1-3{a} libunistring0{a}
  libxml2{a} libxmlrpc-core-c3{a} man-db{a} openssl{a} pkg-config{a}
  po-debconf{a}
The following partially installed packages will be configured:
  pbuilder-satisfydepends-dummy{b}
The following packages are RECOMMENDED but will NOT be installed:
  curl libmail-sendmail-perl libsasl2-modules lynx wget xml-core
0 packages upgraded, 38 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B/16.2MB of archives. After unpacking 45.2MB will be used.
The following packages have unmet dependencies:
  pbuilder-satisfydepends-dummy: Depends: libogre-dev which is a virtual package.
                                 Depends: libboost-thread-dev which is a virtual package.
                                 Depends: libopenal-dev which is a virtual package.
The following actions will resolve these dependencies:

     Remove the following packages:
1)     pbuilder-satisfydepends-dummy



The following NEW packages will be installed:
  bsdmainutils{a}
The following packages will be REMOVED:
  pbuilder-satisfydepends-dummy{a}
0 packages upgraded, 1 newly installed, 1 to remove and 0 not upgraded.
Need to get 0B/205kB of archives. After unpacking 811kB will be used.
debconf: delaying package configuration, since apt-utils is not installed
(Reading database ... 13248 files and directories currently installed.)
Removing pbuilder-satisfydepends-dummy ...
Selecting previously deselected package bsdmainutils.
(Reading database ... 13248 files and directories currently installed.)
Unpacking bsdmainutils (from .../bsdmainutils_8.0.11ubuntu1_amd64.deb) ...
Setting up bsdmainutils (8.0.11ubuntu1) ...
update-alternatives: using /usr/bin/bsd-write to provide /usr/bin/write (write) in auto mode.
update-alternatives: using /usr/bin/bsd-from to provide /usr/bin/from (from) in auto mode.
                                         
Current status: 0 broken [-1].
Aptitude couldn't satisfy the build dependencies
E: pbuilder-satisfydepends failed.
I: Copying back the cached apt archive contents
I: unmounting /var/cache/pbuilder/ccache filesystem
I: unmounting dev/pts filesystem
I: unmounting proc filesystem
I: cleaning the build env
I: removing directory /var/cache/pbuilder/build//6568 and its subdirectories
ckr@ckr-laptop:~/Desktop/ogreoggsound-1.18$


It seems like there is some dependencies that are wrong but it does not seem to say which ones :S

If anybody have any experience with packaging of ubuntu/debian packages and want to help out, then let me know

[amuzen]

Have you tested if it builds without pbuilder?

You should check that you're able to build a binary package by running in the source directory:

{l Code}: {l Select All Code}

dpkg-buildpackage

A source package suitable for uploading to Launchpad can be built with:

{l Code}: {l Select All Code}

dpkg-buildpackage -S -sa

Using pbuilder isn't actually necessary. You can just create the source package with dpkg-buildpackage, though pbuilder can be handy in verifying that the build dependencies of the package are right. I generally only use pbuilder to recheck the dependencies if I change them. Even then, I just upload the files created by dpkg-buildpackage -S -sa

[svenskmand]

Have you tested if it builds without pbuilder?

Last time I tried it compiled fine without pbuilder.

You should check that you're able to build a binary package by running in the source directory:

{l Code}: {l Select All Code}

dpkg-buildpackage

A source package suitable for uploading to Launchpad can be built with:

{l Code}: {l Select All Code}

dpkg-buildpackage -S -sa

Using pbuilder isn't actually necessary. You can just create the source package with dpkg-buildpackage, though pbuilder can be handy in verifying that the build dependencies of the package are right. I generally only use pbuilder to recheck the dependencies if I change them. Even then, I just upload the files created by dpkg-buildpackage -S -sa

I will try this thanks

[StefanP.MUC]

What I'm missing on each release is a nice-to-read changelog in the style of something like:

[Features]
- new trap: Acid Trap
- new monster: Dragon
[garphics]
- new model for Troll
- higher res textures
[Bugfixes]
- no more crash on attacking trolls with golems when one of them stands in water

What else would be nice, is a tutorial on how to get the source code working in Eclipse. I like it more than VC++ (first of all: VC++ does either cost something or needs a registration (Express Version)).

[andrewbuck]

Welcome to the forum blablub.

I don't know much about Eclipse so I don't know if the code could be worked on in there but I don't see why it wouldn't be possible. As for a changelog, all we have right now is the git and svn changelogs. It would be nice to start summarizing them into a more readable form like you described though. It could be done retroactively easily enough since we know what changed in each commit between the releases.

-Buck

[StefanP.MUC]

I already tried to get it working in Eclipse. I'm not new to programming in general (coded a lot in C# and also know C++, but never actually wrote something bigger with C++), but I never worked with version control systems and such complex C-based projects and develpoment environments (letting alone all the dependencies on other libraries like OGRE). But I really would like to contribute something. If we could get it working in Eclipse, I think I could provide some code.

edit: I'm currently trying again. Get MingW, Add MingW to PATH environment variable, then get Eclipse, then get the CDT plugin (C/C++ environment for Eclipse), then get the EGit plugin. Then Import --> Git. There will be a button to clone a remote repository (best to instantly select "development" as the default branch, so you directly get the latest code). After the repository was cloned you get the option to convert the local instance of the repository to a regular Eclipse C++ project. After this step, you should have a git-connected (means: the project has "Team" options) Eclipse C++ project containing the latest OpenDungeons code. Ii should be compilable, IF you have all the needed libraries.

Now my problem is that I don't really know what exactly I need. Something CEGUI, something OGRE, and so on. It'S in the Wiki. But their websites offer a lot of downloads, I'm not exactly sure which one I need.

[oln]

You can generate eclipse project files with CMake by the way, that's what i've used for development in linux. (Though i've been running the build commands manually)
Wiki should tell what libs are needed, though we changed something in the last commit that does some changes to this. I am going to try packaging and get a release going next week, and also update the build instructions. Can't see why it shouldn't be possible to build it with MinGW, will look at that as well.

Also, if you want to contribute, me or andrew can probably help you out over skype when available.

[StefanP.MUC]

I know what libraries, but do I need the binary or the source version (CEGUI and OGRE, for example, are providing both)?
I think I already have Eclipse + MingW running and working. Only missing stuff should be the correct libraries and setting the correct include paths in Eclipse.

[oln]

You'll need the SDK for MinGW I believe, e.g https://sourceforge.net/projects/ogre/files/ogre/1.7/OgreSDK_mingw_v1-7-2.exe/download and http://prdownloads.sourceforge.net/crayzedsgui/CEGUI-SDK-0.7.5-mingw.zip?download.

[StefanP.MUC]

Currently trying with them. I'm getting closer. Currently geeting a MingW error:
"mode_t has not been declared" in "semaphore.h"

edit: Ah, OK, I needed to add "#include <sys/stat.h>" in globals.h

edit2: Now I'm getting "expected unqualified-id before numeric constant" in Functions.cpp, line 19 (double const M_PI = 2 * acos(0.0);)

[oln]

Probably means that M_PI is not defined, which is not required by the standard.
So it would be something like

{l Code}: {l Select All Code}

#ifndef M_PI
#define M_PI 3.14159265358979323846264338327
#endif


[StefanP.MUC]

The M_PI seemed to be an encoding problem olr something. I have overwritten the original "M_PI" with "M_PI" (exactly the same) and then the error was gone. But then a hundred of new errors occured (NOT reffering to M_PI, but to other libraries and the OD code).

I gave it up for now. Why is getting in C++ coding so hard? To work with C# you download a dev environment and start coding and everything works... Why can'T it be like that with C(++)?

[charlie]

Why is getting in C++ coding so hard? To work with C# you download a dev environment and start coding and everything works... Why can'T it be like that with C(++)?

One toolchain was developed 20+ years ago and targets a variety of platforms, the other was developed in the last 10 years and targets a higher-level platform that is then abstracted out where necessary.

Simply put; in C++ you must manually deal with OS-specific implementation differences and 32bit/64bit issues mostly on your own with the help of a few libraries. C# (as with Java, and dynamic languages) target a VM which handles the OS-specific problems for you.

{l Code}: {l Select All Code}

C++ Binary
    /   \
   /  Misc Libraries
   |     |
   v     v
OS i.e. Linux, WinXP/Vista/7, etc

C# Binary
     |
   .NET
     |
    OS

[oln]

Will have to look at the mingw compiler problems, should aim at being compatible with it eventually.