On 01/16/2011 08:49 AM, Steven wrote:
> Joost wrote
>
>> I might (or might not) be looking for an
>> alternate strategy to produce an english-only executable.
> Doesn't this suffice ?
>
> ./configure LANGUAGES=""
>
> Or perhaps you mean something else.
Wanted to build "escid" and scid in a go, by
Joost wrote
> I might (or might not) be looking for an
> alternate strategy to produce an english-only executable.
Doesn't this suffice ?
./configure LANGUAGES=""
Or perhaps you mean something else.
Steve
To cut things short, I did revert to the existing order of files.
Not a dramatic change, just putting the non-english language files back
at their position. I might (or might not) be looking for an alternate
strategy to produce an english-only executable.
Cheers,
Joost.
On 01/15/2011 05:02 PM
On 01/15/2011 04:07 PM, Joost 't Hart wrote:
Hi!
>> Could you please recheck with clean current cvs? I can not see this
[...]
> Hm, I am on current CVS + the new build environment.
>
> I checked with pure CVS and you are right...
;)
> The only thing I can imagine is that I (apparently) messed
On 01/15/2011 03:41 PM, Alexander Wagner wrote:
> On 01/15/2011 03:06 PM, Joost 't Hart wrote:
>
> Hi!
>
>> [CVS/Linux+Windows]
>>
>> 1) Start scid
>> 2) Select Options/Language/Nederlands
>> 3) Ensure options are saved
>> 4) Quit scid
>> 5) Start scid
>>
>> On Linux following is dumped into the co
On 01/15/2011 03:06 PM, Joost 't Hart wrote:
Hi!
> [CVS/Linux+Windows]
>
> 1) Start scid
> 2) Select Options/Language/Nederlands
> 3) Ensure options are saved
> 4) Quit scid
> 5) Start scid
>
> On Linux following is dumped into the console:
>
> Error: invalid command name "setLanguage_N"
> Error
Hi,
[CVS/Linux+Windows]
1) Start scid
2) Select Options/Language/Nederlands
3) Ensure options are saved
4) Quit scid
5) Start scid
On Linux following is dumped into the console:
Error: invalid command name "setLanguage_N"
Error in startup script: can't read "langEncoding(N)": no such element
i
