[MacPorts] #38401: new port: py-khmer
MacPorts
noreply at macports.org
Sat Mar 16 16:51:37 PDT 2013
#38401: new port: py-khmer
-------------------------+--------------------------------
Reporter: sean@… | Owner: macports-tickets@…
Type: submission | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.1.3
Resolution: | Keywords:
Port: py-khmer |
-------------------------+--------------------------------
Comment (by sean@…):
It does build both, but there is no install target for make. Unless I
misunderstand something, I don't see how this would stage any files into
destroot, which is why I went the python route instead.
Replying to [comment:4 larryv@…]:
> Replying to [comment:3 sean@…]:
> > I'm attempting to address this in the revision -- it's a Python
> > project with some C libraries (outside the Python directory) that need
> > to be built first. Looking at just running 'make' in the lib/ dir
> > before the Python module is built. Ideally the Python build would
> > take care of everything, but it doesn't.
>
> This is the top-level makefile:
> {{{
> all: lib_files python_files
>
> clean:
> cd lib && make clean
> cd python && rm -fr build khmer/*.so
>
> doc: FORCE
> cd doc && make html
>
> lib_files:
> cd lib && make
>
> python_files:
> cd python && python setup.py build_ext -i
>
> test: all
> nosetests
>
> FORCE:
> }}}
> It looks like running `make all` from the top-level directory (i.e., the
default MacPorts build behavior) should take care of both the C and Python
bits. Does it not?
--
Ticket URL: <https://trac.macports.org/ticket/38401#comment:5>
MacPorts <http://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list