#15405 closed defect (fixed)
xcode.project variable handles strings as lists
Reported by: | rhwood@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.6.0 |
Keywords: | Cc: | jmroot (Joshua Root) | |
Port: |
Description
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.
Change History (3)
comment:1 Changed 16 years ago by tobypeterson
Milestone: | MacPorts base bugs → MacPorts Future |
---|
comment:2 Changed 16 years ago by jmroot (Joshua Root)
Cc: | jmr@… added |
---|---|
Resolution: | → fixed |
Status: | new → closed |
Fixed in r47758.
comment:3 Changed 15 years ago by jmroot (Joshua Root)
Component: | base → ports |
---|---|
Milestone: | MacPorts Future |
Note: See
TracTickets for help on using
tickets.
Milestone MacPorts base bugs deleted