QMPlay2: why does it hardcode clang?

[barracuda156]

macstrop/multimedia/qmplay2/Portfile

Lines 185 to 188 in ed6e80a

	} elseif {[string match macports-gcc* ${configure.compiler}]} {
	# since building with GCC is mostly an experimental hack, just hardcode a build.dep on clang-12
	configure.objcxx ${prefix}/bin/clang++-mp-12
	depends_build-append port:clang-12

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).

[RJVB]

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++.

[barracuda156]

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.