Page 1 of 2
Is your Client Crashing? This might fix it...
Posted: Sun Feb 20, 2005 6:20 pm
by woo
If your client is crashing when you first startup it might be due to a problem with the metaserver and bensnoodle -- long story
For now, you can get around this by adding the -server option, so to connect to metalforge it would be:
/path/to/your/client -server crossfire.metalforge.net
This will work for cfclient and gtkclient
Posted: Sun Feb 20, 2005 7:12 pm
by cavesomething
or you could build a client from latest CVS, MWedel committed a patch that should work around the problem.
Posted: Sun Feb 20, 2005 8:32 pm
by Rednaxela
cavesomething wrote:or you could build a client from latest CVS, MWedel committed a patch that should work around the problem.
*Looks at the CVS* ah, very recent, only 13 hours ago from right now.
Posted: Mon Feb 21, 2005 6:25 am
by bort
OR wait for a coder to package the CVS into a .deb or .rpm for you.
I prefer source builds myself.
Posted: Mon Feb 21, 2005 6:35 am
by cavesomething
That reminds me, I should get round to making myself a client slackbuild script....
Posted: Mon Feb 21, 2005 7:03 am
by bort
CVS is not always the best way to get a client. Sometimes code changes, especially with os-specific code, is checked in, and you need to figure a route around the os-specific code. E.G. linux uses getcurrentdirectory() while BSD uses getcwd(). And you have to change it.
Posted: Mon Feb 21, 2005 7:22 am
by cavesomething
Yeah, but BSD people know that, so act accordingly, Linux people don't but it doesn't affect me when *BSD breaks, so I am not overly bothered....
Posted: Tue Feb 22, 2005 12:57 am
by bort
'ey,
this is a very common problem. And since when do the FreeBSD'ers actually use CVS on their crossfire-client port?
Posted: Tue Feb 22, 2005 5:31 pm
by cavesomething
Still, it is nothing like the changes that need to be made to port to a windows system....
Code: Select all
$grep -iR ifdef\ FREEBSD* * | wc -l
2
$grep -iR ifdef\ win32* * | wc -l
37
certainly I know the 'ifdefs' that are most invasive and distracting when trying to read the source code.....
not to mention
Code: Select all
$wc -l crossfire/include/win32.h
138 crossfire/include/win32.h
$wc -l crossfire/server/win32.c
160 crossfire/server/win32.c
Posted: Wed Feb 23, 2005 12:18 am
by bort
Perhaps the gtk client should be split up into Unix and Windows? A Windows project because it requires a lot of ifdefs and code changes, Unix because it can be more X oriented, etc,.