Re: [Fink-devel] First round of Xcode results

[Brendan C. <br...@fi...>]

On 12-03-29 09:32 AM, Alexander Hansen wrote:
> I decided not to wait the full 10 or so days it would require to do a
> buildworld :-)
>
> One important result is the following:
>
> $ xcodebuild -version
> Error: No developer directory found at
> /Applications/Xcode.app/Contents/Developer. Run /usr/bin/xcode-select to
> update the developer directory path.
>
> i.e. xcodebuild is installed but appears not to be functional without a
> /Developer directory.
>
> Just grepping through .info files, I found the following items:
>
> "xcode":
>
> aquaterm uses "xcodebuild", but doesn't have an explicit BuildDepends:
> xcode
> backupbouncer has a Depends: xcode. It's not clear from the .info file
> what components exactly are used.
> fontforge uses "xcode-select" to find the Developer directory but
> doesn't have an explicit BuildDepends: xcode
> fuse4x-kext use "xcodebuild", but doesn't have an explicit BuildDepends:
> xcode
> gcc46 | gcc47 have BuildDepends: ( xcode >= 3.1.2); it's not obvious
> from the .info files whether more than just the command-line tools are
> required.
> gtk+2 has a legacy script checking for Leopard-specific issues via
> "xcodebuild -version"
> jicmp | jicmp6 use the system SDKs, which require a full Xcode install.
> I've just fixed changes that _I_ made to those so they now have
> BuildDepends on the system-sdk* packages again.
> launch uses "xcodebuild" without an explicit BuildDepends: xcode
> octave-3.2.4 has BuildDepends: (xcode >= 3.1) because of merging with
> the 10.4 tree. Fixed now.
> qemu has BuildDepends: xcode (<= 4.1-1) | gcc46 ; presumably the xcode
> choice was to use gcc4.2. (Maintainer contacted separately)
> sbcl-N-maxima has a BuildDepends xcode (>=4.3). My note shows that this
> was because it first got along with clang from that version of Xcode,
> i.e. clang-3.1. A Bdep: clang (>=3.1) once that virtual package exists
> _should_ take care of this.
> wine-32bit has an explicit xcode dependency since it only builds with
> gcc-4.2 and currently uses the /Developer directory. Adding a
> BuildDepends: gcc4.2 would probably be a good idea, too.
> wxcocoa293 carries a BuildDepends: xcode (>=4.2.1) because it's patched
> to build with clang-3.0 or later. I'm not completely sure whether
> BuildDepends: clang (>=3.0) will suffice.
> wxmaxima carries a BuildDepends: xcode (>=4.2.1) because it appears to
> need to use the same compiler as wxcocoa293. This can probably go over
> to clang (>= 3.0).
>
> /Developer:
> qt4-base-mac | qt4-base-x11 have 'export
> PATH="/Developer/usr/bin:/usr/llvm-gcc-4.2:$PATH"'. It's not clear from
> the .info file whether anything beyond the CLI tools is needed.
> ruby18 uses '/Developer/Tools/Rez -t APPL Carbon.r -o
> %p/bin/ruby-aqua1.8 || true' in its PostInstScript; no explicit xcode
> dependency.
>
> If folks don't object, I can add BuildDepends: xcode immediately for the
> cases above where the issue is just that 'xcodebuild' or 'xcode-select'
> is being used.

No objection from me.