Messaggio originale
Da: cristi...@gmail.com
Data: 30/05/2013 22.37
A: "Mike Curtis",
Ogg: Re: [Scid-users] build scid on Windows
It's not that big of a problem as I thought. I just reproduced it on Linux too.
It's enough to have spaces in path for scid to trigger the bug.
Th
For reference: scid.exe that was built in a path with spaces will work if
spaces are removed from the path - but only started from cmd. Double
clicking on scid.exe will still not work.
Cristian
--
Introducing AppDynamics L
It's not that big of a problem as I thought. I just reproduced it on Linux
too. It's enough to have spaces in path for scid to trigger the bug.
I've identified the problem in InitImg procedure in this loop:
foreach {piecetype} [split [glob -directory $dname *] " "] {
puts "piecetype $
Only the folders are created (config, log and data) but they are empty. I
tried wit an options.dat from 4.4 but nothing changed.
Cristian
On Thu, May 30, 2013 at 2:23 PM, Mike Curtis wrote:
> What happens if you rename options.dat to options.BAK and try again?
>
> On Thu, May 30, 2013 at 5:57 A
I want to check why it wants a _25.gif file. This is just a suffix to some
of the piece files that are one level deeper than /img/pieces. Something is
not right.
Anyway, config dir being present or not does not change the result and the
img/pieces has the image dirs.
Cristian
On Thu, May 30,
Cristian Stoica wrote:
> Hi Fulvio,
>
> I don't know what I did, but for a brief period of time I could run
> the build without any problems. After reboot the problem came back.
> Here is the trace. If I put a _25.gif file there, it complains about a
> missing _30.gif.
>
Delete the Release/confi
