[MacPorts] #74179: Questions RE install of 'mkvtoolnix' port on macOS Tahoe

MacPorts noreply at macports.org
Thu Jul 2 22:47:24 UTC 2026


#74179: Questions RE install of 'mkvtoolnix' port on macOS Tahoe
---------------------------+---------------------------------
  Reporter:  seamusdemora  |      Owner:  (none)
      Type:  defect        |     Status:  new
  Priority:  Normal        |  Milestone:
 Component:  ports         |    Version:  2.12.5
Resolution:                |   Keywords:  mkvtoolnix, ffmpeg8
      Port:  mkvtoolnix    |
---------------------------+---------------------------------
Description changed by seamusdemora:

Old description:

> I've just gone through the installation of the {{{mkvtoolnix}}} package
> on my Tahoe machine. The current status is that {{{mkvtoolnix}}} has been
> installed, **but none of the "post-install" instructions have been
> executed** at this point - pending answers to my questions.
>
> Also - While I'd prefer to have {{{mkvtoolnix}}} installed on my Mac, I
> can also run it on my Linux box. I say this because of my present
> uncertainty wrt the MacPort installation, and b/c I don't want to wind up
> with a completely broken port system - as I currently have on my Mojave
> Mac! That said, my questions follow:
>
> 1. {{{mkvtoolnix}}} has the {{{+qtgui}}} variant. I was overwhelmed by
> the number of dependencies I'd have to install using the {{{sudo port
> install mkvtoolnix +qtgui}}} command, and so I decided to drop that
> variant from the install. Accordingly, I ran the command: {{{sudo port
> install mkvtoolnix}}}. **Surprisingly, the dependencies were the same
> (AFAICT) with or without the {{{+qtgui}}} option!!**
>
> ''**Q1 - Can someone explain why this is??**''
>

>
> 2.  I've been using {{{ffmpeg ver 7}}} for some time as I like to be
> ''"fairly current"'', but not ''"bleeding edge"''. I am also using
> {{{ffmpeg ver 7}}} in a few shell scripts I've created for processing
> video & audio files. However, installation of {{{mkvtoolnix}}} included
> {{{ffmpeg ver 8}}} as a dependency. I've tested my scripts, and run
> {{{ffmpeg ver 7}}} from the CLI --- it seems that {{{ffmpeg7}}} is "alive
> and well" on my system - so far.
>
> **However:** In the "post install" instructions for {{{mkvtoolnix}}},
> there is this statement that frankly baffles me completely:
>
> {{{
> To compile and link with ffmpeg8, add
> -I/opt/local/libexec/ffmpeg8/include and -L/opt/local/libexec/ffmpeg8/lib
> to your compile command.
> For builds using pkg-config, add /opt/local/libexec/ffmpeg8/lib/pkgconfig
> to $PKG_CONFIG_PATH.
> }}}
>
> ''**Q2.1 - WRT {{{To compile and link with ffmpeg8 ...}}}:**'' AFAICS,
> {{{mkvtoolnix}}} ''**has already been compiled**'', and that being the
> case, **how am I to compile it again**?!?!
>
> ''**Q2.2 - WRT {{{For builds using pkg-config ...}}}:**'' How do I tell
> if I am using {{{pkg-config}}} or not?? The documentation says this re
> {{{pkg-config}}}:
>
> {{{
> Default: ???
> }}}
>
> ''**Q2.3 - Will {{{mkvtoolnix}}} "fall back" to {{{ffmpeg ver 7}}} if
> {{{ffmpeg8}}} is NOT compiled and linked with {{{mkvtoolnix}}}??**''

New description:

 I've just gone through the installation of the {{{mkvtoolnix}}} package on
 my Tahoe machine. The current status is that {{{mkvtoolnix}}} has been
 installed, **but none of the "post-install" instructions have been
 executed** at this point - pending answers to my questions.

 Also - While I'd prefer to have {{{mkvtoolnix}}} installed on my Mac, I
 can also run it on my Linux box. I say this because of my present
 uncertainty wrt the MacPort installation, and b/c I don't want to wind up
 with a completely broken port system - as I currently have on my Mojave
 Mac! That said, my questions follow:

 1. {{{mkvtoolnix}}} has the {{{+qtgui}}} variant. I was overwhelmed by the
 number of dependencies I'd have to install using the {{{sudo port install
 mkvtoolnix +qtgui}}} command, and so I decided to drop that variant from
 the install. Accordingly, I ran the command: {{{sudo port install
 mkvtoolnix}}}. **Surprisingly, the dependencies were the same (AFAICT)
 with or without the {{{+qtgui}}} option!!**

      ''**Q1 - Can someone explain why this is??**''



 2.  I've been using {{{ffmpeg ver 7}}} for some time as I like to be
 ''"fairly current"'', but not ''"bleeding edge"''. I am also using
 {{{ffmpeg ver 7}}} in a few shell scripts I've created for processing
 video & audio files. However, installation of {{{mkvtoolnix}}} included
 {{{ffmpeg ver 8}}} as a dependency. I've tested my scripts, and run
 {{{ffmpeg ver 7}}} from the CLI --- it seems that {{{ffmpeg7}}} is "alive
 and well" on my system - so far.

      **However:** In the "post install" instructions for {{{mkvtoolnix}}},
 there is this statement that frankly baffles me completely:

 {{{
 To compile and link with ffmpeg8, add -I/opt/local/libexec/ffmpeg8/include
 and -L/opt/local/libexec/ffmpeg8/lib to your compile command.
 For builds using pkg-config, add /opt/local/libexec/ffmpeg8/lib/pkgconfig
 to $PKG_CONFIG_PATH.
 }}}

      ''**Q2.1 - WRT {{{To compile and link with ffmpeg8 ...}}}:**''
 AFAICS, {{{mkvtoolnix}}} ''**has already been compiled**'', and that being
 the case, **how am I to compile it again**?!?!

      ''**Q2.2 - WRT {{{For builds using pkg-config ...}}}:**'' How do I
 tell if I am using {{{pkg-config}}} or not?? The documentation says this
 re {{{pkg-config}}}:

 {{{
 Default: ???
 }}}

      ''**Q2.3 - Will {{{mkvtoolnix}}} "fall back" to {{{ffmpeg ver 7}}} if
 {{{ffmpeg8}}} is NOT compiled and linked with {{{mkvtoolnix}}}??**''

--

-- 
Ticket URL: <https://trac.macports.org/ticket/74179#comment:1>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list