xcode.project variable handles strings as lists

[rhwood@…]

The xcode.project portfile variable treats strings as lists.

The variable takes a single project file as an argument to be passed to xcode, but if a space is in the name, it passes the name wrapped in curly braces.

Expected result: setting xcode.project "Chat Core.xcodeproj" does not lead to an error

Returned result:

-->  Building ChatCore
Error: Target org.macports.build returned: shell command "cd "/opt/local/var/macports/build/_Users_Shared_Developer_MacPorts_Repository_trunk_dports_irc_ChatCore/work/trunk" && xcodebuild -project {Chat Core.xcodeproj} -target "ChatCore (Application)" -configuration Release build OBJROOT=build/ SYMROOT=build/ " returned error 1
Command output: xcodebuild: Error: the project name {Chat does not have a valid extension.

Note that {Chat Core.xcodeproj} is passed instead of Chat Core.xcodeproj

This issue is covered in #12429 which I did not reopen due to its commentary.

I found at least one portfile (source:trunk/dports/aqua/IcyJuice/Portfile) that has workarounds in it to address this behavior.

[toby@…]

Milestone MacPorts base bugs deleted

[jmr@…]

Fixed in r47758.