Re: [XBoard-devel] Winboard source

[Daniel Mehrmann]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dan Jenkins schrieb:
| 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...
|

Yes, you're right, but i used protocol 2 and i generated keys with proto
~ 2. The problem of all cvs logins was that the server asked me for a
password. That shouldn't come because my key is my auth. I really don't
know why. And i'm working with enviroments variables too. I tryed so
much but nothing works.
I know a way, doing with linux (transfer the files over a pool
partition), but i wanna work on windows too.

And WinCVS support CF/LF handling UNIX<->WIN, but it looks to me thats
not work correctly. Okay, WinCVS 1.3 is still beta, but for a long time.

[...]

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

Which version do y use ? 2003 ? Standard ? Pro ? Enterprise ?, etc....
I think there are big differents between the versions. So (see below)
that y can fine work and i'm not.


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

yeah, we need a tool that delete the empty lines on all w* files and set
correct LF/CF points.
| 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
|

Hmmm, i know that MS VS is not 100% ansi thats true. I saw it right if i
compiled homer the first time under linux. Wow - there are sooooo big
differents between MS and gcc that really unbelieve. And it's not ANSI,
its much more :(.
Creating VS 2003 project files is at the moment not usefull for me
because i only have VS 6 pro. I'm thinking a long time to update my
professional to 2003, but MS made me not good contions. I only wanna
have c++. I don't need Basic and the other stuff, but y must buy all or
the standard packet. The price was okay (so far 650 euro ~600$)



[...]
|
| That all sounds good to me.
|
Fine.

I don't like the cygwin stuff. We use it for development on work and i
will try it.

| start on making some of the changes discussed about re-arranging some
| of the code files.

On problem. I think we all agreed that a good thing and i would do the
part on the windows side. The only, but really importent thing, is that
we must take care about the pool files and vars. We should agree about
filesnames and for what we use it...


my best
Daniel
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)

iD8DBQE/8vQXPt1V5Pj1nvYRAujoAJ9pwvXj48KxwP4ytrENE67pqLRqFACgh4z7
8Y4aQ37atJwm59stN2Cssek=
=C77V
-----END PGP SIGNATURE-----