Missing Targets on latest Qt

[Francisco-DAnconia]

I installed the latest Qt opensource software (Creator 18.0.01, Qt 6.10.1) on macOS Sonoma. When I open the Fulcrum.pro project (v. 2.1.0) I only see one target, the Debug Target.

What needs to be done to see/build the Release target?

Btw, the Debug target appears to build fine.

Thanks

[cculianu]

Hmm something might be unusual about your setup? I think you need to mess around with Qt Creator to get it to show/do the release target. Go into the project setup screens, etc. Let me know if after messing around, you still couldn't figure it out and I can look at it as well. Basically the idea is wrestle with the settings to enable that target.

[Francisco-DAnconia]

Thanks.
It turned out I had to delete the ".qtcreator" hidden folder. Then the targets could be configured as expected.

However, while troubleshooting this I ran into 2 issues.

1. On an arm64 machine building on Sequoia, I get two warnings. Are these expected?

ld: warning: building for macOS-11.0, but linking with dylib '@rpath/QtNetwork.framework/Versions/A/QtNetwork' which was built for newer version 13.0
ld: warning: building for macOS-11.0, but linking with dylib '@rpath/QtCore.framework/Versions/A/QtCore' which was built for newer version 13.0

2. I was pleasantly surprised when I resolved the .qtcreator problem on x86_64. I didn't have to pass the zeroMQ LIBS & INCLUDEPATH arguments and it also picked up miniupnpc.

But, on the arm_64 Sequoia machine I could never get this to work. Neither with MacPorts nor Homebrew.

PKG_CONFIG_PATH is configured and pkg-config works from the Terminal:

pkg-config --cflags --libs libzmq                                                                                      
-I/opt/local/include -L/opt/local/lib -lzmq
pkg-config --cflags --libs miniupnpc                                                                                    
-I/opt/homebrew/Cellar/miniupnpc/2.3.3/include -L/opt/homebrew/Cellar/miniupnpc/2.3.3/lib -lminiupnpc

When I went back to the x86_64 machine, regardless of how I had setup PKG_CONFIG_PATH it would only ever find Homebrew installed libraries never those from MacPorts. If I deleted the package in Homebrew, the installed MacPorts one was never found. Even though pkg-config worked fine in Terminal.

I even tested pkg-config [Homebrew] vs pkg-config [MacPorts] and the order of precedence in PKG_CONFIG_PATH.

Any thoughts?