RE: Rsyncrypto using wrong gzip ?

[Jan A. <jan...@do...>]

Oke, that is a clear answer, thanks for that.

One last question on this subject. Are you going to try to build a
statically compiled package in one of the next versions ? Or are you leaving
it like it is now ?


-----Oorspronkelijk bericht-----
Van: Shachar Shemesh [mailto:sh...@sh...] 
Verzonden: vrijdag 16 mei 2008 23:01
Aan: Jan Alphenaar
CC: 'L-rsyncrypto'
Onderwerp: Re: Rsyncrypto using wrong gzip ?

Jan Alphenaar wrote:
> Maybe that is one disadvantage of using the MSI system.
>
>   
Actually, you've got it backwards.

I have started to compile rsyncrypto using Visual Studio 9 (2008). I 
figured that upgrading the compiler once a decade is a reasonable 
request. Unfortunately, this resulted in hard dependencies on the MS 
runtime environment (MSVCR9.DLL). This is a DLL which is impossible to 
install by merely copying the file. You absolutely have to go through 
MS's annoying installer in order to get it on your system and get your 
system working. The only sane way I found of doing that is to create an 
MSI for the entire rsyncrypto installation.

So the MSI does three things:
- Copy a bunch of files, DLLs and EXEs into your chosen install 
directory. You can just copy them elsewhere, if you like.
- Copy the openssl DLLs and executable into the "legacy" location - 
usually c:\windows\system32. You will need two DLLs from there if you 
want to copy them by hand.
- Install MSVCR9. I have no clue how you can install it manually, and 
neither does Google. This is a black magic DLL which is impossible to 
manipulate by hand.

I would have gladly linked it statically in order to prevent this 
problem, however it seems that I cannot pass "stderr" between rsyncrypto 
and argtable unless they are both linking dynamically with the same run 
time environment. This is the reason that the build environment now 
compiles argtable2 as part of the rsyncrypto project - to make sure they 
are compiled with compatible options.

Thanks for debugging this.

Shachar