FATE - a user-friendly alternative to EasyGen

(CooperHawkes) #81

I just wanted to make sure that it works for the people without any special path settings :wink:
The first startup takes some time because FATE needs a shitload of libraries g On second startup the file system cache does its job or the libraries are still in memory. If it takes very long you should consider buying a new harddrive :wink:

(Yojo) #82

hehe, my hard drive goes pretty fast, searching the hole / takes only 3 minutes :wink:

blabla off topic

anyway, the first tests look nice.

(kamikazee) #83

@Cooper Hawkes: Thanks for not letting us down, I’ll have a look at it. :wink:

However, if the code was Open Source I could let my Gentoo compile the whole thing and the download would be way smaller.

(flower.Hercules) #84

I’m downloading it now, I know what you mean about nobody hosting 2.5.16…the author can’t even be bothered to respond to people that use his tool, if there was an alternative – I’d sure as hell be using it.

Will leave feedback when this gets done downloading.

You can get q3map2.5.16 from gtkradiant 1.5.0…I know 1.5.0 is a bug with a couple features, but you can still use just 1.5.0 and continue to use radiant 1.4 for mapping :wink:

(Vattu) #85

hi…

is FATE gonna support other quake engine based games like sof2, jka, q3???

it would be great if it did : )

(CooperHawkes) #86

@kamikazee: Believe me, compiling this beast from scratch is a pain in the ass, since it depends on even more libraries than GtkRadiant :wink: I will release the source code in the future… but this needs a lot of code cleanup until I am brave enough to let other people have a look at my ugly lines of code :wink:

@vattu: I never tried other engines… It might work with quake3… just give it a try and be sure to give us some feedback about your results g :wink:

(flower.Hercules) #87

It certainly can’t take longer than compiling Open Office or Mozilla from scratch :slight_smile: I bet kamikazee is one of those weak ones that got the bin :stuck_out_tongue:

(kamikazee) #88

There’s no other option, no?

So you should have got the bin as well. :smiley:
BTW: I’ve never used any binary files for my Gentoo except the bootstrap, all fresh compiled.

(flower.Hercules) #89

Only a true source fanatic will spend an entire night compiling OO:

kyle@home ~ $ genlop -t openoffice

  • app-office/openoffice

    Sun Jul 31 06:29:23 2005 >>> app-office/openoffice-1.1.4-r1
    merge time: 5 hours, 49 minutes and 46 seconds.

There is the option of mozilla-firefox-bin and openoffice-bin because they both take half-of-forever to compile…anyways, release the source :slight_smile:

(kamikazee) #90

Ever tried compiling KDE 3 on a P3?
I surely did… Now that’s wicked and takes 2 days. :stuck_out_tongue:

On topic:
I’ll have a look at the .run to see if I can’t make an ebuild or rpm of it which will configure the dependencies. Using those, it will assure the libs are installed and you get a smaller binary file.
(More about the size of the windows one)

(CooperHawkes) #91

@kamikazee: I can send you the tarballs, so you don’t have to deal with the packaged .run. Thanks 4 the offer to build a rpm. deb files anyone? g

(kamikazee) #92

I got the tarballs out of the .run just by modifying the script, don’t worry.

What’s more of a problem, is that my Mandrake (an RPM based distro) died, so I won’t be able to make an rpm.
The ebuild should work, but it takes time to find out what library is actually part of which install package.

(CooperHawkes) #93

just take the packages used by radiant
plus its c++ (aka *mm) offsprings
plus freeimage

that’s it IIRC. I can give you a detailed list on the weekend if you like.

Thanks a lot for your efforts!

(Shaderman) #94

Maybe the search function on rpmfind is helpful.

(kamikazee) #95

Heh.
Gentoo doesn’t use RPM’s, just .ebuild files to describe what can be installed. Thx anyway.

The problem mainly lies in finding out the dependencies of Fate in term of packages, and as there is no rpm or ebuild yet I’ve got to search what package supply what .so from which is linked. Ok, a .so file named libGTK.so is quite clear to identify, but there were other ones less straightforward.
I could of course reuse .so files from the large package, but Gentoo’s vision is to split up things that do not belong together and let the installer system sort out the dependencies.

(Shaderman) #96

