"Smith, Eric V." <ericsmith@windsor.com> writes:
> > I've been using subversion client (0.15) in combination with
> > cygwin with no
> > problems at all. Windows accepts forward slashed in filenames
> > just as well
> > as backslashes (it's cmd.exe which gets confused about it),
> > so as long as
> > you use relative path-names and avoid cygwin symlinks you
> > have no problems.
>
> I think the problem the original poster was talking about was having svn
> understand the cygwin "paths", created with "mount". For example, on my
> box doing an "ls /tmp" shows the contents of c:/opt/cygwin/tmp, because
> c:/opt/cygwin is mounted as /. It would be nice if svn were buildable
> as a cygwin app, so it could also understand cygwin's mount table.
After building libtool and autoconf from source, I've had no problem
building svn on cygwin. I used to do regularly about 6 months ago,
though I haven't tried in a while.
The only hitch was that subversion's 'make install' target was trying
to copy binaries named 'svn' and 'svnadmin' to /usr/local/bin, when in
fact the compiler had produced 'svn.exe' and 'svnadmin.exe'. But the
libsvn_*.so's installed fine, so all I had to do was hand-copy the
binaries.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jan 9 17:10:46 2003