Is your Client Crashing? This might fix it...

woo · Post by **woo** » Sun Feb 20, 2005 6:20 pm

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

cavesomething · Post by **cavesomething** » Sun Feb 20, 2005 7:12 pm

or you could build a client from latest CVS, MWedel committed a patch that should work around the problem.

Rednaxela · Post by **Rednaxela** » Sun Feb 20, 2005 8:32 pm

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.

bort · Post by **bort** » Mon Feb 21, 2005 6:25 am

OR wait for a coder to package the CVS into a .deb or .rpm for you.

I prefer source builds myself.

cavesomething · Post by **cavesomething** » Mon Feb 21, 2005 6:35 am

That reminds me, I should get round to making myself a client slackbuild script....

bort · Post by **bort** » Mon Feb 21, 2005 7:03 am

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.

cavesomething · Post by **cavesomething** » Mon Feb 21, 2005 7:22 am

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....

bort · Post by **bort** » Tue Feb 22, 2005 12:57 am

'ey,
this is a very common problem. And since when do the FreeBSD'ers actually use CVS on their crossfire-client port?

cavesomething · Post by **cavesomething** » Tue Feb 22, 2005 5:31 pm

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

bort · Post by **bort** » Wed Feb 23, 2005 12:18 am

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,.