#3 windows port ?

[Anonymous]

Hi,

I hate to ask about this, but is there a windows port ( or cygwin which is fine for me) ?

Maybe this could be crosscompiled easly, isnt it ?

Later
--
http://rzr.online.fr/q/SVN

[Igor V. Kovalenko]

Logged In: YES
user_id=56781
Originator: NO

0.6.12 probably builds on windows out the box

[Wolfgang Baron]

Logged In: YES
user_id=822853
Originator: NO

It is partly true, that it builds on Windows cygwin out of the box. I built it using gcc 3.4.4 and had to change only 1 line: line 513 in file src/entries_parser.cpp is missing the __CYGWIN__ symbol and should read:

#if (_WINDOWS || ESVN_WIN || __CYGWIN__)

I cannot confirm how well it is working yet, because I just compiled it and am now going to dig into the documentation to find out how to work with it.

Is any of this getting though to the developers, or should I contact them in any other way?

[Igor V. Kovalenko]

Logged In: YES
user_id=56781
Originator: NO

Windows support is harder bit, because AFAIK noone is actively doing builds
of esvn 0.6.x on windows with MSVC because that requires expensive qt3 license.
I'm not aware of anyone using cygwin with opensource qt3 either.

Your change seems OK, but there are other places ESVN_WIN is used.
You may need to change more places, at least you need the same change
in esvn-diff-wrapper.cpp or it won't be built.

[Wolfgang Baron]

Logged In: YES
user_id=822853
Originator: NO

I am using the opensource qt3 on cygwin and I only had to change that single line. The rest works fine with cygwin. I also do not know about an MSVC port and I don't really care.

The change is only there, because cygwin seems to behave like MSVC when it comes down to timezone stuff. The rest of cygwin is more like Linux or other Un*X derivations.

If anyone could integrate that single line I mentioned, then you would get a cygwin port out-of-the-box!