<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, May 13, 2020 at 9:30 PM John Hoyt <<a href="mailto:john.hoyt@gmail.com">john.hoyt@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Craig I know I’m naive but QT do say<br>
<br>
<quote><br>
<br>
Target Platform Architecture Build Environment<br>
macOS 10.13, 10.14, 10.15 x86_64 and x86_64h Xcode 11 (10.15 SDK)<br>
<br>
Build Environment<br>
<br>
The build environment on macOS is defined entirely by the Xcode version used to build your application. Xcode contains <br>
both a toolchain (compiler, linker, and other tools), and a macOS platform-SDK (headers and libraries). Together these<br>
define how your application is built.<br>
<br>
Note: The version of macOS that you are running Xcode on does not matter. As long as Apple ships a given Xcode version<br>
that runs on your operating system, the build environment will be defined by that Xcode version.<br>
</quote><br>
<br>
ahh I see apple’s fine print<br>
<quote><br>
Xcode 11 requires a Mac running macOS Mojave 10.14.4 or later.<br>
</quote><br>
<br>
James</blockquote><div><br></div><div>That's a bummer, Catalina shipped with Xcode 11 and I don't believe it's compatible with Xcode 10.</div><div><br></div><div>....you could always go the VM route if you can get your hands on a Mojave install. </div></div></div></blockquote><div><br></div><div>Looking over your config file again this AM, one besides the Qt version being slightly different, another thing that jumps out is your libCEC doesn't seem to be found by configure</div></div><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div class="gmail_quote">
<div><span style="font-variant-ligatures:no-common-ligatures;background-color:rgba(0,0,0,0.85);color:rgb(242,242,242);font-family:Monaco;font-size:10px">libCEC device support </span><span class="gmail-Apple-converted-space" style="font-variant-ligatures:no-common-ligatures;background-color:rgba(0,0,0,0.85);color:rgb(242,242,242);font-family:Monaco;font-size:10px"> </span><span style="font-variant-ligatures:no-common-ligatures;background-color:rgba(0,0,0,0.85);color:rgb(242,242,242);font-family:Monaco;font-size:10px">no [/usr/include]</span></div></div></blockquote>This makes me think that maybe you don't have the macports paths on set in your .profile/.zprofile.<div><br></div><div>I have the following lines in both my .profile and .zprofile. Macports should have done this automagically, but if you have another line trumping it...</div><div>
<p class="gmail-p1" style="margin:0px;font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;font-size:10px;line-height:normal;font-family:Monaco;color:rgb(242,242,242);background-color:rgba(0,0,0,0.85)"><span class="gmail-s1" style="font-variant-ligatures:no-common-ligatures"># MacPorts Installer addition on 2020-04-08_at_17:10:32: adding an appropriate PATH variable for use with MacPorts.</span></p></div><div>
<p class="gmail-p1" style="margin:0px;font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;font-size:10px;line-height:normal;font-family:Monaco;color:rgb(242,242,242);background-color:rgba(0,0,0,0.85)"><span class="gmail-s1" style="font-variant-ligatures:no-common-ligatures">export PATH=/opt/local/bin:/opt/local/sbin:$PATH</span></p>
<p class="gmail-p1" style="margin:0px;font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;font-size:10px;line-height:normal;font-family:Monaco;color:rgb(242,242,242);background-color:rgba(0,0,0,0.85)"><span class="gmail-s1" style="font-variant-ligatures:no-common-ligatures">export MANPATH=/opt/local/share/man:$MANPATH</span></p></div><div><br></div><div>Also, do you have Xcode's command line tools installed? (you should have to get macports running, but sometimes and update screws that up)..</div><div><br></div><div>Can you run the following commands and port the output:</div><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div>which gcc</div><div>which g++</div><div>which make</div></blockquote><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div>printenv</div></blockquote><div> <br></div><div>Given you have a "dirty" source directory, you may want to run a distclean or delete and repull from git the mythtv src. The tells us <span style="font-variant-ligatures:no-common-ligatures;background-color:rgba(0,0,0,0.85);color:rgb(242,242,242);font-family:Monaco;font-size:10px">ff_codec_id_strin </span>something went array with building or linking the external FFMPEG stuff.</div>
</div>