On Tue, 23 Mar 2010, Bill Janssen wrote:
Andi Vajda <va...@apache.org> wrote:
Here's what the result of p2w is:
$ p2w /x/pylucene/trunk/build/test
x:/pylucene/trunk/build/test
$
That's a valid Windows path, but I get the same error:
$ make test
mkdir -p `p2w /x/pylucene/trunk/build/test`
PYTHONPATH=`p2w /x/pylucene/trunk/build/test` /c/Python26/python.exe -m
jcc.__main__ --shared --compiler mingw32 --find-jvm-dll --jar
lucene-java-3.0.1/build/lucene-core-3.0.1.jar --jar
lucene-java-3.0.1/build/contrib/snowball/lucene-snowball-3.0.1.jar --jar
lucene-java-3.0.1/build/contrib/analyzers/common/lucene-analyzers-3.0.1.jar
--jar lucene-java-3.0.1/build/contrib/regex/lucene-regex-3.0.1.jar --jar
lucene-java-3.0.1/build/contrib/memory/lucene-memory-3.0.1.jar --jar
lucene-java-3.0.1/build/contrib/highlighter/lucene-highlighter-3.0.1.jar --jar
lucene-java-3.0.1/build/contrib/queries/lucene-queries-3.0.1.jar --jar
build/jar/extensions.jar --package java.lang java.lang.System java.lang.Runtime
--package java.util java.util.Arrays java.text.SimpleDateFormat
java.text.DecimalFormat java.text.Collator --package java.io
java.io.StringReader java.io.InputStreamReader java.io.FileInputStream
--exclude org.apache.lucene.queryParser.Token --exclude
org.apache.lucene.queryPa
rs
e!
r.T
okenMgrError --exclude org.apache.lucene.queryParser.QueryParserTokenManager
--exclude org.apache.lucene.queryParser.ParseException --exclude
org.apache.lucene.search.regex.JakartaRegexpCapabilities --exclude
org.apache.regexp.RegexpTunnel --python lucene --mapping
org.apache.lucene.document.Document
'get:(Ljava/lang/String;)Ljava/lang/String;' --mapping java.util.Properties
'getProperty:(Ljava/lang/String;)Ljava/lang/String;' --rename
org.apache.lucene.search.highlight.SpanScorer=HighlighterSpanScorer --version
3.0.1 --module python/collections.py --files 3 --install --install-dir `p2w
/x/pylucene/trunk/build/test`
running build_ext
running install
Checking .pth file support in x:pylucene\trunk\build\test\
That's not the path you'd expect, though, it's missing its leading \.
Why that is, I don't know. I don't have msys either.
Got to be some code in jcc that's doing this, as I'm passing a valid
Windows path. Over to you.
Err, it works for me on cygwin just fine.
Yes, I'm assuming that cygpath produces paths of the form C:\\foo\\bar,
while p2w produces c:/foo/bar (also a valid path), which is why you
didn't see this bug before.
I can't reproduce this.
Did you try putting the path in explicitly, in the c:/foo/bar form?
Ah ha, the c:/foo/bar form doesn't work. But the c:\\foo\\bar form does.
I checked that I'm passing it unadultered to setup()'s script_args
parameter. Strictly speaking, windows wants \\. Feed it what it wants.
Andi..
