If the wxwindows USE flag is set, the mkvtoolnix ebuild explicitly requires wxGTK-2.6*. However, if wxGTK-2.4* is not installed, the mmg GUI will automatically be excluded by ./configure, no matter the USE flags, and mmg will NOT be built.
Can you test the new version (1.7.0) and see if it still an issue?
(In reply to comment #1) > Can you test the new version (1.7.0) and see if it still an issue? > i have upgraded to 1.7.0 today and this version is built without gui too. wxwindows use flag is enabled and installed wxgtk is version 2.6.2-r1.
Can someone on wxWindows team take a look at this? If 2.4 and 2.6 are both installed, the config script will use 2.4. Fixing it is beyond my ebuildage.
Created attachment 101838 [details, diff] Change dependency to wxGTK-2.4* This patch made it work with me
The problem has nothing to do with wx version. The problem is with the fact that wx-config symlinks point at wx-config-2.4 on systems that have both installed, and the package using the wx-config symlink instead of wx-config-2.6, because mkvtoolnix build system isn't using the official AM_PATH_WXCONFIG aclocal macro provided by wxwin.m4 which would make the environment flags used to make it use the wx-config-2.6 symlink in wxwindows.eclass be honored. One possible workaround is to uninstall wxGTK-2.4 and re-emerge wxGTK-2.6 after that - the re-emerge essentially just makes wx-config symlink and makes it point at wx-config-2.6 (so this could be done manually instead to save time).
mkvtoolnix 1.8.1 which went stable this week now has a configure option to tell wx-config path : use wxwindows && myconf="--with-wx-config=${WX_CONFIG}" so I suppose this one is fixed.
