On 28 April 2015 at 15:54, Dirk Hohndel d...@hohndel.org wrote:
On Tue, Apr 28, 2015 at 02:16:32PM +0300, Lubomir I. Ivanov wrote:
On 28 April 2015 at 11:55, Lubomir I. Ivanov neolit...@gmail.com wrote:
On 28 April 2015 at 08:39, Dirk Hohndel d...@hohndel.org wrote:
So this problem
On 28 April 2015 at 11:55, Lubomir I. Ivanov neolit...@gmail.com wrote:
On 28 April 2015 at 08:39, Dirk Hohndel d...@hohndel.org wrote:
So this problem apparently still isn't fixed. How frustrating.
The current 4.4.1 Windows binaries are build with libzip version
42199fe38a16 which should
On Tue, Apr 28, 2015 at 02:16:32PM +0300, Lubomir I. Ivanov wrote:
On 28 April 2015 at 11:55, Lubomir I. Ivanov neolit...@gmail.com wrote:
On 28 April 2015 at 08:39, Dirk Hohndel d...@hohndel.org wrote:
So this problem apparently still isn't fixed. How frustrating.
The current 4.4.1 Windows
On 28 April 2015 at 16:00, Robert Helling hell...@atdotde.de wrote:
Hi,
On 28.04.2015, at 14:54, Dirk Hohndel d...@hohndel.org wrote:
Path handling
on Windows makes no sense to me :-(
totally ignorant suggestion (by somebody who has no idea about windows
paths): Could we use a relative
On Tue, Apr 28, 2015 at 04:13:32PM +0300, Lubomir I. Ivanov wrote:
Which version of libzip are you using in your tests?
As usual, my understanding of all this is somewhat limited. Path handling
on Windows makes no sense to me :-(
I built a Subsurface binary with version 42199fe38a16
On 28 April 2015 at 08:39, Dirk Hohndel d...@hohndel.org wrote:
So this problem apparently still isn't fixed. How frustrating.
The current 4.4.1 Windows binaries are build with libzip version
42199fe38a16 which should contain all the necessary fixes, yet exporting
to divelogs.de still fails
On Tue, Apr 28, 2015 at 2:30 PM, Dirk Hohndel d...@hohndel.org wrote:
Oh joy. Guess what, libzip has two different ways to build it (sound
familiar, anyone)? And if you use autoconf then the Win32 specific path
handling routines aren't even built. And of course I built all this with
Oh joy. Guess what, libzip has two different ways to build it (sound
familiar, anyone)? And if you use autoconf then the Win32 specific path
handling routines aren't even built. And of course I built all this with
configure...
But if you use CMake then it compiles different source files. Oh, and
On 28 April 2015 at 20:30, Dirk Hohndel d...@hohndel.org wrote:
Oh joy. Guess what, libzip has two different ways to build it (sound
familiar, anyone)? And if you use autoconf then the Win32 specific path
handling routines aren't even built. And of course I built all this with
configure...
So this problem apparently still isn't fixed. How frustrating.
The current 4.4.1 Windows binaries are build with libzip version
42199fe38a16 which should contain all the necessary fixes, yet exporting
to divelogs.de still fails without any error.
I have now created a new Windows VM where I was
10 matches
Mail list logo