Re: [XBoard-devel] Winboard source

[Dan Jenkins]

> From: Daniel Mehrmann <address@hidden>
> Reply-To: address@hidden
> To: Dan Jenkins <address@hidden>,  XBoard Devel 
> <address@hidden>
> Subject: Re: [XBoard-devel] Winboard source
> Date: Wed, 31 Dec 2003 17:06:47 +0100
>
>
> 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.

When you created your key, did you use a password for the key?  If so, you 
need to use that same password when it asks for it here...  Otherwise, I'm 
not sure.  It does take a little bit before Savannah updates they keys on 
the server so that they work.  (They are only updated hourly, I think it 
said.)


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

I have Visual Studio 6.0 Pro, Visual Studio .Net Enterprise edition, and 
Visual Studio .Net 2003 Enterprise Edition.  (We have used Visual Studio at 
work for awhile now...) :)  When I tried the nmake, it was with my 
environment setup to use it from VC++ 6.0.  I tried it again this weekend 
after I got my savannah account working again, but it crashed on compiling 
the resources, as you stated.  I also tried compiling it with Cygwin and 
that did work, however...

> 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$)

Yeah, it does kind of stink that they have to price it like that.  I only 
have the latest version because we work with Visual Studio at my work, 
mostly using C# code.  A VS 2003 project might not be useful for you, but it 
could be for other people.  It's not something I'm too worried about, 
though.  I want to spend more time working with developing under Linux, so I 
probably wouldn't even benefit much from a VS 2003 project. :)

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

Yeah, I agree that we should agree on filenames and such.  I wasn't planning 
to make changes that are too dramatic yet...

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