Issue getting application to built

Toby Johnson toby at etjohnson.us
Tue Sep 30 10:23:03 EDT 2008


David Smith wrote:
> Hi Toby,
>
> Toby Johnson wrote:
>   
>> David, maybe I missed something here but why are you building under
>> Cygwin? Both of these programs were developed initially on Windows, with
>> Linux build support added later on. Were you under the impression that
>> they are *nix only?
>>     
>
> Unix only no, because I have used the existing nightly exe files on my
> XP box, but the only reference to building things on the wiki is phrased
> in terms of *nix, in fact it mentions using Cygwin under Windows to get
> the perl modules:
> http://www.pumacode.org/projects/vss2svn/wiki/InstallingVss2Svn

I hadn't really looked at that part of the wiki before, it definitely 
does seem misleading regarding running on Windows.

> I only want to build this to get the patches that Alexander Gavrilov
> submitted in late May 2008. I have never looked at perl before playing
> with vss2svn and my general impression (dangerous things!) was that it
> was a *nix thing. OK, it's a script language that can be used anywhere
> the interpreter is available, but its use in the Windows world is not
> widespread in my experience.
>   
Those patches were to the Perl script portion only, not ssphys.exe. The 
latter was last changed on April 9 
(http://www.pumacode.org/projects/vss2svn/log/trunk/ssphys ) so you can 
just grab the ssphys.exe from the latest nightly instead of building it.

Regarding Perl on Windows, my employer at the time I first wrote this 
script certainly used it a lot, thus my choice of using it... this was 
one of those "quick and dirty" tools that I had no idea would still be 
in use 5 years later :) But the ActiveState Perl build for Windows, and 
accompanying modules, are top quality and certainly not second-class 
citizens, unlike the typical *nix build tools that have been "ported" to 
Windows or Cygwin but often produce more headache than anything.

> OK then, as I said all I want to do is build a version of vss2svn.exe
> containing the patches that Alexander submitted. How would I go about
> that on my XP box? Unless ssphys has had any improvements since April I
> don't particularly *want* to build it.
>
> I have a copy of the vss2svn SVN project on my XP box, I have copies of
> the patches on my XP box, I know how to apply the patches, I even have a
> version of Perl (v5.8.8) available from XP. :)
>
> I would like to build the vss2svn.exe file, but maybe from what you said
> I don't have to. Maybe I just patch the perl files and execute the
> vss2svn.pl with the appropriate arguments? Certainly sounds easier.
>   

Yes, that's correct... vss2svn.exe is really just a self-extracting zip 
file that extracts the script and a compact Perl interpreter into a 
temporary folder and runs it (that's why I put "compile" in quotes), so 
patching and running the script using perl.exe is exactly the same thing.

In fact, if you haven't already done the patching, I would be happy to 
create a branch for you in the project's Subversion repo and give you 
commit access (I would have done so for Mr. Gavrilov in the first place 
but didn't know until afterwards that he was doing so much work on the 
script). If you're interested, send me your preferred username to 
toby at etjohnson.us and I'll create an account.

toby
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.pumacode.org/pipermail/vss2svn-users-lists.pumacode.org/attachments/20080930/19d27a1b/attachment.html


More information about the vss2svn-users mailing list