Sorry, didn’t know that :frowning:

(flower.Hercules) #97

Copyright 1999-2005 Gentoo Foundation

Distributed under the terms of the GNU General Public License v2

$Header: /var/cvsroot/gentoo-x86/x11-wm/openbox/openbox-3.3_rc2-r2.ebuild,v 1.1 2005/12/18 19:02:05 gothgirl Exp $

inherit eutils

DESCRIPTION=“Openbox is a standards compliant, fast, light-weight, extensible window manager.”
HOMEPAGE=“http://icculus.org/openbox/”
SRC_URI=“http://icculus.org/openbox/releases/${P/_/-}.tar.gz
mirror://gentoo/ob-themes-usability.tar.bz2”

LICENSE=“GPL-2”
SLOT=“3”
KEYWORDS="~x86 ~ppc ~sparc ~alpha ~hppa ~amd64"
IUSE=“pango nls startup-notification xinerama”

RDEPEND="|| ( ( x11-libs/libXrandr
x11-libs/libXt
xinerama? ( x11-libs/libXinerama )
)
virtual/x11
)
virtual/xft
>=dev-libs/glib-2
>=media-libs/fontconfig-2
>=dev-libs/libxml2-2.0"
DEPEND="${RDEPEND}
|| ( (
xinerama? ( x11-proto/xineramaproto )
x11-proto/xextproto
x11-proto/xf86vidmodeproto
)
virtual/x11
)
pango? ( x11-libs/pango )
startup-notification? ( x11-libs/startup-notification )
dev-util/pkgconfig"

S=${WORKDIR}/${P/_/-}

src_unpack() {
unpack ${A}
epatch ${FILESDIR}/${P}-64bit-property.patch
}

src_compile() {
econf use_enable nls use_enable pango ${myconf} || die
emake || die
}

src_install() {
dodir /etc/X11/Sessions
echo “/usr/bin/openbox” > ${D}/etc/X11/Sessions/openbox
fperms a+x /etc/X11/Sessions/openbox

insinto /usr/share/xsessions
doins ${FILESDIR}/${PN}.desktop

make DESTDIR=${D} install || die
dodoc ABOUT-NLS AUTHORS CHANGELOG COMPLIANCE COPYING README

Extra styles from http://home.clara.co.uk/dpb/openbox.htm

These are included due to the poor usability of the default themes

for users with limited vision. These are based on Jimmac’s

Gorilla and Industrial themes for Metacity.

insinto /usr/share/themes
#cp -pPR ${WORKDIR}/ob-themes-usability/* ${D}/usr/share/themes
doins -r ${WORKDIR}/ob-themes-usability/*
}

Is the ebuild for openbox, for an example; however, I think Shaderman was simply referring to rpmfind, not as a reference to download rpms but because it will tell you what package (which happens to be in the Redhat format) is linked to certain libraries. It is quite helpful as a resource other than RPMs. I used it quite a bit to resolve dependencies in other distributions, like slackware. For this, Shaderman’s link and http://rpm.pbone.net/ are both quite helpful.

(kamikazee) #98

After some tries, I think it won’t help to try messing with your program and stripping all the precompiled libraries… :confused:
When running FATE on it’s own, I get

bin/fate.x86: error while loading shared libraries: libglademm-2.0.so.1: cannot open shared object file: No such file or directory
bin/fate.x86: error while loading shared libraries: libgdkmm-2.0.so.1: cannot open shared object file: No such file or directory

Gdkmm seems a part of the GTK+ package, and furthermore, I have these files:

/usr/lib/libgdkmm-2.4.so.1
/usr/lib/libglademm-2.4.so.1

Is there a substantial difference between glademm 2.0 and 2.4 in terms of compatability?
Maybe it would work better if I could compile it from source as most Gentoo packages do… :bored:

(flower.Hercules) #99

Just a thought, did you try making a sym link from 2.4 to 2.0? That would be the best indication of compatibility.

(kamikazee) #100

Ok, it could work as an experimant and I’ll give it a try tomorrow.
Compiling and linking to an existing library straight away is still the prefered method though, if possible.

I’m going to find out how GTKRadiant resolves all it’s dynamic libraries first. Maybe there’s something interesting to find there.