Re: [Mingw-users] building cvs

[Earnie B. <ea...@us...>]

Kris Warkentin wrote:
>>No, msysDTK is just a set of tools (e.g. CVS) built to use msys-1.0.dll,
> 
> and
> 
>>msysDVLPR is the compiler and linker that was used to build them. Both
>>should be installed in the MSYS directory tree, not in the MinGW tree. If
>>you don't mind using msysDVLPR then MSYS CVS should be all you need, but
> 
> if
> 
>>you prefer a MinGW build of CVS (not dependent on msys-1.0.dll) then you
>>should get the official source (IIRC its at cvshome.org) or get cvsNT. I
>>have build CVS using MinGW before, but I haven't built SSH and I suspect
>>that it is more difficult. I only use MSYS CVS/SSH though, because it
>>cooperates better with rxvt.
> 
> 
> Ah....I think we would probably prefer things not to depend on msys-1.0.dll.
> My ignorance is being exposed here.  If you build under msys, are things
> always linked to the msys dll?  

No.  The purpose of MSYS was to provide tools that MinGW could use to 
configure and make for the MSVCRT.DLL runtime library.  It requires the 
msysDVLPR package to build msys dll dependent applications.

> If so, how do you avoid that?  The problem
> I'm having with cvs seems to be one of headers though.  It's looking for a
> sys/utsname.h that doesn't exist.  I'm thinking that the cvs shipped with
> the msys source is a port so I'll have to figure out what was done and see
> if it can be rolled into the official cvs source tree.
> 

The cvs source that I used was a Cygwin port.  It depends on the 
msys-1.0.dll runtime.  I chose to do that because I didn't have time to 
port it to native MSVCRT.DLL.  The package is named msysDTK because the 
binaries are dependent on the msys-1.0.dll.

Earnie.
-- 
http://www.mingw.org