[gtkada] gtkada 2.2.1 on mac os x

[Thomas De Contes]

Le dimanche, 5 déc 2004, à 23:42 Europe/Paris, Jacob Sparre Andersen a  
écrit :

> What is the current status of GtkAda for Mac OS X?
>
> My Linux system just died, so I'm stuck with developing on a
> Mac OS X system.

:-D you're welcome :-)

> It would be nice, if it was as easy to get started with Ada
> programming on Mac OS X as it is on Debian.

normally, no problem

i've made scripts to make it easier, online here :
http://tDeContes.hd.free.fr/miseADisposition/contributions/ 
install%20scripts/
(i invite you to read them before continue, if not you may not  
understand the rest)


but right now i have problems (i hope they'll be resolved soon) :

at the moment of applying the gtkada patch :
patching file config.sub
Hunk #1 FAILED at 94.
Hunk #3 FAILED at 957.
patching file src/Makefile.in
Hunk #1 FAILED at 12.

then, running the gtkada sample :
testgtk/testgtk
raised CONSTRAINT_ERROR : gtk-handlers.adb:1368 access parameter is null

in fact, some prgms can not compile, some can compile but can not  
launch (testgtk), some can launch but can not do everything they should


and Nicolas Setton said me :

> It's gtk+-2.2.4.
[which is compatible with  
http://libre.act-europe.fr/GtkAda/GtkAda-2.2.1.tgz , because gtk+-2.4.x  
isn't]
>  But you'd be better off by working with the CVS version and  
> investigating the reasons why Jim Hopper's patch do not apply, and  
> fixing these. Or just wait until we integrate this patch in the CVS  
> version.

but darwinports provides only gtk+-2.4.x, :'(
and i'm available to help, but i'm not able to do all myself


so i invite you to make a lobbying on Nicolas Setton and Jim Hopper to  
make what we need to have gtkada working ;-) :-D



ps : let me know if you have not the same result as me for gtkada, or  
if it doesn't work for the others :-)



btw, Jim, i've forget to ask in the last msg :
here is what i installed exactly when i installed xcode 1.5 (pdf) :
http://tDeContes.hd.free.fr/aide/ada/gtk/x%20code%20install/
is it right ?