[MacPorts] #40762: xcode portgroup only recognizes Xcode compilers

[MacPorts]

#40762: xcode portgroup only recognizes Xcode compilers
---------------------------+--------------------------------
  Reporter:  ryandesign@…  |      Owner:  macports-tickets@…
      Type:  enhancement   |     Status:  new
  Priority:  Normal        |  Milestone:
 Component:  ports         |    Version:
Resolution:                |   Keywords:
      Port:                |
---------------------------+--------------------------------

Comment (by egall@…):

 Replying to [comment:3 ryandesign@…]:
 > If we need to write Xcode plugins (which appear to just be folder-
 bundles with a plist inside) to get Xcode to understand MacPorts
 compilers, we can have each compiler port do that
 I'd recommend making the Xcode plugins be subports of each compiler port,
 so that way people who don't want to or can't use the plugin with Xcode
 can avoid it.
 >  * Can we tell Xcode to look in a particular directory for plugins (e.g.
 somewhere under ${prefix}) or must it be a particular directory (e.g. in
 /Library/Application Support)?
 >  * Is this directory the same for all versions of Xcode that MacPorts
 supports — Xcode 2 on Tiger through Xcode 5 on Mavericks and beyond?
 >  * Can we write a single plugin that works in all versions of Xcode or
 do different Xcode versions need different plugins?

 There are many different directories that plugins can be found in, and
 some of them are compatible between Xcode versions, while others aren't. I
 think if we use the `${developer_dir}` variable we should be good though,
 because that already varies between different versions, and I'm pretty
 sure it does it correctly.

-- 
Ticket URL: <https://trac.macports.org/ticket/40762#comment:4>
MacPorts <http://www.macports.org/>
Ports system for OS X