1. For starters, 32 bit support is deprecated in the next version of Mac
OS X. Other things like Hardened Runtime (
https://lapcatsoftware.com/articles/hardened-runtime-sandboxing.html) may
not be relevant, but to make things compatible, apps need to be compiled
with an SDK > 10.7. The 64 bit is the big thing.
2 & 3. I want static and can't figure out how to get it to compile. Why
static? I want to be able to distribute it to other users without having to
install anything else.
4. I forget where I got the specific opusenc and opusdec that I have been
using, but I do see older binaries linked right from the opus page:
https://archive.mozilla.org/pub/opus/macos/opus-tools-0.1.9-macos.tar.gz
So I'm just looking to statically compile the current version of opus tools
for OS X. I'll check out your page at https://github.com/janstary/ports/
Thanks,
Scott
On Tue, May 20, 2019 at 17:21:25 +0200 Jan Stary <hans at stare.cz>
wrote:
> Hi,
>
> On May 20 11:04:02, scottcbrown at gmail.com wrote:
> > I've been using the command line opusenc/opusdec tools for a while
now to
> > encode/decode files. The next version of OS X changes a few things,
>
> can you be specific?
>
> > so I was looking to recompile these tools
> > using a version of the OS X SDK > 10.7
> > (needed for apple's "hardened runtime") but had no luck.
>
> What errors are you running into?
>
> > How can I compile a static version of opus tools on OS X that
doesn't
> > depend on any other files,
>
> Why do you need them to be static?
>
> > like the older opusenc and opusdec OS X binaries
> > floating around?
>
> Which ones do you mean?
>
>
> I am bulding my *opus* using https://github.com/janstary/ports/
> but that build the normal dynamically linked version
>
> Jan
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.xiph.org/pipermail/opus/attachments/20190521/8600b235/attachment.html>
