Re: Qt terminal

[Mojca M. <moj...@gm...>]

2012/1/8 Jérôme Lodewyck wrote:
> Le Dimanche 8 Janvier 2012 17:45:08 vous avez écrit :
>> I had to replace Cocoa/Cocoa.h with Carbon/Carbon.h. Import of Cocoa
>> doesn't work and I have no idea why (maybe because it is in Objective
>> C and some compiler flags bail?). I also have no idea how safe it is
>> to use Carbon, but apparently it worked this time.
>
> Just for the fun, here is a version that should compile with Cocoa.

Thank you very much. It compiles and works fine (not that I understand
what is the difference since AquaTerm is also using Objective C and
there is no special compiler, maybe only some different flags).

> Beware it
> breaks the build systems on non-OSX systems (I don't know how to conditionally
> add sources for a given OS in Makefile.am...). As far as I understand, the
> problem with Carbon is that it is somehow obsolete and apperently does not
> work on 64 bits systems.

I'm not sure what is going one. I also believed that Carbon was 100%
forbidden in 64-bit applications, but your previous code with
Cocoa->Carbon worked and:

> file /System/Library/Frameworks/Carbon.framework/Carbon
/System/Library/Frameworks/Carbon.framework/Carbon: Mach-O universal
binary with 2 architectures
/System/Library/Frameworks/Carbon.framework/Carbon (for architecture
x86_64):	Mach-O 64-bit dynamically linked shared library x86_64
/System/Library/Frameworks/Carbon.framework/Carbon (for architecture
i386):	Mach-O dynamically linked shared library i386

Maybe there is some core part of functionality in Carbon that still
works, but even that might easily disappear at any given moment
without notice. My bet is that next OS version won't ship Carbon at
all.

Mojca

PS: what exactly is -DXAPPLRESDIR=\"/etc/X11/app-defaults/\"? That
folder doesn't exist.