tcl-mac — Q&A for Tcl on the Macintosh platform

Re: [MACTCL] Building Aqua Tk on MacOS X

[James B. <jk...@mr...>]

On Fri, Mar 01, 2002 at 04:15:23PM +0100, Jean-Claude Wippler wrote:
> Is it a good idea to get the macosx branches of tcl/tk from CVS, HEAD
> revision and follow instructions (which?) from there on?

You want the macosx-8-4-branch.

cvs -d:pserver:ano...@cv...:/cvsroot/tktoolkit login
cvs -z3 -d:pserver:ano...@cv...:/cvsroot/tktoolkit \
    co -r macosx-8-4-branch tk
cvs -z3 -d:pserver:ano...@cv...:/cvsroot/tcl \
    co -r macosx-8-4-branch tcl

Don't rename the tcl/tk directories as they need to be called this way (tk
includes ../tcl/generic) - put them in a sub-directory if you want to name
them after the release.

From there it's quite easy - just run the Project Builder on the
macosx/*.pbproj files.

James

-- 
James Bonfield (jk...@mr...)   Fax: (+44) 01223 213556
Medical Research Council - Laboratory of Molecular Biology,
Hills Road, Cambridge, CB2 2QH, England.
Also see Staden Package WWW site at http://www.mrc-lmb.cam.ac.uk/pubseq/

Re: [MACTCL] Building Aqua Tk on MacOS X

[Franc B. <br...@cb...>]

Dear Jean-Claude,

I'll be eternally grateful if you can document and post an "OS X 
tcltk install process for the dummies" that is transparently as 
simple as one under OS9.x now, so that I end up with an environment 
where I can just copy most existing OS9.x tcltk programs to OS X 
partition and invoke them readily with tclsh or wish under OS X (as I 
do now under OS 9.2). Making a "drag & drop tclet" would be nice but 
is not an essential priority (for me at least).

I didn't get too far in October -- the version was buggy, and despite 
kind help from Jim, it was way too early for someone with my limited 
experience to continue -- I'll get back to OS X once I am confident 
that our OS9.2 tcktk programs will "just work as is" under OS X as 
well as they do currently under unix, linux, and windows.

We have by now developed, UNDER macOS9.2, a very comfortable 
cross-platform "8.3.4 ticklish environment" that will address and 
resolve a number of questions from less experienced tcltk 
mac-programmers on this forum -- including platform independent 
self-installation of paths for each and every program and library 
package we develop. We hope to have this environment documented and 
ready for release by the tcltk conference submission deadline. It 
will be a tribute to all tcltk mac-developers who made this 
mac-platform development possible for us -- in particular if we can 
port it cleanly also to macOS X and report on it.

Many thansk to Jim, you, and others "in the know".

Franc

PS -- once you made a posting, pls send mail under a new header, eg.
      "OS X tcltk installation, testing, and verification notes"

At 4:15 PM +0100 3/1/02, Jean-Claude Wippler wrote:
>Steve Landers <st...@di...> wrote:
>
>>I'm trying to build Aqua Tk on MacOS X, using Jim's instructions posted
>>back in October. I'm doing this in the hope of getting TclKit working on
>>Aqua Tk supporting dynamic loading.
>[...]
>>BTW, the machine is an iBook running MacOS X 10.1.3 using the December
>>2001 developer tools.
>
>I'd like to help.  I have just configured the same setup from scratch,
>and am about to grab Tcl/Tk etc sources (also incrtcl).  Given that my
>setup is clean, this will make a good test case for working through the
>entire build process.
>
>Is it a good idea to get the macosx branches of tcl/tk from CVS, HEAD
>revision and follow instructions (which?) from there on?
>
>If someone can point me to the proper spot(s), I'll report my progress.
>Steve: the least that ought to come out is finding out whether/how your
>setup differs from mine in any way.
>
>-jcw
>
>
>_______________________________________________
>Tcl-mac mailing list
>Tc...@li...
>https://lists.sourceforge.net/lists/listinfo/tcl-mac

[MACTCL] OS X tcl/tk installation

[Jason S. <je...@ya...>]

Hi all,

I was thinking about how to make the installation a bit easier for the end
user.
Would the maintainers consider making a dmg file with the tarball and an
installation shell script?  Off the top of my head... something like:



#!/bin/sh

touch /.can_i_write > /dev/null 2>&1

if [ $? -eq 0 ] ; then
    /bin/rm -f /.can_i_write
    echo "Installing for all users..."
    INSTALL_DIR="/"
    SYMLINK_DIR="/usr/bin"
else
    echo Installing for `whoami`...
    INSTALL_DIR=$HOME
    SYMLINK_DIR=${HOME}/bin
fi

TARBALL=`pwd`/MacOSXTk8.4a4-2.tar.gz
cd $INSTALL_DIR
tar -xzf $TARBALL
ln -s ${INSTALL_DIR}/Applications/Wish\ Shell.app/Contents/MacOS/Wish\ Shell
${S
YMLINK_DIR}/wish


__________________________________________________
Do You Yahoo!?
Yahoo! Greetings - Send FREE e-cards for every occasion!
http://greetings.yahoo.com

RE: [MACTCL] Building Aqua Tk on MacOS X

[macnerd <ma...@re...>]

Does AguaTK use Cocoa/OPENSTEP or is it a Carbon thing?

-----Original Message-----
From: tcl...@li...
[mailto:tcl...@li...]On Behalf Of Jean-Claude
Wippler
Sent: Friday, March 01, 2002 7:15 AM
To: tc...@li...
Subject: Re: [MACTCL] Building Aqua Tk on MacOS X


Steve Landers <st...@di...> wrote:

>I'm trying to build Aqua Tk on MacOS X, using Jim's instructions posted
>back in October. I'm doing this in the hope of getting TclKit working on
>Aqua Tk supporting dynamic loading.
[...]
>BTW, the machine is an iBook running MacOS X 10.1.3 using the December
>2001 developer tools.

I'd like to help.  I have just configured the same setup from scratch,
and am about to grab Tcl/Tk etc sources (also incrtcl).  Given that my
setup is clean, this will make a good test case for working through the
entire build process.

Is it a good idea to get the macosx branches of tcl/tk from CVS, HEAD
revision and follow instructions (which?) from there on?

If someone can point me to the proper spot(s), I'll report my progress. 
Steve: the least that ought to come out is finding out whether/how your
setup differs from mine in any way.

-jcw


_______________________________________________
Tcl-mac mailing list
Tc...@li...
https://lists.sourceforge.net/lists/listinfo/tcl-mac

Re: [MACTCL] Building Aqua Tk on MacOS X

[Jean-Claude W. <jc...@eq...>]

Steve Landers <st...@di...> wrote:

>I'm trying to build Aqua Tk on MacOS X, using Jim's instructions posted
>back in October. I'm doing this in the hope of getting TclKit working on
>Aqua Tk supporting dynamic loading.
[...]
>BTW, the machine is an iBook running MacOS X 10.1.3 using the December
>2001 developer tools.

I'd like to help.  I have just configured the same setup from scratch,
and am about to grab Tcl/Tk etc sources (also incrtcl).  Given that my
setup is clean, this will make a good test case for working through the
entire build process.

Is it a good idea to get the macosx branches of tcl/tk from CVS, HEAD
revision and follow instructions (which?) from there on?

If someone can point me to the proper spot(s), I'll report my progress. 
Steve: the least that ought to come out is finding out whether/how your
setup differs from mine in any way.

-jcw

Re: [MACTCL] Setting environment vars from tcl

[James B. <jk...@mr...>]

On Thu, Feb 28, 2002 at 11:33:08AM -0800, Jim Ingham wrote:
> James,
> 
> I did notice this when I was playing around just yesterday.  It is odd, 
> because it mostly works just fine, and then every so often you will get 
> the "can't read..." error, or it will just silently fail to set the 
> environment.  Then one or two commands later it will work again.  Please 
> file a bug on this, and if you want to have a whack at it, that would be 
> great.  It is a pretty annoying bug.

I've tracked down the cause of the bug and a possible solution, although I
need to experiment further.

TclSetupEnv has:

    environ = *_NSGetEnviron();

When adding an environment variable we need to extend environ, which is done
using ckalloc and memcpy. However an array names or similar function will
recall TclSetupEnv and so throws away our extended copy. Even if it didn't
call TclSetupEnv we'd still have problems for subprocesses as we haven't
actually changed the environment, we've just made a copy.

So just after the reallocate I added:

char ***e = _NSGetEnviron();
*e = environ;

and lo the problem has vanished! I'm guessing that this has nothing at all to
do with MacOS X, but to do with the earlier mac versions too. I admit that I
was a little suprised I could change the environment just like that, but I'm
happy I can.

I'll produce a patch and submit this to sourceforge.

James

-- 
James Bonfield (jk...@mr...)   Fax: (+44) 01223 213556
Medical Research Council - Laboratory of Molecular Biology,
Hills Road, Cambridge, CB2 2QH, England.
Also see Staden Package WWW site at http://www.mrc-lmb.cam.ac.uk/pubseq/

Re: [MACTCL] tbcload 1.3

[Alexander S. <A.S...@se...>]

> 
> I believe they are only platform independent because somebody
> out there wrote tbcload13 for the mac. Scriptics didn't write this
> in their tclpro, as they had given up supporting macOS. So I wonder who
> developed this and also whether tbcload 1.3 will translate the
> byte codes created in tclpro 1.4. I recently download tclpro 1.4 for
> windows, so one of these days I'll try mac-tbcload13
> to see if it works, but I was wondering if it's been tested yet
> by anyone else and who to turn to with problems.

The byte code it self is platform independend.
I only compiled the tbcload library and it worked without problems.

> 
> RK
> 
> Alexander Schoepe wrote:
> > 
> > Am Mittwoch den, 27. Februar 2002, um 19:29, schrieb Robert Karen:
> > 
> > > I noticed this project in sourceforge.net,
> > > but I don't see any info about it or any
> > > emails associated with it. Does anyone know
> > > if it is solid. Also, can I use tclpro _1.4_ on
> > > windows to build tbc files and then use _1.3_
> > > on mac to read them?
> > yes
> > > This would be on Mac OS 8 and 9.
> > >
> > > Thanks for any leads.
> > >
> > > Robert Karen
> > >
> > 
> > tbcload comes with TclPro v1.4 and v1.5 and the .tbc files are platform
> > independend.
> > 
> > alexander schoepe

Re: [MACTCL] Hello... (INTRO)

[Jim I. <ji...@ap...>]

Joaqin,

Welcome...

On Thursday, February 28, 2002, at 12:01  PM, macnerd wrote:

>
> Hi all.
>
> I am a whitebox server QA tester.  I am interested in learning 
> scripting languages to
> see how they can benefit testing.  I am now using ActivePerl on 
> Windows, and I am
> using tools to do OLE Automation with MS Outlook 2k.  I would like to 
> monitor other
> languages like tcl/tk and python as well.
>
> Personally, I own a pc-box, a G4 cube, and a g4 titanium.  I run both 
> Mac OS 9.x
> and Mac OS X. I like MacOS X because they added korean and chinese 
> support
> recently, and also because it is UNIX, and it is well ... cool.  I do 
> web-projects
> with XML and SOAP stuff at home using Linux.
>
> On the Mac OS, I would like monitor and play with some thigns:
>
>    - use AppleEvents to puppeteer applications and have better 
> integration with the MacOS

There are two extensions to use AppleEvents from Tcl, TclAppleScript, 
and TclAE.  The former compiles AppleScript code & executes it, the 
latter sends raw apple event.

>    - use Carbonized version to have pretty gem-like Aqua buttons under 
> MacOS X

Have fun!

>    - have a build system in MPW for classic builds as I get aggravated 
> with CodeWarrior
>      proj files NEVER working.  Move resources to .r's to better 
> maintainability and check-in,
>      if this is not done already.

Somebody had MPW project files a while ago.  The problem was that the 
MPW C libraries are buggy, and so some things didn't work.  The previous 
reason for using MPW was 'cause it was free.  Don't know if these are 
still around (I didn't keep them) but if you can find them you might get 
them to use the MW C libraries instead...

>
> For general technologies I am interested in the following to work with 
> Mac OS
>
>    - TclDP, Tix, and other toys common in tck/tk world

TclDP has not been maintained for a while.  I don't think it runs on 
Tcl8.3 or 8.4.  Somebody wrote a Tcl only version of some of the RPC 
stuff in TclDP.  There isn't a UDP module for Tcl right now, IIRC...  
Tix has never been ported to Classic MacOS but a MacOS X port is in the 
works.

>    - TclSOAP
>    - any and all freeware XML solutions (expat, DOM, SAX, TrAX, PDOM)
>    - CGI parsing algorithms
>    - TclODBC
>    - Combat (CORBA in Tcl)
>    - AOLServer
>    - DB server (there was one out there but it disappeared)
>

Any standard Tcl extensions (as opposed to Tk extensions) compile pretty 
straightforwardly on Mac OS X, but are much harder to get working on 9.  
Tk ones can be trickier...

Jim
--
Jim Ingham                                   ji...@ap...
Developer Tools - gdb
Apple Computer

Re: [MACTCL] tbcload 1.3

[Alexander S. <a.s...@se...>]

Am Mittwoch den, 27. Februar 2002, um 19:29, schrieb Robert Karen:

> I noticed this project in sourceforge.net,
> but I don't see any info about it or any
> emails associated with it. Does anyone know
> if it is solid. Also, can I use tclpro _1.4_ on
> windows to build tbc files and then use _1.3_
> on mac to read them?
yes
> This would be on Mac OS 8 and 9.
>
> Thanks for any leads.
>
> Robert Karen
>

tbcload comes with TclPro v1.4 and v1.5 and the .tbc files are platform 
independend.

alexander schoepe

RE: [MACTCL] Setting environment vars from tcl

[Robert C. <ro...@iC...>]

I've set environment variables without any problems. I don't have OS X or
TCL here at work to show the results but doing a "parray env" should list
like the following:


% array set env "DELIGHT /Applications/Graphics/3Delight-0.9.2"

% parray env
  [..other env vars...]
env(DELIGHT) = /Applications/Graphics/3Delight-0.9.2


(I hope I remembered this right. I'll look at home tonight and repost if
its wrong.)

-- 
Robert Coldwell
ro...@iC...

[MACTCL] Hello... (INTRO)

[macnerd <ma...@re...>]

Hi all.

I am a whitebox server QA tester.  I am interested in learning scripting =
languages to
see how they can benefit testing.  I am now using ActivePerl on Windows, =
and I am
using tools to do OLE Automation with MS Outlook 2k.  I would like to =
monitor other
languages like tcl/tk and python as well.

Personally, I own a pc-box, a G4 cube, and a g4 titanium.  I run both =
Mac OS 9.x=20
and Mac OS X. I like MacOS X because they added korean and chinese =
support
recently, and also because it is UNIX, and it is well ... cool.  I do =
web-projects=20
with XML and SOAP stuff at home using Linux.

On the Mac OS, I would like monitor and play with some thigns:
=20
   - use AppleEvents to puppeteer applications and have better =
integration with the MacOS
   - use Carbonized version to have pretty gem-like Aqua buttons under =
MacOS X
   - have a build system in MPW for classic builds as I get aggravated =
with CodeWarrior
     proj files NEVER working.  Move resources to .r's to better =
maintainability and check-in,
     if this is not done already.

For general technologies I am interested in the following to work with =
Mac OS
  =20
   - TclDP, Tix, and other toys common in tck/tk world
   - TclSOAP
   - any and all freeware XML solutions (expat, DOM, SAX, TrAX, PDOM)
   - CGI parsing algorithms
   - TclODBC
   - Combat (CORBA in Tcl)
   - AOLServer
   - DB server (there was one out there but it disappeared)

regards,=20
  Joaquin

Re: [MACTCL] Setting environment vars from tcl

[Jim I. <ji...@ap...>]

James,

I did notice this when I was playing around just yesterday.  It is odd, 
because it mostly works just fine, and then every so often you will get 
the "can't read..." error, or it will just silently fail to set the 
environment.  Then one or two commands later it will work again.  Please 
file a bug on this, and if you want to have a whack at it, that would be 
great.  It is a pretty annoying bug.

Jim

On Thursday, February 28, 2002, at 10:15  AM, James Bonfield wrote:

> There seems to be a bug in keeping the program environment and env() 
> array
> synchronised. I've tried this with the macos8-4-branch and the tclsh 
> shipped
> with the mac. This is under MacOS X.
>
> % set env(a) b;puts $env(a)
> b
> % parray env
> env(DYLD_LIBRARY_PATH) = /Users/pubseq/share/lib/macosx-binaries
> env(ENV_SET)           =
> env(GROUP)             = staff
> [cut for brevity]
> env(_)                 = /usr/bin/tclsh
> % puts $env(a)
> can't read "env(a)": no such variable
>
> array names has the same problem:
>
> % set env(a) b
> b
> % puts $env(a)
> b
> % array names env
> MANPATH HOME STADENROOT PWD LOGNAME ENV_SET DYLD_LIBRARY_PATH GROUP HOST
> VENDOR TERM SHELL HOSTTYPE GTAGDB SHLVL REMOTEHOST STADLIB MACHTYPE 
> OSTYPE
> MACHINE STADENROOT_2001 PATH _ STADTABL USER
> % puts $env(a)
> can't read "env(a)": no such variable
> %
>
> I thought I'd submitted this to sourceforge somewhere, but now I can't 
> see
> it. Anyway, just incase it didn't make it in there I thought I'd ask 
> here if
> anyone has seen this bug? I may have a look into this myself as that 
> bit of
> code is nice and Unix like so it shouldn't be too daunting :-)
>
> James
>
> --
> James Bonfield (jk...@mr...)   Fax: (+44) 01223 213556
> Medical Research Council - Laboratory of Molecular Biology,
> Hills Road, Cambridge, CB2 2QH, England.
> Also see Staden Package WWW site at http://www.mrc-lmb.cam.ac.uk/pubseq/
>
> _______________________________________________
> Tcl-mac mailing list
> Tc...@li...
> https://lists.sourceforge.net/lists/listinfo/tcl-mac
>
--
Jim Ingham                                   ji...@ap...
Developer Tools - gdb
Apple Computer

[MACTCL] Setting environment vars from tcl

[James B. <jk...@mr...>]

There seems to be a bug in keeping the program environment and env() array
synchronised. I've tried this with the macos8-4-branch and the tclsh shipped
with the mac. This is under MacOS X.

% set env(a) b;puts $env(a)
b
% parray env
env(DYLD_LIBRARY_PATH) = /Users/pubseq/share/lib/macosx-binaries
env(ENV_SET)           = 
env(GROUP)             = staff
[cut for brevity]
env(_)                 = /usr/bin/tclsh
% puts $env(a)
can't read "env(a)": no such variable

array names has the same problem:

% set env(a) b
b
% puts $env(a)
b
% array names env
MANPATH HOME STADENROOT PWD LOGNAME ENV_SET DYLD_LIBRARY_PATH GROUP HOST
VENDOR TERM SHELL HOSTTYPE GTAGDB SHLVL REMOTEHOST STADLIB MACHTYPE OSTYPE
MACHINE STADENROOT_2001 PATH _ STADTABL USER
% puts $env(a)
can't read "env(a)": no such variable
% 

I thought I'd submitted this to sourceforge somewhere, but now I can't see
it. Anyway, just incase it didn't make it in there I thought I'd ask here if
anyone has seen this bug? I may have a look into this myself as that bit of
code is nice and Unix like so it shouldn't be too daunting :-)

James

-- 
James Bonfield (jk...@mr...)   Fax: (+44) 01223 213556
Medical Research Council - Laboratory of Molecular Biology,
Hills Road, Cambridge, CB2 2QH, England.
Also see Staden Package WWW site at http://www.mrc-lmb.cam.ac.uk/pubseq/

[MACTCL] tbcload 1.3

[Robert K. <ro...@cr...>]

I noticed this project in sourceforge.net,
but I don't see any info about it or any
emails associated with it. Does anyone know
if it is solid. Also, can I use tclpro _1.4_ on 
windows to build tbc files and then use _1.3_
on mac to read them?

This would be on Mac OS 8 and 9.

Thanks for any leads.

Robert Karen

Re: [MACTCL] Re: tclLoadDyld.c (was: Itcl on MacOSX)

[James B. <jk...@mr...>]

On Tue, Feb 26, 2002 at 10:29:55PM +1100, Daniel A. Steffen wrote:
> you need to run /usr/libexec/makewhatis as root
> 
> the /etc/weekly cron job does it for you if your machine is on at Sat 
> 4:30 am (c.f. /etc/crontab)

Our Mac is used much like a real Unix machine. It's always up and so the cron
jobs are run. The problem is not that makewhatis hasn't been run, but simply
that the format of the manual pages has not been thought out correctly. Either 
the NAME component needs to list all the function names contained within it so 
that makewhatis can add them to its database, or a dummy manual page needs to
be created. Eg:

% cat NSAddModule.3
.so man3/NSModules.3

(That's just a guess - I haven't checked in which man section it really is.)
This is the standard way of doing things on Digital Unix and several other
Unix systems, and it means that man works much more intuitively.

> I find that a google search for e.g. "NSAddImage" is often faster & 
> more productive than grep -r through my filesystem...

I do wonder how come apple don't run an internal-only web server on the system 
with a precomputed index of all the documentation using one of the standard,
and free, web search engines. That way searching in the online help would
actually work.

Anyway, thanks for the google idea. It does indeed come up with the goods (as
always it seems!).

James

-- 
James Bonfield (jk...@mr...)   Fax: (+44) 01223 213556
Medical Research Council - Laboratory of Molecular Biology,
Hills Road, Cambridge, CB2 2QH, England.
Also see Staden Package WWW site at http://www.mrc-lmb.cam.ac.uk/pubseq/

[MACTCL] Building Aqua Tk on MacOS X

[Steve L. <st...@di...>]

Hi folks,

I'm trying to build Aqua Tk on MacOS X, using Jim's instructions posted
back in October. I'm doing this in the hope of getting TclKit working on
Aqua Tk supporting dynamic loading.

I've grabbed the latest Tcl and Tk CVS sources (including Daniel's
tclLoadDylb patch) and stored them in the same directory.

As per the instructions, I've checked the "Place build products for this
project ..." option and in both projects set it to the tcl/macosx/build
directory.

Tcl builds just fine, but Tk fails to resolve the various _Tcl_ symbols
when linking (apparently it isn't seeing the stubs library).

As far as I can tell I've followed the instructions, but given that I'm
just starting to use Project Builder and the MacOS X development model
there's plenty of scope for errors on my part.

Anyway, can anyone suggest what to try next?

BTW, the machine is an iBook running MacOS X 10.1.3 using the December
2001 developer tools.

Many thanks

Steve

---

Steve Landers                     Scripting Design Studio
Digital Smarties                  st...@di...
Perth, Western Australia          www.digital-smarties.com

Re: [MACTCL] Re: tclLoadDyld.c (was: Itcl on MacOSX)

[Jim I. <ji...@ap...>]

James,

Most of the NS*** documentation is reachable from AppKit and Foundation 
main pages:

file:///Developer/Documentation/Cocoa/Reference/ApplicationKit/ObjC_classic/
AppKitTOC.html

and

file:////Developer/Documentation/Cocoa/Reference/Foundation/ObjC_classic/FoundationTOC.
html

I just stick these two in the toolbar links in IE, and I can usually 
find what I want scanning the index, but you can also grep in these two 
directories for some of the stuff.  The PB folks are working on better 
help searches, but that is not all there yet.  At least in the latest 
version of PB they use their own help viewer, rather than Help Viewer...

The NSAddImage etc calls are pretty obscurely documented, mostly in 
release notes.  Don't know exactly this is, but these are not really 
normal user level calls, the NSBundle API's are the higher level 
user-friendly loading calls...

As Daniel says, you can run /usr/libexec/makewhatis.  I think this was 
supposed to be run as part of the devtools post-install script, but got 
left out somehow.  We also need to figure out a better way to do the 
cron stuff.  Most Unix machines never sleep & never get turned off, and 
a lot of the traditional unix self-care stuff is based on this 
assumption.  That is not true for most Mac's, but you also wouldn't want 
to have your mac start churning with all the cron stuff it had missed 
when you turn it on in the morning.  The systems folks are working on 
some elegant solution for this, but till then you may have to do some 
stuff by hand...

Jim

On Tuesday, February 26, 2002, at 01:59  AM, James Bonfield wrote:

> On Tue, Feb 26, 2002 at 04:14:25PM +1100, Daniel A. Steffen wrote:
>> man NSModule:
> ...
>
> On a related note, does anyone know how to get the most of the MacOS X 
> help?
> It's help centre is worse than useless, refusing to give me 
> documentation on
> things which I know exist.
>
> The Unix based man command works well, but Apple don't seem to have 
> created a
> proper whatis database. Therefore:
>
> [mac5031-1:~] jkb% man -k NSAddImage
> nsaddimage: nothing appropriate
> [mac5031-1:~] jkb% man NSAddImage
> man: no entry for NSAddImage in the manual.
>
> So how exactly am I meant to guess that "man NSModule" is the command 
> to get
> the NSAddImage (and friends) manual pages? I've resorted to using a 
> series of
> greps for most documentation lookups now which works very well, if a 
> bit slow,
> but alternative methods would be gratefully received!
>
> Anyway, many thanks for adding the patch Daniel.
>
> James
>
> --
> James Bonfield (jk...@mr...)   Fax: (+44) 01223 213556
> Medical Research Council - Laboratory of Molecular Biology,
> Hills Road, Cambridge, CB2 2QH, England.
> Also see Staden Package WWW site at http://www.mrc-lmb.cam.ac.uk/pubseq/
>
> _______________________________________________
> Tcl-mac mailing list
> Tc...@li...
> https://lists.sourceforge.net/lists/listinfo/tcl-mac
>
--
Jim Ingham                                   ji...@ap...
Developer Tools - gdb
Apple Computer

[MACTCL] Getting 8.3 to work on OS X.

[Christopher S. M. <mor...@AR...>]

I need a push in the right direction.  I've been spending some time
getting our "house" integration of 8.3.2 (tcl/tk 8.3.2, itcl, iwidgets,
and other mods) to install hitchless on Mac OS X.

I've basically gotten everything to work with one minor exception.  I have
to manually set the environment variables (at least TCL_LIBRARY and
ITCL_LIBRARY) for the tools to work.  They either fail or warn saying that
init.tcl or itcl.tcl (respectively) can't be found, listing the path
searched.  Can someone tell me what file(s) I should be looking at so that
this does not need to happen.  I know that my modifying the source so that
a particular instal path is also searched is not the right solution.  But
I can't seem to figure out how to modify that path properly.

Of particular interest, I notice that /System/Library/Tcl/8.3 is always
listed in the search path (which doesn't exist on my box for other
reasons).  Where is that path getting pulled from?  And, more importantly,
how can I get it to search my install path?

Cheers!

Sean

Re: [MACTCL] Re: tclLoadDyld.c (was: Itcl on MacOSX)

[Daniel A. S. <st...@ic...>]

At 9:59 +0000 on 26/2/02, James Bonfield wrote:
>The Unix based man command works well, but Apple don't seem to have created a
>proper whatis database. Therefore:

you need to run /usr/libexec/makewhatis as root

the /etc/weekly cron job does it for you if your machine is on at Sat 
4:30 am (c.f. /etc/crontab)

>So how exactly am I meant to guess that "man NSModule" is the command to get
>the NSAddImage (and friends) manual pages? I've resorted to using a series of
>greps for most documentation lookups now which works very well, if a bit slow,
>but alternative methods would be gratefully received!

I find that a google search for e.g. "NSAddImage" is often faster & 
more productive than grep -r through my filesystem...

Cheers,

Daniel
-- 
** Daniel A. Steffen          **  "And now to something completely
** Department of Mathematics  **   different"    Monty Python
** Macquarie University       ** <mailto:st...@ma...>
** NSW 2109 Australia         ** <http://www.maths.mq.edu.au/~steffen/>

Re: [MACTCL] Re: tclLoadDyld.c (was: Itcl on MacOSX)

[James B. <jk...@mr...>]

On Tue, Feb 26, 2002 at 04:14:25PM +1100, Daniel A. Steffen wrote:
> man NSModule:
...

On a related note, does anyone know how to get the most of the MacOS X help?
It's help centre is worse than useless, refusing to give me documentation on
things which I know exist.

The Unix based man command works well, but Apple don't seem to have created a
proper whatis database. Therefore:

[mac5031-1:~] jkb% man -k NSAddImage
nsaddimage: nothing appropriate
[mac5031-1:~] jkb% man NSAddImage
man: no entry for NSAddImage in the manual.

So how exactly am I meant to guess that "man NSModule" is the command to get
the NSAddImage (and friends) manual pages? I've resorted to using a series of
greps for most documentation lookups now which works very well, if a bit slow,
but alternative methods would be gratefully received!

Anyway, many thanks for adding the patch Daniel.

James

-- 
James Bonfield (jk...@mr...)   Fax: (+44) 01223 213556
Medical Research Council - Laboratory of Molecular Biology,
Hills Road, Cambridge, CB2 2QH, England.
Also see Staden Package WWW site at http://www.mrc-lmb.cam.ac.uk/pubseq/

Re: [MACTCL] os x command shell from tcl

[Robert C. <ro...@iC...>]

That works! Also, thanks to Jim Ingham for pointing out how to set other
environment variables. I'm well on my way to getting this to work. I'm
working on getting TkMatMan working on OS X using 3Delight.


>Same thing should happen on other systems as well, if I'm not mistaken
>(e.g. linux).  At least same failure happens on my linux boxes.  That's
>because cd is a shell-built-in command for most shells and, more
>importantly (I assume), because thereis not an actual "cd" command (e.g.
>`which cd` returns a not found). Just type 'cd' without the exec and it
>should work just fine. Same with ls, pwd, etc and the rest of the usual
>shell-built-in commands.  Unless I just missed what you were saying
>altogether.. 
>
>Cheers!
>
>
>On Tue, 26 Feb 2002, Robert Coldwell wrote:
>
>> How would one do the "cd" command to the OS X command shell from TCL and
>> get it to work? This is what I put and what I get back:
>> 
>> () 2 % exec cd /bin
>> couldn't execute "cd": no such file or directory
>> 
>> Doing "ls" works fine. It seems to me there is something about keeping
>> the communication open that is not happening. What it seems to do is just
>> "send data" and "retreive data." Any suggestions?
>> 
>> If I can get this to work it will lead into more questions I'm sure.
Thanks.
>> 
>> -- 
>> Robert Coldwell
>

-- 
Robert Coldwell

ro...@iC...
http://iColdwell.com/pixelsplace

Re: [MACTCL] os x command shell from tcl

[Christopher S. M. <mor...@AR...>]

Same thing should happen on other systems as well, if I'm not mistaken
(e.g. linux).  At least same failure happens on my linux boxes.  That's
because cd is a shell-built-in command for most shells and, more
importantly (I assume), because thereis not an actual "cd" command (e.g.
`which cd` returns a not found). Just type 'cd' without the exec and it
should work just fine. Same with ls, pwd, etc and the rest of the usual
shell-built-in commands.  Unless I just missed what you were saying
altogether.. 

Cheers!


On Tue, 26 Feb 2002, Robert Coldwell wrote:

> How would one do the "cd" command to the OS X command shell from TCL and
> get it to work? This is what I put and what I get back:
> 
> () 2 % exec cd /bin
> couldn't execute "cd": no such file or directory
> 
> Doing "ls" works fine. It seems to me there is something about keeping
> the communication open that is not happening. What it seems to do is just
> "send data" and "retreive data." Any suggestions?
> 
> If I can get this to work it will lead into more questions I'm sure. Thanks.
> 
> -- 
> Robert Coldwell

[MACTCL] os x command shell from tcl

[Robert C. <ro...@iC...>]

How would one do the "cd" command to the OS X command shell from TCL and
get it to work? This is what I put and what I get back:

() 2 % exec cd /bin
couldn't execute "cd": no such file or directory

Doing "ls" works fine. It seems to me there is something about keeping
the communication open that is not happening. What it seems to do is just
"send data" and "retreive data." Any suggestions?

If I can get this to work it will lead into more questions I'm sure. Thanks.

-- 
Robert Coldwell

ro...@iC...
http://iColdwell.com/pixelsplace

Re: [MACTCL] Re: tclLoadDyld.c (was: Itcl on MacOSX)

[Daniel A. S. <st...@ic...>]

At 9:47 -0800 on 25/2/02, Jim Ingham wrote:

>  > tests/load.test passes in the 3 branches and [load] now gives an
>>  error message when a file can't be found/loaded and also searches
>  > DYLD_LIBRARY_PATH.
>
>I saw this before, and added a LD_LIBRARY_PATH_VAR to the tcl.m4 which could
>be set to DYLD_LIBRARY_PATH on X to get around this.  Did you have to do
>something else to work around this?

the difference in behaviour is controlled by the 
NSADDIMAGE_OPTION_WITH_SEARCHING flag to NSAddImage. without it 
NSAddImage only tries to load the file it was given the path to, with 
it also searches through the standard dyld library directories & 
DYLD_LIBRARY_PATH etc:

man NSModule:

        The other options of NSAddImage are as follows:

        NSADDIMAGE_OPTION_WITH_SEARCHING
               With this option  the  image_name  passed  for  the
               library  and all its dependents will be effected [sic] by
               the various DYLD environment variables as  if  this
               library were linked into the program.

Cheers,

Daniel
-- 
** Daniel A. Steffen          **  "And now to something completely
** Department of Mathematics  **   different"    Monty Python
** Macquarie University       ** <mailto:st...@ma...>
** NSW 2109 Australia         ** <http://www.maths.mq.edu.au/~steffen/>

[MACTCL] Re: tclLoadDyld.c (was: Itcl on MacOSX)

[Daniel A. S. <st...@ic...>]

Jim,

sorry for the delay

At 10:42 -0800 on 15/2/02, Jim Ingham wrote:

>So check it into the head.  You can check stuff into the 
>macosx-8-4-branch too, right?

yes, the tclLoadDyld.c patch (adapted for 8.4 vfs apis where 
necessary) is now checked into the HEAD, core-8-3-1-branch and 
macosx-8-4-branch

I've also checked an older change of mine to the HEAD into 
macosx-8-4-branch (doesn't seem to have made it through your join):
in tcl.m4 & configure, SHLIB_LD_LIBS needs to be set to '${LIBS}', 
otherwise make fails in unix/dltest.

tests/load.test passes in the 3 branches and [load] now gives an 
error message when a file can't be found/loaded and also searches 
DYLD_LIBRARY_PATH.

Cheers,

Daniel
-- 
** Daniel A. Steffen          **  "And now to something completely
** Department of Mathematics  **   different"    Monty Python
** Macquarie University       ** <mailto:st...@ma...>
** NSW 2109 Australia         ** <http://www.maths.mq.edu.au/~steffen/>