Re: Using SystemConfiguration API inside KEXT
Re: Using SystemConfiguration API inside KEXT
- Subject: Re: Using SystemConfiguration API inside KEXT
- From: Jean-Daniel Dupas <email@hidden>
- Date: Tue, 11 May 2010 21:18:50 +0200
And so what ?
Anyway Apple is moving away gcc by developing a closed proprietary compiler call clang. Hum wait, my bad, clang is OpenSource and released under the BSD license.
Just out of curiosity, can you tell me how an apple hater end on an Apple developer mailing list ?
Le 11 mai 2010 à 21:12, John B Brown a écrit :
> Dear Folk,
>
> I do believe the first clue to the general lie that Apple supports a legitimate port of the GNU compiler system is the fact that Apple has not ported Glibc to the Mac OS.
>
> DUH!
>
> On 5/11/10 12:15 PM, David Leimbach wrote:
>> Reading documentation is bullshit too!
>>
>> On Tue, May 11, 2010 at 11:08 AM, Mo McRoberts<email@hidden> wrote:
>>
>>>
>>> On 11-May-2010, at 19:00, John B Brown wrote:
>>>
>>>> Dear Folk,
>>>>
>>>> I see that, in addition to screwing up other GNU utilities, Apple
>>> has screwed up the C and GNU compiler system. This is NOT porting, it is
>>> pulling a SUN; call it standard but make it proprietary.
>>>>
>>>> In order to write and compile C code on an Apple you must ignore
>>> the workings of the C and GNU compilers and use a proprietary Apple system.
>>>>
>>>> That is pure BULLSHIT!
>>>
>>> The framework-supporting extensions have been part of GCC for, literally,
>>> years. I might be wrong, but I’m pretty sure they were part of the
>>> enhancements which NeXT contributed back to the GCC project as part of
>>> support for Objective-C. It just happens that GCC only enables this
>>> functionality when built for Darwin, but it’s part of the mainline source
>>> (indeed, there have been plenty of people over the years asking if it can be
>>> enabled on other platforms, too).
>>>
>>> In this case, looking in framework paths for headers is a pretty
>>> straightforward backwards-compatible enhancement. Not exactly “pure
>>> BULLSHIT”, whichever way you look at it. You don’t ignore the workings of
>>> the C and GNU compilers (which in many cases are one and the same — clang
>>> behaves the same way, though, for obvious reasons); you just RTFM when
>>> developing on the platform and be aware that the compilers do more on Darwin
>>> than they do on other systems.
>>>
>>> There are *dozens* of platform-specific aspects to the GNU Compiler System
>>> and Binutils. Are they all bullshit, too?
>>>
>>> M.
>>>
>>> _______________________________________________
>>> Do not post admin requests to the list. They will be ignored.
>>> Darwin-dev mailing list (email@hidden)
>>> Help/Unsubscribe/Update your Subscription:
>>>
>>> This email sent to email@hidden
>>>
>>
>
>
>
>
> Shalom,
>
> John B. Brown.
> [email@hidden]
> 358 High Street,
> Buffalo, Wyoming
> 82834
>
> "Freedom is not worth having if it does not include
> the freedom to make mistakes" Mahatma Gandhi
> "If any question why we died, tell them,
> because our fathers lied." Rudyard Kipling
> "A man who does not know the truth is just an idiot
> but a man who knows the truth and calls it a lie
> is a crook." Bertolt Brecht
> "I wonder whether the world is being run
> by smart people who are putting us on
> or by imbeciles who really mean it." Mark Twain
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Darwin-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
-- Jean-Daniel
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden