Posted: Wed Nov 23, 2005 4:19 pm
Have you guys checked out Autopackage which could be a great way of supporting most distros with minimum effort.
Forums for the FreeOrion project
https://www.freeorion.org/forum/
I see... Oh well. If you want I can prepare Mandriva 2005LE rpm's as soon as the CVS is stable.Yoghurt wrote:Yes, but they also mention it doesn't really work for C++ projects.Wolverine wrote:Ok. Now I understand. However I still think that I have seen somewhere in the documentation that autopackage takes care of such things.
Posted. I found three new bugs as of now.Yoghurt wrote:Then please, please, submit bug reports ASAP, as the CVS currently is identical with the upcoming 0.3 releaseHowever the latest CVS is broken as hell.
There is a "--clean" option built-in.Wolverine wrote:Could you please make "clean" target for Scons?
Did you tell the autopackage guys about this? I'm sure they'd be either able to fix it to work on most distros or be eager to address any shortcomings you have exposed with their system.Yoghurt wrote:And as already stated earlier, I had prepared an autopackage based binary. And that wouldnt work on most distros.
I might go with the double-compile approach, but for now I have to get FO to work on my own machine (it crashes mysteriously since a while ago)autopackage homepage wrote:Important note to C++ developers
If your software uses QT/kdelibs, or just relies on large C++ libraries, then you must be careful. [...] Because of this, we cannot guarantee that your software will run on all systems. [...]Full C++ support is planned for autopackage 1.2. Our solution is to double compile C++ applications and select the correct binary at install time.
Yeah, when splitting fleet for example. :-(Yoghurt wrote:I might go with the double-compile approach, but for now I have to get FO to work on my own machine (it crashes mysteriously since a while ago)autopackage homepage wrote:Important note to C++ developers
If your software uses QT/kdelibs, or just relies on large C++ libraries, then you must be careful. [...] Because of this, we cannot guarantee that your software will run on all systems. [...]Full C++ support is planned for autopackage 1.2. Our solution is to double compile C++ applications and select the correct binary at install time.
Are you using the v0.2 download? That had known fleet splitting bugs.quork wrote:Yeah, when splitting fleet for example.
I'm using tainted source files from current CVS (20051203 11:28 GMT). GiGi doesn't install headers where it's expected (/usr/local/include/GG), so I had to copy them manually (I'm debianizing libgigi and FreeOrion builds). scons install only creates /usr/local/include/GG and copies only one header file.Geoff the Medio wrote:Are you using the v0.2 download? That had known fleet splitting bugs.quork wrote:Yeah, when splitting fleet for example. :-(
If it's happening (again) in v0.3 from CVS, then please post a bug report ASAP.