On 3/28/12 1:36 PM, Alexander Hansen wrote:
> On 3/28/12 12:56 PM, William G. Scott wrote:
>>
>> On Mar 27, 2012, at 10:44 PM, Alexander Hansen wrote:
>>
>>> On 3/27/2012 10:14 PM, William G. Scott wrote:
>>>> On Mar 27, 2012, at 9:39 PM, Alexander Hansen wrote:
>>>>
>>>>> fink-0.32.4.1 supports Xcode 4.3.x in whatever
>>>>> location it is installed.
>>>> Hi Alexander:
>>>>
>>>> Is there any reason a user needs to have Xcode installed, since the
>>>> command-line stuff and headers, etc, are all available via I
>>>> separate stand-alone download?
>>>>
>>>> Bill
>>>>
>>>>
>>> Good question. I haven't actually checked to see what the
>>> ramifications of that would be. Any package which builds using
>>> xcodebuild wouldn't function, and such packages would need to have
>>> an explicitly declared BuildDepends: xcode. The bootstrap script
>>> would need to be modified as well, since it now checks for Xcode.
>>>
>>> Beyond that, I'm not sure. I'll cc the developer list with my reply
>>> for any thoughts.
>> FWIW,
>>
>> % which xcodebuild
>> /usr/bin/xcodebuild
>>
>> It seems to get installed with the command-line tools. This is on a
>> laptop with no Xcode installed (due to space).
>>
>> The download is here: https://developer.apple.com/downloads and is
>> entitled "Command Line Tools for Xcode, late March"
>>
>> I've been hoping for this for about 10 years.
>>
>> Bill
>>
> Since I've got a spare 10.7 box handy, I'm going to set up a
> buildworld on it to built the entire current Lion distribution to see
> what can't be built with just the command-line tools. I can also
> test bootstrapping.
>
I've found a few things of interest so far.
Quite a few package uses a versioned dependency on "xcode". Of course,
any package which uses BuildDepends xcode (>= 3.1) on Lion can have that
removed :-) , but it's probably a good idea to use some more
fine-grained versioned virtual compiler packages instead.
I'd like to make a similar change to the gcc4N virtuals that I did for
the system SDKs. For example I get the following from Xcode 4.3.2:
$ fink --trees=virtual list -t gcc
Scanning package description files
Information about 279 packages read in 2 seconds.
broken-gcc 3.3-1 [virtual package representing a broken
gcc compiler]
gcc2 2.95.2-0 [virtual package representing the gcc 2.95.2
compiler]
gcc2.95 2.95.2-0 [virtual package representing the gcc
2.95.2 compiler]
gcc3.1 3.1-0 [virtual package representing the gcc 3.1
compiler]
gcc3.3 3.3-0 [virtual package representing the gcc 3.3
compiler]
gcc4.0 4.0-0 [virtual package representing the gcc 4.0
compiler]
It seems kind of silly to keep most of these populated at this point on
Lion. :-) On the other hand, it seems like the gcc4.2 entry _should_ be
there, albeit not installed, because one _could_ install Xcode 4.1 if
desired.
I propose getting rid of gcc2, gcc2.95, and gcc3.1 for all
currently-supportd OS versions.
gcc3.3, gcc4.0, and gcc4.2 would be set as the possible compilers for
10.5, and then fink would check if they actually are present and show
them as installed if they are.
gcc4.0, gcc4.2, llvm, and clang would be set as the possible compilers
for 10.6, the latter two requiring new virtual packages. Under Xcode
4.2, gcc4.0 and gcc4.2 would normally be listed as uninstalled, but when
a 10.6 user installs Xcode 4.2 over Xcode 3.2.6 potentially all four
could show up.
gcc4.2, llvm, and clang would be set as the possibilities for 10.7.
gcc4.2 would be "installed" only for Xcode 4.1, or again, if it didn't
happen to get removed by a later install.
--
Alexander Hansen, Ph.D.
Fink User Liaison
http://finkakh.wordpress.com/2012/02/21/got-job/
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel
