RE: [XBoard-devel] Winboard source

[Dan Jenkins]

See comments below:

> From: Daniel Mehrmann <address@hidden>
> To: XBoard Devel <address@hidden>
> Subject: [XBoard-devel] Winboard source
> Date: Sun, 28 Dec 2003 12:25:02 +0100
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hello all,
>
> good news: Now i can checkout cvs stuff with anonymous. My account don't
> work and i still waiting for help :(.

I still need to try and get my savannah account setup to get the files from 
CVS again too.  I've been kind of busy with the holidays and all.

You may have done all this already, but just to make sure here's how I think 
you need to get it working now.  You need to generate an ssh key with 
ssh-keygen, give the public key to Savannah via the web forms, make sure 
your environment variable CVS_RSH=ssh, and make sure you have a couple of 
lines in ~/.ssh/config that looks something like so:

Host subversions.gnu.org
       Protocol 2

Note: It used to be protocol 1, now that it's protocol 2, this might not be 
strictly necessary, though.  Like I said, I haven't tried this out yet since 
Savannah has come back up, though...


> This is the first time that i look into the wb cvs code with my Visual
> Studio and it looks like broken at all for me.
>
> 1. The sourcefiles couldn't read error free with my windows system :(
> (CF / LF line errors)

For Windows I use Cygwin's cvs/ssh.  When you install Cygwin, one of the 
first options is to use Unix or DOS style files.  If you choose DOS, it will 
automagically take care of the CRLF conversions with cvs for you.

> 2. The Visual Studio Projectfiles don't manage the right directories and
> files. (VS crashed with a DrWatson if i try to compile - never see this
> before :(( )

I never had much luck compiling from the VStudio IDE either.  However, when 
I would just use nmake on the Makefile, it compiled fine for me, last time I 
checked...

> 3. winboard.rc is complete broken.

This could be because of the CRLF problem...  Although, I did notice a 
couple of resources in there that didn't seem to want to load for some 
reason.  I never looked at it too closely, though.

> 4. The makefile don't work for me (wrong path and other stuff).
> 5. The include path of all files are broken because we have a new
> file/dir struct.
>
> I want create a complete new winboard directory with a new enviroment:
>
> 1. Create new Projectfiles (Visual Studio 6 Pro + Processor Pack addon)

I agree it would be nice to upgrade the project to at least VS 6.  If it's 
something that you guys think would be a good thing, I could also work on 
making a VS .Net 2003 project for it.  One thing nice about the 2003 VC++ 
.Net is that it's compiler is much more ANSI compliant than VC++ 6.0.  I 
went to TechEd this last summer, and I think the numbers they gave at one of 
the seminars was something like:

VC++ 6.0           76% ANSI compliant
VC++ .Net          85% ANSI compliant
gnu g++             96% ANSI compliant
VC++ .Net 2003  97% ANSI compliant

Granted, it was Microsoft employees giving the seminar, but still fairly 
impressive improvements in ANSI compliance.

> 2. Create new Makefile for Visual Studio
> 3. Repair the winboard source files (_NO_ new stuff, only compile ready)
> 4. winboard.rc: I think the best way is to use my winboard.rc of my
> latest wb-dm version (3.7b - graz WM edition). Of course cleanup some
> parts...
>
> I want create a new directory in our cvs  , for example
> winboard.cleanup, and everbody could look about the files. After all
> members says its okay we delete the old winboard directory and rename
> winboard.cleanup to winboard.

That all sounds good to me.

I haven't done much with the project for a few weeks because I've been a bit 
busy with stuff at home.  (I got engaged, the holidays, etc.)  Now that 
Savannah is up again, I will at least get my development environments setup 
to access the savannah files again, and maybe get a start on making some of 
the changes discussed about re-arranging some of the code files.

_________________________________________________________________
Take advantage of our limited-time introductory offer for dial-up Internet 
access. http://join.msn.com/?page=dept/dialup