RE: VS2003-compiled WinCvs doesn't work for me...

Oliver,

I couldnt get WinCVS to compile OK with VS.NET 2003 unless I used the PSDK that came with VS.NET 2003 (ie: remove/move any other PSDK below the default SDK in the project directories preference).

Once that was done it builds and runs ok - but just testing with CVSNT 2244 - status is the only command that doesn't output anything.

I'll try and look at that a little closer tonight.

I tested using CVSNT client 2244, server 2214 and a pserver connection - the WinCVS sources/build are about a month old fromt he trunk (at the time I submitted the VS.2003 patch).

Regards,


Arthur



-----Original Message-----
From:	[email protected] on behalf of Oliver Giesen
Sent:	Fri 2/24/2006 10:06 PM
To:	[email protected]
Cc:	
Subject:	[cvsgui-dev] VS2003-compiled WinCvs doesn't work for me...

Hi all!

I'm having a bit of a problem with my build of WinCvs which I compiled using VS2003 (including all SPs, not sure which PSDK version is installed on that box - the timestamp of most of the files is Apr 2005). The build runs through without errors or warnings and when I run the app everything seems fine at first as well but...

Whenever I try to run any CVS commands there is no output (apart from the command echo) and AFAICT the commands fail. The fishes swim for a while that seems appropriate for the command in question but then they just stop and nothing else happens. It doesn't even report the exit code. This was when testing with various CVSNT 2.5.x builds.

With CVSNT 2.0.51d it seems the commands are at least partially working. Add, Remove, Commit, Log/Graph and External diff all appear to be working and Status on a touched unmodified file correctly resets the modified state. However, there is never any command output or exit code.

Any ideas what could be going wrong there? I'm not having any such problems with the official 2.0.3 build that Jerzy published.

Unfortunately my VS6 VM got corrupted by a harddisk failure and I do not have the time to set it up anew right now so the VS2003 is currently the only WinCvs-compatible build environment I have available.

Cheers,

Oliver
----	 ------------------
Skype: ogiesen
MSN:   [email protected]
ICQ:	 18777742	(http://wwp.icq.com/18777742)
Y!:    ogiesen


[Non-text portions of this message have been removed]



 
Yahoo! Groups Links



 










[Non-text portions of this message have been removed]



 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/cvsgui-dev/

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/