It works if you provide a differently named build directory passed by commandline arguments:
--output target then generated source code is packed into the sdist. Now I'am trying to include the jars as resources (which are only required at runtime, because the wrapper c++ code already has been generated). Tried to achieve this via --resource parameters. But my jars are not included. I guess its a bug/feature of distutils not to include stuff named after a hidden scheme... :-) Am 04.11.2013 16:09, schrieb Andi Vajda (JIRA): > > [ > https://issues.apache.org/jira/browse/PYLUCENE-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13812887#comment-13812887 > ] > > Andi Vajda commented on PYLUCENE-27: > ------------------------------------ > > By "source code", did you mean the C++ code produced by JCC ? > You said on the list that moving this source code into a non-"build" > directory solves the problem. > Did you try this ? Do you have a patch that fixes this problem ? > Creating source distributions from JCC output is an interesting use case that > would be nice to support. But if JCC is then out of the picture to compile > this source distribution, how does distutils/setuptools know where the JVM is > ? (and all the necessary include and link flags) How does it know where > libjcc is ? (if shared mode is desired) > It might still be 'simpler' to just use JCC to do the build from .java files, > then no ? > > >> JCC should be able to create sdist archives >> ------------------------------------------- >> >> Key: PYLUCENE-27 >> URL: https://issues.apache.org/jira/browse/PYLUCENE-27 >> Project: PyLucene >> Issue Type: Wish >> Environment: jcc-svn-head >> Reporter: Martin Scherer >> >> I was not able to create a complete (in terms one is able to compile and >> install the desired wrapper) source distribution. >> I've tried following calls: >> python -m jcc --jar foo --egg-info --extra-setup-arg sdist >> and >> python -m jcc --jar foo --extra-setup-arg sdist >> Both create archives only containing the egg-info and setup.py but no source >> code at all. >> I really need this feature for my testing environment with tox, since this >> heavily depends on the sdist feature. >> thanks, >> best, >> Martin > > > > -- > This message was sent by Atlassian JIRA > (v6.1#6144) >
