On Mar 23, 2009, at 3:04 PM, Alexander Wagner wrote:
> If you have xboard compatible engines they usually need some
> config file and most of them require this file sitting in
> the same dir as the engine. Additionally, many require their
> own books and stuff and even generate a bunch of files.
Israel Chauca Fuentes wrote:
Hi!
[...]
> Can we eliminate the engine's parent folders? instead of "engines/
> Phalanx-XXII/phalanx.scid" why dont we use "engines/phalanx-scid" and
> the same for toga. What's the reason behind that setup?
If you have xboard compatible engines they usually need
Hi,
I made some modifications and commited to CVS. Seems to work on Windows
also.
Pascal
--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabiliti
Hi there!
We need some discussion to finish this.
On Feb 22, 2009, at 11:34 AM, Pascal Georges wrote:
> There is no need to keep Crafty, it is no longer needed by any
> feature of
> Scid.
Crafty is out of the equation.
> phalanx-pg is not a correct name. Maybe phalanx-scid ?
> Current name i
On Thu, 2009-02-26 at 19:33 +0100, Alexander Wagner wrote:
> Joost ´t Hart wrote:
>
> Hi!
>
> >> I'm not sure on what your request is, if its about exporting the
> >> COMPILE/LINK variables to the engine's makefiles, I'm not sure how to
> >> handle that. I could give it a try though, but I th
Joost ´t Hart wrote:
Hi!
>> I'm not sure on what your request is, if its about exporting the
>> COMPILE/LINK variables to the engine's makefiles, I'm not sure how to
>> handle that. I could give it a try though, but I think it would be
>> better if someone who already knows how would volunt
On Thu, 2009-02-26 at 04:07 -0600, Israel Chauca Fuentes wrote:
> Hi Joost,
>
> I'm not sure on what your request is, if its about exporting the
> COMPILE/LINK variables to the engine's makefiles, I'm not sure how to
> handle that. I could give it a try though, but I think it would be
> bett
Hi Joost,
I'm not sure on what your request is, if its about exporting the
COMPILE/LINK variables to the engine's makefiles, I'm not sure how to
handle that. I could give it a try though, but I think it would be
better if someone who already knows how would volunteer to fix it.
Israel
On F
Hi Israel,
One request from my side, as you are touching these makefiles anyway.
On my system (ubuntu), the g++ executable is named 'g++-4.3'. This is
something I survive during scids ./configure stage.
Unfortunately, the COMPILE/LINK variables are not exported to the engine
makefiles, so I have
> There is no need to keep Crafty, it is no longer needed by any
> feature of
> Scid.
>
OK
> phalanx-pg is not a correct name. Maybe phalanx-scid ?
> Current name is phalanx, which collides with original phalanx which
> is no
> longer maintained. So indeed there could be both versions install
2009/2/22 Israel Chauca Fuentes
>
>
> > BTW: I'm not sure about crafty. This one was droped out of Scids
> > distribution recently. Probably one should leave it here as well?
>
There is no need to keep Crafty, it is no longer needed by any feature of
Scid.
>
> >> what should be done if no engi
On Feb 22, 2009, at 1:24 AM, Alexander Wagner wrote:
> Israel Chauca Fuentes wrote:
>
> Hi!
>
>> How does this look?
>
> Gererally good :)
>
> I did not check but does our build for Toga not include proper
> renaming of the executable? (Ie. fruit != toga...) This is an old
> bug in Toga's Mak
Israel Chauca Fuentes wrote:
Hi!
> How does this look?
Gererally good :)
I did not check but does our build for Toga not include proper renaming
of the executable? (Ie. fruit != toga...) This is an old bug in Toga's
Makefile, I usually take care of this by some mv in my private setup. I
thin
I think this didn't make it to the list, sorry if you see it twice.
How does this look? should I add some other path? what should be done
if no engines are found?
# Read the user Engine List file now:
#
catch { ::enginelist::read }
if {[llength $engines(list)] == 0} {
# No engines, so set up
How does this look? should I add some other path? what should be done
if no engines are found?
# Read the user Engine List file now:
#
catch { ::enginelist::read }
if {[llength $engines(list)] == 0} {
# No engines, so set up a default engine list:
set scidlet "scidlet"
set crafty "craft
Mikhail Kalenkov wrote:
Hi!
> 2009/2/20 Pascal Georges :
>> This is indeed useful and necessary but I see several cases to handle :
>>
>> - Windows installation
>> - Linux installation -> engines are in shared dir
>> - Linux from sources -> engines are relative to Scid's exe
> I keep engines in t
2009/2/20 Pascal Georges :
> This is indeed useful and necessary but I see several cases to handle :
>
> - Windows installation
> - Linux installation -> engines are in shared dir
> - Linux from sources -> engines are relative to Scid's exe
I keep engines in the same directory with Scid ( /usr/bin
This is indeed useful and necessary but I see several cases to handle :
- Windows installation
- Linux installation -> engines are in shared dir
- Linux from sources -> engines are relative to Scid's exe
- Mac Os installation
- Mac Os from sources
So given that the engines (at least on Linux) can
18 matches
Mail list logo
