You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Florian Schulze <fl...@gmx.net> on 2003/06/27 15:04:21 UTC
cvs2svn.py and Python bindings on Windows
Hi!
I was today able to compile the Python bindings for Windows with a small
problem. The generated C files from SWIG have (long long) in them when
there should be (__int64). I use SWIG 1.3.17. After I fixed that manually
the bindings compiled without problems. I don't know if they work flawless,
because I only tried cvs2svn.py yet, see below.
cvs2svn.py is another problem. I had to add binary to some (4 or so) file
open calls, so the CVS repository is parsed correctly. The popen call has
the buffersize set to something like 108..., which doesn't work on Windows,
which wants -1 or nothing (not specified) for the buffersize. After these
changes the SVN repository was filled, but there was no path seperation
done. The files had names like "\path\Makefile" which can't be checked out.
Regards,
Florian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: cvs2svn.py and Python bindings on Windows
Posted by kf...@collab.net.
"Russell Yanofsky" <re...@columbia.edu> writes:
> kfogel@collab.net wrote:
> > Also, I'm not sure exactly what you mean by:
> >
> > ...but there was no path seperation done. The files had names
> > like "\path\Makefile" which can't be checked out.
>
> The patch for cvs2svn that I posted two weeks ago fixes this issue.
>
> http://subversion.tigris.org/servlets/ReadMsg?list=dev&msgNo=39020
Ah, and it's also
http://subversion.tigris.org/issues/show_bug.cgi?id=1360
Thanks for the reminder, Russ.
-K
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: cvs2svn.py and Python bindings on Windows
Posted by Russell Yanofsky <re...@columbia.edu>.
kfogel@collab.net wrote:
> Also, I'm not sure exactly what you mean by:
>
> ...but there was no path seperation done. The files had names
> like "\path\Makefile" which can't be checked out.
>
The patch for cvs2svn that I posted two weeks ago fixes this issue.
http://subversion.tigris.org/servlets/ReadMsg?list=dev&msgNo=39020
- Russ
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: cvs2svn.py and Python bindings on Windows
Posted by Florian Schulze <fl...@gmx.net>.
On 27 Jun 2003 10:27:38 -0500, <kf...@collab.net> wrote:
> Maybe you're not aware that cvs2svn.py no longer uses the SWIG/Python
> bindings? It just depends on the 'svnadmin' binary being available.
>
> If your cvs2svn.py requires the bindings, then it is *very* old and
> you should update.
I wasn't aware and I used todays revision 6362.
> Can you post the patch you made? (If you have time to write a log
> message for it, that's great, but it's fine to just post the change if
> not.)
Only four lines yet, there might be more. It's attached. The popen call
should be wrapped somehow I think. I also don't know if it needs the binary
read as well.
> Also, I'm not sure exactly what you mean by:
>
> ...but there was no path seperation done. The files had names
> like "\path\Makefile" which can't be checked out.
>
> Could you describe precisely what happened?
Already explained in a followup.
Regards,
Florian
Re: cvs2svn.py and Python bindings on Windows
Posted by kf...@collab.net.
Florian Schulze <fl...@gmx.net> writes:
> I was today able to compile the Python bindings for Windows with a
> small problem. The generated C files from SWIG have (long long) in
> them when there should be (__int64). I use SWIG 1.3.17. After I fixed
> that manually the bindings compiled without problems. I don't know if
> they work flawless, because I only tried cvs2svn.py yet, see below.
Maybe you're not aware that cvs2svn.py no longer uses the SWIG/Python
bindings? It just depends on the 'svnadmin' binary being available.
If your cvs2svn.py requires the bindings, then it is *very* old and
you should update.
> cvs2svn.py is another problem. I had to add binary to some (4 or so)
> file open calls, so the CVS repository is parsed correctly. The popen
> call has the buffersize set to something like 108..., which doesn't
> work on Windows, which wants -1 or nothing (not specified) for the
> buffersize. After these changes the SVN repository was filled, but
> there was no path seperation done. The files had names like
> "\path\Makefile" which can't be checked out.
Can you post the patch you made? (If you have time to write a log
message for it, that's great, but it's fine to just post the change if
not.)
Also, I'm not sure exactly what you mean by:
...but there was no path seperation done. The files had names
like "\path\Makefile" which can't be checked out.
Could you describe precisely what happened?
Thanks,
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: cvs2svn.py and Python bindings on Windows
Posted by Russell Yanofsky <re...@columbia.edu>.
Florian Schulze wrote:
> Hi!
>
> I was today able to compile the Python bindings for Windows with a
> small problem. The generated C files from SWIG have (long long) in
> them when there should be (__int64). I use SWIG 1.3.17. After I fixed
> that manually the bindings compiled without problems. I don't know if
> they work flawless, because I only tried cvs2svn.py yet, see below.
My generated files don't contain long long, but I'm using SWIG 1.3.19. Maybe you
need to use a newer version of swig.
- Russ
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org