[jira] [Commented] (LUCENE-3018) Lucene Native Directory implementation need automated build
[ https://issues.apache.org/jira/browse/LUCENE-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13031063#comment-13031063 ] Simon Willnauer commented on LUCENE-3018: - varun, can you update the build.xml with the solaris line. I think we are ready to commit once this is in so I will take over once you upload a new patch. simon Lucene Native Directory implementation need automated build --- Key: LUCENE-3018 URL: https://issues.apache.org/jira/browse/LUCENE-3018 Project: Lucene - Java Issue Type: Wish Components: Build Affects Versions: 4.0 Reporter: Simon Willnauer Assignee: Varun Thacker Priority: Minor Fix For: 4.0 Attachments: LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch, cpptasks-1.0b5.jar, cpptasks-LICENSE-ASL.txt, cpptasks.jar, cpptasks.jar Currently the native directory impl in contrib/misc require manual action to compile the c code (partially) documented in https://svn.apache.org/repos/asf/lucene/dev/trunk/lucene/contrib/misc/src/java/overview.html yet it would be nice if we had an ant task and documentation for all platforms how to compile them and set up the prerequisites. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-3018) Lucene Native Directory implementation need automated build
[ https://issues.apache.org/jira/browse/LUCENE-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13028649#comment-13028649 ] Simon Willnauer commented on LUCENE-3018: - hey varun sorry for the long delay! I have a couple of comments for you: * I think we should default the compiler to whatever ant-conrtib uses as the default so we can remove the -Dcompilername * -Dbuild64 is an option that only works on x86-64 architectures so I think we can remove that too entirely. * we are going to commit the cpptasks jar file into the ant_lib directory so it comes with the checkout meaning you can remove the line in the overview.html file saying that you need to place the jar there. * the overview should say cd lucene/contrib/misc/ instead of cd lucene/dev/trunk/lucene/contrib/misc/ same is true for ... will be located in the lucene/dev/trunk/lucene/build/native/ simon Lucene Native Directory implementation need automated build --- Key: LUCENE-3018 URL: https://issues.apache.org/jira/browse/LUCENE-3018 Project: Lucene - Java Issue Type: Wish Components: Build Affects Versions: 4.0 Reporter: Simon Willnauer Assignee: Varun Thacker Priority: Minor Fix For: 4.0 Attachments: LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch, cpptasks-1.0b5.jar, cpptasks-LICENSE-ASL.txt, cpptasks.jar, cpptasks.jar Currently the native directory impl in contrib/misc require manual action to compile the c code (partially) documented in https://svn.apache.org/repos/asf/lucene/dev/trunk/lucene/contrib/misc/src/java/overview.html yet it would be nice if we had an ant task and documentation for all platforms how to compile them and set up the prerequisites. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-3018) Lucene Native Directory implementation need automated build
[
https://issues.apache.org/jira/browse/LUCENE-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13028689#comment-13028689
]
Michael McCandless commented on LUCENE-3018:
Patch works well for me -- I installed cpptasks-1.0b5.jar under
lucene/contrib/misc/ant_lib, and was then able to simply ant
build-native-unix, which produced the .so under lucene/build/native.
I then added lucene/build/native to my LD_LIBRARY_PATH, and ran:
{noformat}
ant test -lib lucene/build/contrib/misc/lucene-misc-4.0-SNAPSHOT.jar
-Dtests.directory=org.apache.lucene.store.DirectIOLinuxDirectory
{noformat}
at the top of the source tree, ie, it runs all unit tests, forcing the dir impl
to be DirectIOLinuxDirectory. All tests passed!
For grins I tried the first step on OpenSolaris too, and it generated a big
number of compilation errors, which seems strange. EG it could not find jni.h
on this platform. (I expect a few compilation errors because we are using
Linux-only flags, but not that it could not find jni.h)... any ideas?
Lucene Native Directory implementation need automated build
---
Key: LUCENE-3018
URL: https://issues.apache.org/jira/browse/LUCENE-3018
Project: Lucene - Java
Issue Type: Wish
Components: Build
Affects Versions: 4.0
Reporter: Simon Willnauer
Assignee: Varun Thacker
Priority: Minor
Fix For: 4.0
Attachments: LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch,
LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch,
LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch, cpptasks-1.0b5.jar,
cpptasks-LICENSE-ASL.txt, cpptasks.jar, cpptasks.jar
Currently the native directory impl in contrib/misc require manual action to
compile the c code (partially) documented in
https://svn.apache.org/repos/asf/lucene/dev/trunk/lucene/contrib/misc/src/java/overview.html
yet it would be nice if we had an ant task and documentation for all
platforms how to compile them and set up the prerequisites.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-3018) Lucene Native Directory implementation need automated build
[ https://issues.apache.org/jira/browse/LUCENE-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13028738#comment-13028738 ] Michael McCandless commented on LUCENE-3018: OK, if I change the /linux to /solaris (in the build.xml), then on OpenSolaris I get the expected compilation errors (using the wrong IO flags). Can this somehow be done automagically...? Lucene Native Directory implementation need automated build --- Key: LUCENE-3018 URL: https://issues.apache.org/jira/browse/LUCENE-3018 Project: Lucene - Java Issue Type: Wish Components: Build Affects Versions: 4.0 Reporter: Simon Willnauer Assignee: Varun Thacker Priority: Minor Fix For: 4.0 Attachments: LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch, cpptasks-1.0b5.jar, cpptasks-LICENSE-ASL.txt, cpptasks.jar, cpptasks.jar Currently the native directory impl in contrib/misc require manual action to compile the c code (partially) documented in https://svn.apache.org/repos/asf/lucene/dev/trunk/lucene/contrib/misc/src/java/overview.html yet it would be nice if we had an ant task and documentation for all platforms how to compile them and set up the prerequisites. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-3018) Lucene Native Directory implementation need automated build
[
https://issues.apache.org/jira/browse/LUCENE-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13028757#comment-13028757
]
Simon Willnauer commented on LUCENE-3018:
-
bq. OK, if I change the /linux to /solaris (in the build.xml), then on
OpenSolaris I get the expected compilation errors (using the wrong IO flags).
Can this somehow be done automagically...?
kind of quick and dirty but we could simply include
{noformat}
pathelement location=${java.home}/../include/solaris/
{noformat}
so we automatically build on solaris too?
simon
Lucene Native Directory implementation need automated build
---
Key: LUCENE-3018
URL: https://issues.apache.org/jira/browse/LUCENE-3018
Project: Lucene - Java
Issue Type: Wish
Components: Build
Affects Versions: 4.0
Reporter: Simon Willnauer
Assignee: Varun Thacker
Priority: Minor
Fix For: 4.0
Attachments: LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch,
LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch,
LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch, cpptasks-1.0b5.jar,
cpptasks-LICENSE-ASL.txt, cpptasks.jar, cpptasks.jar
Currently the native directory impl in contrib/misc require manual action to
compile the c code (partially) documented in
https://svn.apache.org/repos/asf/lucene/dev/trunk/lucene/contrib/misc/src/java/overview.html
yet it would be nice if we had an ant task and documentation for all
platforms how to compile them and set up the prerequisites.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-3018) Lucene Native Directory implementation need automated build
[ https://issues.apache.org/jira/browse/LUCENE-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13028798#comment-13028798 ] Michael McCandless commented on LUCENE-3018: That sounds good for starters? Just stick /solaris (and others...?) in? Lucene Native Directory implementation need automated build --- Key: LUCENE-3018 URL: https://issues.apache.org/jira/browse/LUCENE-3018 Project: Lucene - Java Issue Type: Wish Components: Build Affects Versions: 4.0 Reporter: Simon Willnauer Assignee: Varun Thacker Priority: Minor Fix For: 4.0 Attachments: LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch, cpptasks-1.0b5.jar, cpptasks-LICENSE-ASL.txt, cpptasks.jar, cpptasks.jar Currently the native directory impl in contrib/misc require manual action to compile the c code (partially) documented in https://svn.apache.org/repos/asf/lucene/dev/trunk/lucene/contrib/misc/src/java/overview.html yet it would be nice if we had an ant task and documentation for all platforms how to compile them and set up the prerequisites. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-3018) Lucene Native Directory implementation need automated build
[
https://issues.apache.org/jira/browse/LUCENE-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13022724#comment-13022724
]
Simon Willnauer commented on LUCENE-3018:
-
bq. In my opinion, the folder name of this utility lib should maybe named
different, because lib/ is used for runtime libs and not compile-time
dependencies. Any comments on this? Simon?
I agree, maybe we should call it ant_lib ?
{quote}We require all libs in Lucene to be named with version number. Of course
the lib should contain it in its manifest, but the name should also contain it.
Cpptasks is a utility lib, so its not so important for this case, but for
consistency, all other libs that will be copied by the user to his classpath
when using Lucene this is important to make sure, that the user can manage the
dependencies if he has conflicting version numbers.
{quote}
Varun, can you change it please?
Lucene Native Directory implementation need automated build
---
Key: LUCENE-3018
URL: https://issues.apache.org/jira/browse/LUCENE-3018
Project: Lucene - Java
Issue Type: Wish
Components: Build
Affects Versions: 4.0
Reporter: Simon Willnauer
Assignee: Varun Thacker
Priority: Minor
Fix For: 4.0
Attachments: LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch,
LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch, cpptasks-1.0b5.jar,
cpptasks-LICENSE-ASL.txt, cpptasks.jar, cpptasks.jar
Currently the native directory impl in contrib/misc require manual action to
compile the c code (partially) documented in
https://svn.apache.org/repos/asf/lucene/dev/trunk/lucene/contrib/misc/src/java/overview.html
yet it would be nice if we had an ant task and documentation for all
platforms how to compile them and set up the prerequisites.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-3018) Lucene Native Directory implementation need automated build
[ https://issues.apache.org/jira/browse/LUCENE-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13022231#comment-13022231 ] Uwe Schindler commented on LUCENE-3018: --- Looks fine, I would only replace the compilerarg value=-fPIC/compilerarg by compilerarg value=-fPIC / (as compilerarg is defined to be empty). Lucene Native Directory implementation need automated build --- Key: LUCENE-3018 URL: https://issues.apache.org/jira/browse/LUCENE-3018 Project: Lucene - Java Issue Type: Wish Components: Build Affects Versions: 4.0 Reporter: Simon Willnauer Assignee: Varun Thacker Priority: Minor Fix For: 4.0 Attachments: LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch, cpptasks-LICENSE-ASL.txt, cpptasks.jar, cpptasks.jar Currently the native directory impl in contrib/misc require manual action to compile the c code (partially) documented in https://svn.apache.org/repos/asf/lucene/dev/trunk/lucene/contrib/misc/src/java/overview.html yet it would be nice if we had an ant task and documentation for all platforms how to compile them and set up the prerequisites. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-3018) Lucene Native Directory implementation need automated build
[ https://issues.apache.org/jira/browse/LUCENE-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13022233#comment-13022233 ] Uwe Schindler commented on LUCENE-3018: --- bq. The version number of cpptasks.jar is located in the cpptasks.jar/META-INF/MANIFEST.MF file. We require all libs in Lucene to be named with version number. Of course the lib should contain it in its manifest, but the name should also contain it. Cpptasks is a utility lib, so its not so important for this case, but for consistency, all other libs that will be copied by the user to his classpath when using Lucene this is important to make sure, that the user can manage the dependencies if he has conflicting version numbers. In my opinion, the folder name of this utility lib should maybe named different, because lib/ is used for runtime libs and not compile-time dependencies. Any comments on this? Simon? Lucene Native Directory implementation need automated build --- Key: LUCENE-3018 URL: https://issues.apache.org/jira/browse/LUCENE-3018 Project: Lucene - Java Issue Type: Wish Components: Build Affects Versions: 4.0 Reporter: Simon Willnauer Assignee: Varun Thacker Priority: Minor Fix For: 4.0 Attachments: LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch, cpptasks-LICENSE-ASL.txt, cpptasks.jar, cpptasks.jar Currently the native directory impl in contrib/misc require manual action to compile the c code (partially) documented in https://svn.apache.org/repos/asf/lucene/dev/trunk/lucene/contrib/misc/src/java/overview.html yet it would be nice if we had an ant task and documentation for all platforms how to compile them and set up the prerequisites. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-3018) Lucene Native Directory implementation need automated build
[ https://issues.apache.org/jira/browse/LUCENE-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13020331#comment-13020331 ] Steven Rowe commented on LUCENE-3018: - bq. I built cpptasks-1.0b5 using jdk-1.5 . I have also attached the LICENSE file by renaming it according to license naming convention. Excellent. Lucene Native Directory implementation need automated build --- Key: LUCENE-3018 URL: https://issues.apache.org/jira/browse/LUCENE-3018 Project: Lucene - Java Issue Type: Wish Components: Build Affects Versions: 4.0 Reporter: Simon Willnauer Assignee: Varun Thacker Priority: Minor Fix For: 4.0 Attachments: LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch, cpptasks-LICENSE-ASL.txt, cpptasks.jar, cpptasks.jar Currently the native directory impl in contrib/misc require manual action to compile the c code (partially) documented in https://svn.apache.org/repos/asf/lucene/dev/trunk/lucene/contrib/misc/src/java/overview.html yet it would be nice if we had an ant task and documentation for all platforms how to compile them and set up the prerequisites. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-3018) Lucene Native Directory implementation need automated build
[
https://issues.apache.org/jira/browse/LUCENE-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13020339#comment-13020339
]
Varun Thacker commented on LUCENE-3018:
---
If we place the cpptasks.jar in the lucene/contrib/misc/lib folder the command
line for running the build.xml would be :
{noformat}
ant -lib lib/cpptasks.jar build-native
{noformat}
Lucene Native Directory implementation need automated build
---
Key: LUCENE-3018
URL: https://issues.apache.org/jira/browse/LUCENE-3018
Project: Lucene - Java
Issue Type: Wish
Components: Build
Affects Versions: 4.0
Reporter: Simon Willnauer
Assignee: Varun Thacker
Priority: Minor
Fix For: 4.0
Attachments: LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch,
cpptasks-LICENSE-ASL.txt, cpptasks.jar, cpptasks.jar
Currently the native directory impl in contrib/misc require manual action to
compile the c code (partially) documented in
https://svn.apache.org/repos/asf/lucene/dev/trunk/lucene/contrib/misc/src/java/overview.html
yet it would be nice if we had an ant task and documentation for all
platforms how to compile them and set up the prerequisites.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-3018) Lucene Native Directory implementation need automated build
[ https://issues.apache.org/jira/browse/LUCENE-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13020351#comment-13020351 ] Uwe Schindler commented on LUCENE-3018: --- In general, you should make it possible to not supply a -lib parameter at all. E.g. look like this is implemented for clover.jar in common-build.xml (which is also a external plugin to ant). The whole thing is to put the classpath into the build.xml before trying to use the plugin. Lucene Native Directory implementation need automated build --- Key: LUCENE-3018 URL: https://issues.apache.org/jira/browse/LUCENE-3018 Project: Lucene - Java Issue Type: Wish Components: Build Affects Versions: 4.0 Reporter: Simon Willnauer Assignee: Varun Thacker Priority: Minor Fix For: 4.0 Attachments: LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch, cpptasks-LICENSE-ASL.txt, cpptasks.jar, cpptasks.jar Currently the native directory impl in contrib/misc require manual action to compile the c code (partially) documented in https://svn.apache.org/repos/asf/lucene/dev/trunk/lucene/contrib/misc/src/java/overview.html yet it would be nice if we had an ant task and documentation for all platforms how to compile them and set up the prerequisites. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-3018) Lucene Native Directory implementation need automated build
[
https://issues.apache.org/jira/browse/LUCENE-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13020354#comment-13020354
]
Uwe Schindler commented on LUCENE-3018:
---
something like that:
{code:xml}
taskdef resource=cpptasks.tasks
classpath
pathelement location=${lib}/cpptasks.jar/
/classpath
/taskdef
{code}
Lucene Native Directory implementation need automated build
---
Key: LUCENE-3018
URL: https://issues.apache.org/jira/browse/LUCENE-3018
Project: Lucene - Java
Issue Type: Wish
Components: Build
Affects Versions: 4.0
Reporter: Simon Willnauer
Assignee: Varun Thacker
Priority: Minor
Fix For: 4.0
Attachments: LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch,
cpptasks-LICENSE-ASL.txt, cpptasks.jar, cpptasks.jar
Currently the native directory impl in contrib/misc require manual action to
compile the c code (partially) documented in
https://svn.apache.org/repos/asf/lucene/dev/trunk/lucene/contrib/misc/src/java/overview.html
yet it would be nice if we had an ant task and documentation for all
platforms how to compile them and set up the prerequisites.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-3018) Lucene Native Directory implementation need automated build
[
https://issues.apache.org/jira/browse/LUCENE-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13019786#comment-13019786
]
Simon Willnauer commented on LUCENE-3018:
-
It seems like that you need to use includepath rather than libset here
something like
{code}
includepath
pathelement location=${java.home}/include/
pathelement location=${java.home}/include/linux/
/includepath
{code}
simon
Lucene Native Directory implementation need automated build
---
Key: LUCENE-3018
URL: https://issues.apache.org/jira/browse/LUCENE-3018
Project: Lucene - Java
Issue Type: Wish
Components: Build
Affects Versions: 4.0
Reporter: Simon Willnauer
Assignee: Varun Thacker
Priority: Minor
Fix For: 4.0
Attachments: LUCENE-3018.patch
Currently the native directory impl in contrib/misc require manual action to
compile the c code (partially) documented in
https://svn.apache.org/repos/asf/lucene/dev/trunk/lucene/contrib/misc/src/java/overview.html
yet it would be nice if we had an ant task and documentation for all
platforms how to compile them and set up the prerequisites.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-3018) Lucene Native Directory implementation need automated build
[
https://issues.apache.org/jira/browse/LUCENE-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13019789#comment-13019789
]
Simon Willnauer commented on LUCENE-3018:
-
regarding you attached patch. you should make sure that you are checking the
{noformat} Grant license to ASF for inclusion in ASF works (as per the Apache
License ยง5) {noformat} checkbox in the attach dialog when you uploading
patches. Can you also provide a quick guide how to install the cpp tasks for
ant and maybe upload the jars you have added to make this task work?
simon
Lucene Native Directory implementation need automated build
---
Key: LUCENE-3018
URL: https://issues.apache.org/jira/browse/LUCENE-3018
Project: Lucene - Java
Issue Type: Wish
Components: Build
Affects Versions: 4.0
Reporter: Simon Willnauer
Assignee: Varun Thacker
Priority: Minor
Fix For: 4.0
Attachments: LUCENE-3018.patch
Currently the native directory impl in contrib/misc require manual action to
compile the c code (partially) documented in
https://svn.apache.org/repos/asf/lucene/dev/trunk/lucene/contrib/misc/src/java/overview.html
yet it would be nice if we had an ant task and documentation for all
platforms how to compile them and set up the prerequisites.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-3018) Lucene Native Directory implementation need automated build
[
https://issues.apache.org/jira/browse/LUCENE-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13019833#comment-13019833
]
Steven Rowe commented on LUCENE-3018:
-
When {{cpptasks.jar}} is committed to the Lucene source tree, it should have a
version number included in its name. E.g., if the jar was built from the 1.0b5
sources, the committed jar should be named {{cpptasks-1.0b5.jar}}.
Varun, where did you get the {{cpptasks.jar}} from? If you build it yourself,
please use a Java 1.5 JDK, to insure it will be compatible with 1.5 JVMs.
Lucene Native Directory implementation need automated build
---
Key: LUCENE-3018
URL: https://issues.apache.org/jira/browse/LUCENE-3018
Project: Lucene - Java
Issue Type: Wish
Components: Build
Affects Versions: 4.0
Reporter: Simon Willnauer
Assignee: Varun Thacker
Priority: Minor
Fix For: 4.0
Attachments: LUCENE-3018.patch, LUCENE-3018.patch, cpptasks.jar
Currently the native directory impl in contrib/misc require manual action to
compile the c code (partially) documented in
https://svn.apache.org/repos/asf/lucene/dev/trunk/lucene/contrib/misc/src/java/overview.html
yet it would be nice if we had an ant task and documentation for all
platforms how to compile them and set up the prerequisites.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-3018) Lucene Native Directory implementation need automated build
[ https://issues.apache.org/jira/browse/LUCENE-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13019839#comment-13019839 ] Varun Thacker commented on LUCENE-3018: --- Sorry for not being clear about it. I should have named it cpptasks-1.0b4.jar. I did not build it myself but used the one provided on the ant-contrib development page. Link to cpptasks-1.0b4 : http://sourceforge.net/projects/ant-contrib/files/ant-contrib/cpptasks-1.0-beta4/ Should I upload the LICENSE file which came with it ? Lucene Native Directory implementation need automated build --- Key: LUCENE-3018 URL: https://issues.apache.org/jira/browse/LUCENE-3018 Project: Lucene - Java Issue Type: Wish Components: Build Affects Versions: 4.0 Reporter: Simon Willnauer Assignee: Varun Thacker Priority: Minor Fix For: 4.0 Attachments: LUCENE-3018.patch, LUCENE-3018.patch, cpptasks.jar Currently the native directory impl in contrib/misc require manual action to compile the c code (partially) documented in https://svn.apache.org/repos/asf/lucene/dev/trunk/lucene/contrib/misc/src/java/overview.html yet it would be nice if we had an ant task and documentation for all platforms how to compile them and set up the prerequisites. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-3018) Lucene Native Directory implementation need automated build
[
https://issues.apache.org/jira/browse/LUCENE-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13019848#comment-13019848
]
Simon Willnauer commented on LUCENE-3018:
-
hey varun,
here are some comments
do we need
{code}
property environment=env/
property name=jni1 location=${env.JAVA_HOME}/include /
property name=jni2 location=${env.JAVA_HOME}/include/linux /
{code}
or can we simply use
{code}
includepath
pathelement location=${java.home}/include/
pathelement location=${java.home}/lnclude/linux/
/includepath
{code}
instead of using
{code}fileset file=src/java/org/apache/lucene/store/NativePosixUtil.cpp /
{code}
we should rather using
{code}fileset file=${src.dir}/org/apache/lucene/store/NativePosixUtil.cpp /
{code}
I wonder if we really want to put the build .so file into
src/java/org/apache/lucene/store/NativePosixUtil (outfile) or if this should
rather be build into ${common.build.dir}
that way it would be cleaned up too something like this:
{code}
mkdir dir=${common.build.dir}/native/
cpptasks:cc outtype=shared subsystem=console
outfile=${common.build.dir}/native/NativePosixUtil
{code}
Do we need to specify gcc as the compiler? afaik its default so we might can
let it choose the default?
I also wonder what happens if the java.home points to a $JAVA_HOME/jre
directory and not to $JAVA_HOME directly in such a case we need to include
${java.home}/../include etc. maybe we need to specify the path based on a
condition?
it would be great if we had a way to test that the native lib works so maybe we
wanna check that too with a small testcase?
simon
Lucene Native Directory implementation need automated build
---
Key: LUCENE-3018
URL: https://issues.apache.org/jira/browse/LUCENE-3018
Project: Lucene - Java
Issue Type: Wish
Components: Build
Affects Versions: 4.0
Reporter: Simon Willnauer
Assignee: Varun Thacker
Priority: Minor
Fix For: 4.0
Attachments: LUCENE-3018.patch, LUCENE-3018.patch, cpptasks.jar
Currently the native directory impl in contrib/misc require manual action to
compile the c code (partially) documented in
https://svn.apache.org/repos/asf/lucene/dev/trunk/lucene/contrib/misc/src/java/overview.html
yet it would be nice if we had an ant task and documentation for all
platforms how to compile them and set up the prerequisites.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-3018) Lucene Native Directory implementation need automated build
[ https://issues.apache.org/jira/browse/LUCENE-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13019863#comment-13019863 ] Simon Willnauer commented on LUCENE-3018: - bq. I will write a small test case to see whether the .so file being built is working fine. awesome! :) Lucene Native Directory implementation need automated build --- Key: LUCENE-3018 URL: https://issues.apache.org/jira/browse/LUCENE-3018 Project: Lucene - Java Issue Type: Wish Components: Build Affects Versions: 4.0 Reporter: Simon Willnauer Assignee: Varun Thacker Priority: Minor Fix For: 4.0 Attachments: LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch, cpptasks.jar Currently the native directory impl in contrib/misc require manual action to compile the c code (partially) documented in https://svn.apache.org/repos/asf/lucene/dev/trunk/lucene/contrib/misc/src/java/overview.html yet it would be nice if we had an ant task and documentation for all platforms how to compile them and set up the prerequisites. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-3018) Lucene Native Directory implementation need automated build
[ https://issues.apache.org/jira/browse/LUCENE-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13019889#comment-13019889 ] Simon Willnauer commented on LUCENE-3018: - one more comment about the cpptasks-1.0b4.jar, I think we should put it into lucene/contrib/misc/lib instead of lucene/lib since we only need it in there though. while we are on that you might need to update the README.TXT and the overview.html accordingly since we now have an ant build for it. Lucene Native Directory implementation need automated build --- Key: LUCENE-3018 URL: https://issues.apache.org/jira/browse/LUCENE-3018 Project: Lucene - Java Issue Type: Wish Components: Build Affects Versions: 4.0 Reporter: Simon Willnauer Assignee: Varun Thacker Priority: Minor Fix For: 4.0 Attachments: LUCENE-3018.patch, LUCENE-3018.patch, LUCENE-3018.patch, cpptasks.jar Currently the native directory impl in contrib/misc require manual action to compile the c code (partially) documented in https://svn.apache.org/repos/asf/lucene/dev/trunk/lucene/contrib/misc/src/java/overview.html yet it would be nice if we had an ant task and documentation for all platforms how to compile them and set up the prerequisites. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-3018) Lucene Native Directory implementation need automated build
[ https://issues.apache.org/jira/browse/LUCENE-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13019326#comment-13019326 ] Simon Willnauer commented on LUCENE-3018: - varun, pastbin links are not ideal for work on issues here. you can post small snippets directly here or upload a patch so we can review. nevertheless, the example you have added to pastebin seems just like a generic example can you try to integrate it into the trunk/lucene/conrib/misk/build.xml file and make it compile the NativePosixUtil.cpp? If you have that you can create a patch with svn diff LUCENE-3018.patch and upload it. if you need 3rd party libs like ant contrib you can upload them here too. simon Lucene Native Directory implementation need automated build --- Key: LUCENE-3018 URL: https://issues.apache.org/jira/browse/LUCENE-3018 Project: Lucene - Java Issue Type: Wish Components: Build Affects Versions: 4.0 Reporter: Simon Willnauer Assignee: Varun Thacker Priority: Minor Fix For: 4.0 Currently the native directory impl in contrib/misc require manual action to compile the c code (partially) documented in https://svn.apache.org/repos/asf/lucene/dev/trunk/lucene/contrib/misc/src/java/overview.html yet it would be nice if we had an ant task and documentation for all platforms how to compile them and set up the prerequisites. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-3018) Lucene Native Directory implementation need automated build
[ https://issues.apache.org/jira/browse/LUCENE-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13019329#comment-13019329 ] Uwe Schindler commented on LUCENE-3018: --- Hi, I suggest to use ANT Contrib for compiling the C Parts. That includes fine in our build infrastructure and supplies ANT tasks for compiling and linking: [http://ant-contrib.sourceforge.net/cpptasks/index.html] I think your example pastebin is using this. We only need to add the JAR in the lib folder of Lucene, so ANT can load the plugin. Lucene Native Directory implementation need automated build --- Key: LUCENE-3018 URL: https://issues.apache.org/jira/browse/LUCENE-3018 Project: Lucene - Java Issue Type: Wish Components: Build Affects Versions: 4.0 Reporter: Simon Willnauer Assignee: Varun Thacker Priority: Minor Fix For: 4.0 Currently the native directory impl in contrib/misc require manual action to compile the c code (partially) documented in https://svn.apache.org/repos/asf/lucene/dev/trunk/lucene/contrib/misc/src/java/overview.html yet it would be nice if we had an ant task and documentation for all platforms how to compile them and set up the prerequisites. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-3018) Lucene Native Directory implementation need automated build
[ https://issues.apache.org/jira/browse/LUCENE-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13019356#comment-13019356 ] Varun Thacker commented on LUCENE-3018: --- I made the mistake of adding the ant-contrib jar and trying to compile it. This requires cpptasks which is not part of ant-contrib Link to the cpptasks jar : http://sourceforge.net/projects/ant-contrib/files/ant-contrib/cpptasks-1.0-beta4/ Adding this jar , I was able to compile the code. Lucene Native Directory implementation need automated build --- Key: LUCENE-3018 URL: https://issues.apache.org/jira/browse/LUCENE-3018 Project: Lucene - Java Issue Type: Wish Components: Build Affects Versions: 4.0 Reporter: Simon Willnauer Assignee: Varun Thacker Priority: Minor Fix For: 4.0 Currently the native directory impl in contrib/misc require manual action to compile the c code (partially) documented in https://svn.apache.org/repos/asf/lucene/dev/trunk/lucene/contrib/misc/src/java/overview.html yet it would be nice if we had an ant task and documentation for all platforms how to compile them and set up the prerequisites. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-3018) Lucene Native Directory implementation need automated build
[ https://issues.apache.org/jira/browse/LUCENE-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13018762#comment-13018762 ] Simon Willnauer commented on LUCENE-3018: - Varun, are you getting along here so far? Lucene Native Directory implementation need automated build --- Key: LUCENE-3018 URL: https://issues.apache.org/jira/browse/LUCENE-3018 Project: Lucene - Java Issue Type: Wish Components: Build Affects Versions: 4.0 Reporter: Simon Willnauer Assignee: Varun Thacker Priority: Minor Fix For: 4.0 Currently the native directory impl in contrib/misc require manual action to compile the c code (partially) documented in https://svn.apache.org/repos/asf/lucene/dev/trunk/lucene/contrib/misc/src/java/overview.html yet it would be nice if we had an ant task and documentation for all platforms how to compile them and set up the prerequisites. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-3018) Lucene Native Directory implementation need automated build
[ https://issues.apache.org/jira/browse/LUCENE-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13018951#comment-13018951 ] Varun Thacker commented on LUCENE-3018: --- This is a small ant task I wrote to build a shared library from a .cpp file. http://pastebin.com/diTXru9w I will update the code to add options for command line parameters which are required to build NativePosixUtil.cpp Lucene Native Directory implementation need automated build --- Key: LUCENE-3018 URL: https://issues.apache.org/jira/browse/LUCENE-3018 Project: Lucene - Java Issue Type: Wish Components: Build Affects Versions: 4.0 Reporter: Simon Willnauer Assignee: Varun Thacker Priority: Minor Fix For: 4.0 Currently the native directory impl in contrib/misc require manual action to compile the c code (partially) documented in https://svn.apache.org/repos/asf/lucene/dev/trunk/lucene/contrib/misc/src/java/overview.html yet it would be nice if we had an ant task and documentation for all platforms how to compile them and set up the prerequisites. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-3018) Lucene Native Directory implementation need automated build
[ https://issues.apache.org/jira/browse/LUCENE-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13018335#comment-13018335 ] Varun Thacker commented on LUCENE-3018: --- I'll take up this task as it would help me understand the community process involved submitting a patch. I can use this experience to patch LUCENE-2793 and LUCENE-2795 over the summer . Lucene Native Directory implementation need automated build --- Key: LUCENE-3018 URL: https://issues.apache.org/jira/browse/LUCENE-3018 Project: Lucene - Java Issue Type: Wish Components: Build Affects Versions: 4.0 Reporter: Simon Willnauer Priority: Minor Fix For: 4.0 Currently the native directory impl in contrib/misc require manual action to compile the c code (partially) documented in https://svn.apache.org/repos/asf/lucene/dev/trunk/lucene/contrib/misc/src/java/overview.html yet it would be nice if we had an ant task and documentation for all platforms how to compile them and set up the prerequisites. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
