QMPlay2: why does it hardcode clang?

Open barracuda156 opened this issue 1 year ago • 2 comments

https://github.com/RJVB/macstrop/blob/ed6e80a92ea4ee583a359b2417a7da8ed03a6afd/multimedia/qmplay2/Portfile#L185-L188

What is the issue with building with gcc?

I certainly can build it with gcc, though I use a version compatible with Qt4 (i.e. not the latest one).

Jul 22 '24 08:07 barracuda156

On Monday July 22 2024 01:36:02 Sergey Fedorov wrote:

https://github.com/RJVB/macstrop/blob/ed6e80a92ea4ee583a359b2417a7da8ed03a6afd/multimedia/qmplay2/Portfile#L185-L188

What is the issue with building with gcc?

Look at what line 187 does ;)

More recent QMPlay2 versions contain ObjC++ files that use Apple-specific language features not supported by GCC. So those need to be built with clang++.

Jul 22 '24 10:07 RJVB

More recent QMPlay2 versions contain ObjC++ files that use Apple-specific language features not supported by GCC

Oh, this is an infinite source of trouble. Got it.

Jul 22 '24 11:07 barracuda156