M
Mike
Building the TclTk extension on Max OS X (10.2.3)
1. Additions to 'extconf.rb' (justs bypasses all the config stuff)
5,15d4
< if /darwin/ =~ RUBY_PLATFORM
< stubs = enable_config("tcltk_stubs") || with_config("tcltk_stubs")
< $CPPFLAGS += ' -DUSE_TCL_STUBS -DUSE_TK_STUBS' if stubs
< $CPPFLAGS += ' -DMAC_OSX_TCL -DMAC_OSX_TK'
< $CPPFLAGS += ' -I/Library/Frameworks/Tcl.framework/Headers'
< $CPPFLAGS += ' -I/Library/Frameworks/Tk.framework/Headers'
< $LDFLAGS += ' -framework Tcl -framework Tk'
< create_makefile("tcltklib")
< exit
< end
2. Added '#include <sys/time.h>' to 'tcltklib.c'
(for the definition of 'struct timeval')
3. Added '(const char **)' before 'av' on line 812,
(to avoid an incompatible-type warning)
TRAP_BEG;
ptr->return_value = (*info.proc)(info.clientData, ptr->ip,
argc, (const char **)av);
TRAP_END;
It builds OK.
The demos draw their windows, but the windows never activate.
Clicking on a window gives an message:
SetFrontProcess failed,-606
which is some stupid Apple message.
You have to go to another shell to find the PID to kill it.
Any clues?
1. Additions to 'extconf.rb' (justs bypasses all the config stuff)
5,15d4
< if /darwin/ =~ RUBY_PLATFORM
< stubs = enable_config("tcltk_stubs") || with_config("tcltk_stubs")
< $CPPFLAGS += ' -DUSE_TCL_STUBS -DUSE_TK_STUBS' if stubs
< $CPPFLAGS += ' -DMAC_OSX_TCL -DMAC_OSX_TK'
< $CPPFLAGS += ' -I/Library/Frameworks/Tcl.framework/Headers'
< $CPPFLAGS += ' -I/Library/Frameworks/Tk.framework/Headers'
< $LDFLAGS += ' -framework Tcl -framework Tk'
< create_makefile("tcltklib")
< exit
< end
2. Added '#include <sys/time.h>' to 'tcltklib.c'
(for the definition of 'struct timeval')
3. Added '(const char **)' before 'av' on line 812,
(to avoid an incompatible-type warning)
TRAP_BEG;
ptr->return_value = (*info.proc)(info.clientData, ptr->ip,
argc, (const char **)av);
TRAP_END;
It builds OK.
The demos draw their windows, but the windows never activate.
Clicking on a window gives an message:
SetFrontProcess failed,-606
which is some stupid Apple message.
You have to go to another shell to find the PID to kill it.
Any clues?