Some ports are failing to build due to new build system in Xcode 10

[mf2k (Frank Schima)]

Xcode 9 introduced a new build system but it was not the default. Xcode 10 has made it the default.

This is an example of a failure message usually seen.

:info:build Details:  Failed to create workspace arena at <DVTFilePath:0x7f9ad0459500:'/Users/macports/Library/Developer/Xcode/DerivedData/pinentry-mac-asqmjqvkuvyzkeaduqaryxjqemdk'>: Error Domain=NSCocoaErrorDomain Code=513 "You don’t have permission to save the file “pinentry-mac-asqmjqvkuvyzkeaduqaryxjqemdk” in the folder “DerivedData”." UserInfo={NSFilePath=/Users/macports/Library/Developer/Xcode/DerivedData/pinentry-mac-asqmjqvkuvyzkeaduqaryxjqemdk, NSUnderlyingError=0x7f9ad02c4190 {Error Domain=NSPOSIXErrorDomain Code=1 "Operation not permitted"}}
75	:info:build Object:   <IDEWorkspaceArena: 0x7f9ad01ea080>
76	:info:build Method:   -createWorkspaceArenaFolderIfNecessary
77	:info:build Thread:   <NSThread: 0x7f9acb617690>{number = 1, name = main}
78	:info:build Please file a bug at https://bugreport.apple.com with this warning message and any useful information you can provide.

This ticket will track ports that are affected by it. It is a work in progress so feel free to add/remove ports and improve my description of it.

port	maintainer	status
BGHUDAppKit		​https://github.com/macports/macports-ports/pull/2720
cotvnc		#57174
gimp-app		​#2718
macports-notifier		#57209
MacVim		#57170
pinentry-mac	@Ionic	#57178
terminal-notifier	@raimue,openmaintainer	#57210
VLC	@RJVB,openmaintainer	#57260
xhyve	@jeremyhu	#57223

[michaellass (Michael Lass)]

BGHUDAppKit is also affected. A workaround was proposed as ​#2720.

[michaellass (Michael Lass)]

... and so is VLC: #57260

[Aaron Madlon-Kay <amake@…>]

In 6e5b5bd7177b4ae6cbf3ee31d5a6409dd2258775/macports-ports (master):

gimp-app: fix build on macOS 10.14

refs #57234

[pmetzger (Perry E. Metzger)]

BTW note that the kludge for this is really only needed for destroot. Typically if the build itself fails and is fixed by this, it means that the include statements in the sources are incorrectly using angle brackets instead of double quotes.

[kencu (Ken)]

I would worry that using the new build system for the build and then the old build system for the destroot might truly be leading into totally unknown territory. Seems logical to me to use one or the other throughout.

[kencu (Ken)]

Replying to pmetzger:

it means that the include statements in the sources are incorrectly using angle brackets instead of double quotes.

This behaviour seems to have changed in Xcode10. I am unable to find any documentation about exactly what is different about the CPP search path handling anywhere on the web so far (if that is what this is about). I would appreciate any information anyone knows about this.