[CWB] CWB Windows 7 (64bit) used with cygwin

[Hannah Kermes]

  Hi Andrew,

thanks for trying it out.  I saw you used double backslashes and 
quotation marks in your registry file, instead of single backslashes and 
quotation marks. I tried it out, and it worked this way.

Best Hannah

Am 30.07.2010 01:01, schrieb Hardie, Andrew:
>
> Hi Hannah,
>
> I am afraid that I can't reproduce this error on my system -- the 
> following all works for me within cmd.exe:
>
> C:\CWB>cqp -r registry
>
> [no corpus]> show corpora;
>
> System corpora:
>
>  [correct list of corpora]
>
> C:\>cqp -r C:\CWB\REgistry
>
> [no corpus]> show corpora;
>
> System corpora:
>
>  [correct list of corpora]
>
> C:\Documents and Settings>cqp -r C:\CWB\REgistry
>
> [no corpus]> show corpora;
>
> System corpora:
>
>  [correct list of corpora]
>
> With the following paths in the registry file:
>
> # path to binary data files
>
> HOME "C:\\CWB\\Data\\name-of-corpus"
>
> # optional info file (displayed by "info;" command in CQP)
>
> INFO "C:\\CWB\\Data\\name-of-corpus\\corpus-info.txt"
>
> Even *cqp -r "documents and Settings\..\CWB\Registry"* worked.**
>
> I was working on a clean XP virtual machine, version 3.2.b1. I have 
> not got a Windows 7 install disk yet, but I should have it next week, 
> and when I do I will try it on there to see if it's just a difference 
> in the OS that is causing your trouble.
>
> Andrew.
>
> *From:* cwb-bounces at sslmit.unibo.it 
> [mailto:cwb-bounces at sslmit.unibo.it] *On Behalf Of *Hannah Kermes
> *Sent:* 26 July 2010 12:08
> *To:* cwb at sslmit.unibo.it
> *Subject:* Re: [CWB] CWB Windows 7 (64bit) used with cygwin
>
> Hi Andrew,
> Am 26.07.2010 12:17, schrieb Hardie, Andrew:
>
> Hi Hannah,
>
> It's almost certainly because you are using forward-slash as the 
> directory separator. The Windows build expects backslash as is usual 
> in the Windows world. Likewise it expects a drive-letter root not a 
> bare / root for absolute paths. (If you use cwb-encode to create your 
> registry file, you'll see it creates paths like this; paths may also 
> need to be double quoted in the reg file).
>
> That was what I tried first, but with backslashes with or without 
> drive-letter root it wouldn't work (I am talking about the windows 
> shell now). The only version that works is with forward-slashes and no 
> drive-letter root (i.e., the version I sent to you). That was what 
> suprised me in the beginning, because the windows shell displays the 
> directory with backslashes.
>
> Best
> Hannah
>
> The Windows version can in some cases but not all cope with the 
> forward slash as a separator, as you found, but I think the problems 
> on cygwin may be due to the conflicting expectations of cygwin and the 
> win32 build environment in this regard. But I'm not especially 
> troubled by this; as I said before, the win32 binaries are not 
> expected to work in cygwin, so when they don't, it's not a bug! If you 
> build CWB from source within cygwin, then all the paths you gave below 
> will work exactly as per your expectations.
>
> As for -e mode -- I see the problem now. The command-line editing you 
> get from cmd.exe includes the use of backspace, left-right cursors, 
> and a command history on the up-down cursors. Under *nix, you need the 
> --e option to get these -- and so that's what I was thinking about, 
> rather than the TAB-complete-corpus. Next time I get a chance, I'll 
> take a look at the code to see if there is a way to enable this in the 
> Win32 build. However, I suspect this may be problematic.
>
> best
>
> Andrew.
>
>

-- 
Dr. Hannah Kermes
Dept. of Applied Linguistics, Interpreting and Translation (FR 4.6)
Universität des Saarlandes
Building A2.2, Room 1.07
P.O. Box 15 11 50, D-66041 Saarbrücken
phone: +49-(0)681-302-70076

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://liste.sslmit.unibo.it/pipermail/cwb/attachments/20100730/93d0a876/attachment.htm