Making a portfile from a cmake based project

Manu N audionuma at gmail.com
Sun Feb 28 01:05:23 PST 2016


Thanks all that provided guidance.
I eventually disabled the tests build as they require downloading several
megs of audio files to be run, and check compliance to the r128 standard
rather than correct build of the library.
Portfile submitted as https://trac.macports.org/ticket/50732
audionuma

2016-02-27 21:26 GMT+01:00 Ryan Schmidt <ryandesign at macports.org>:

> On Feb 27, 2016, at 11:13, Mojca Miklavec <mojca at macports.org> wrote:
>
> >> 425cc98f9140885966ce17c1d1
> >> depends_lib        port:speex-devel
> >
> > I was unable to use that because I already had "speex" installed. I
> > removed -devel and it seemed to work.
>
> If both work, a path: dependency should be used to allow either.
>
>
> >> OK.
> >> Added a github.tarball_from releases command as there is a release on
> >> github.
> >
> > I'm not sure when this is needed.
>
> If the project's developers provide a release download, it should be used.
> This project's developers don't, so it cannot be used here.
>
>
> >> variant with_tests description {Build tests suite} {
> >>  configure.args-append -DENABLE_TESTS=ON
> >> }
>
> Variant names should not begin with words like "with" or "without" or "no".
>
> Does building the test suite really need to be a variant? How long does it
> take?
>
>
> > As far as the tests are concerned: MacPorts offers some functionality
> > to run the tests (like "sudo port test libebur128"), but I would have
> > to check how to properly implement that.
>
>
> test.run yes
>
> And change test.target if necessary.
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.macosforge.org/pipermail/macports-dev/attachments/20160228/cd133653/attachment.html>


More information about the macports-dev mailing list