On 2015-09-08 13:00, Stefan Hett wrote:
> On 9/7/2015 10:21 PM, Win32Svn wrote:
>> On 2015-09-07 18:59, Barry Scott wrote:
>>>> On 7 Sep 2015, at 11:43, Andreas Stieger <andreas.stieger_at_gmx.de>
>>>> wrote:
>>>>
>>>> Hi,
>>>>
>>>> Barry Scott wrote:
>>>>> I see that the recent 1.7 and 1.8 win32svn builds being announced,
>>>>> thanks for
>>>>> them.
>>>>>
>>>>> Do you know when the svn 1.9 win32svn build might be available?
>>>> Available at other binary "vendors":
>>>> https://subversion.apache.org/packages.html#windows
>>> Sadly only win32svn packages the include files that are needed to write
>>> code against svn. In my case I use win32svn as the basis of the pysvn
>>> win32 build.
>>>
>>> Barry
>>>
>>
>> Hi Barry!
>>
>> I'm sorry to say there won't be any 1.9.x build of Win32SVN.
>> You can read about it on http://alagazam.net (click the 1.9.x info
>> link on the right)
>>
>> Regards,
>> David Darj a.k.a. Alagazam
>> Maintainer of Win32SVN
>> http://alagazam.net
>>
>> ps.
>> If you like my work, please support this project by donating at
>> http://sourceforge.net/donate/index.php?group_id=357628
>>
>
> Hi David,
>
> I'm wondering which particular VS6 issue you are referring to in that
> note.
> I've been told the only known issues atm not working using VS6 would
> be in the javahl code (due to the template code) which I assume is not
> the issue you are talking about, or is it?
>
Hi Stefan
I don't remember exactly now, but I gave one of the 1.9.0-alpha a shot
with my build scripts (you can find them on sourceforge).
There were a lot more compilation errors than in 1.8.x where I've
already patched a lot, and the time to look deeper then didn't exist.
Maybe there isn't any specific windows api issues or other features, but
the old C standard (MS-standard) in VC6 makes the burden, right now at
least, to much.
Regards,
David Darj a.k.a. Alagazam
Maintainer of Win32SVN
Received on 2015-09-08 18:57:03 CEST