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

Re: [MACTCL] Bugs in Tclapplescript.shlb

[Bernard D. <bde...@ea...>]

Jim Ingham wrote:

> On 3/12/02 12:31 PM, "Bernard Desgraupes   (by way of Jon Guyer)"
> <bde...@ea...> wrote:
>
>
> > Here are the two problems
> > 1-  this is with the "AppleScript execute" command. When the first
> > two characters of your
> > script are a comment sign (double dash) the interpreter gets confused
> > and thinks it is an
> > option : it sends an error message :
> > "Error, no value given for switch etc," followed by the entire text
> > of your script.
> > To avoid this, the code for the tclOSAExecuteCmd (in tclMacOSA.c)
> > should be made more
> > robust. To tell the truth I don't really see the necessity of a check
> > for an "--" option
> > since this command doesn't have any switch.
>
> Yes it does, it takes the -context switch.  You can say:
>
> AppleScript execute -context contextToken <Some Script Data>
>

Oh, that's right, sorry, I was too quick.
There still is this risk of a clash between "--" as a switch and "--" as a comment sign at
the beginning of an AppleScript script.
This means that we should _always_ use the -- switch in "AppleScript execute" to be safe.

Cheers

Bernard

[MACTCL] Can't find install directory properly on OS X.

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

My apologies if this is an answered question (couldn't find it in
archives), but I'm having difficulty getting 8.3.2 to find itself properly
after installation.  I have similar problems for everything else
thereafter (tk, itcl, itk, iwidgets).  

The quick fix is to set the corresponding XXXX_LIBRARY environment
variable to the packages find what they need, and all is good.  But that
doesn't fix the problem, it quells the symptom.  How does
/System/Library/Tcl/8.3 get into that search path and how can I go about
to get that to be based off --prefix's value. 

There is a little oddity of the Makefile getting modified (necessarily on
other platforms) prior to building.  The details are included below.  Any
help is appreciated. 

As a side note, I have to use 8.3.2 for this release, unfortunately.
Then I'll be upgrading it to newer tcl/tk sources.  A short-term fix to
get this version working would be nice, though.



Here is the error message:

bash2.04 sean@dhcp-32-233 ~/brlcad6/.libtcl8.3.pmac % tclsh
application-specific initialization failed: Can't find a usable init.tcl
in the following directories: 
    /System/Library/Tcl/8.3 /usr/brlcad/lib/tcl8.3 /usr/lib/tcl8.3
/usr/lib/tcl8.3/library /usr/library /usr/tcl8.3/library /tcl8.3/library
/System/Library/Tcl/8.3


This probably means that Tcl wasn't installed properly.



Here is the initial build:

( CFLAGS=" -O3  -fno-common -ffast-math -fstrength-reduce
-fexpensive-optimizations "; AFTER_MAKE="rm -f libtcl.a ; ln -s
libtcl8.3.a libtcl.a"; RANLIB="ranlib -c"; LDFLAGS="-O3  -fno-common
-ffast-math -fstrength-reduce -fexpensive-optimizations  ";
BUILD_LIBRARY="ar r"; CC="cc"; export CFLAGS RANLIB LDFLAGS BUILD_LIBRARY
CC AFTER_MAKE; ../libtcl8.3/"unix"/configure
--srcdir=/Users/sean/brlcad6/.libtcl8.3.pmac/../libtcl8.3/"unix" --quiet
--cache-file cache.pmac --exec-prefix=/usr/brlcad --prefix=/usr/brlcad
--disable-shared; ../libtcl8.3/fix_makefile.sh > Makefile.pmac)
creating cache cache.pmac
Can't figure out how to do dynamic loading or shared libraries
on this system.
updating cache cache.pmac
creating ./config.status
creating Makefile
creating tclConfig.sh
make -f Makefile.pmac tclsh
cc -c -O3  -fno-common -ffast-math -fstrength-reduce
-fexpensive-optimizations  -Wall -Wconversion -Wno-implicit-int
-I/Users/sean/brlcad6/.libtcl8.3.pmac/../libtcl8.3/unix/../generic
-I/Users/sean/brlcad6/.libtcl8.3.pmac/../libtcl8.3/unix -DHAVE_UNISTD_H=1
-DHAVE_LIMITS_H=1 -DHAVE_GETCWD=1 -DHAVE_OPENDIR=1 -DHAVE_STRSTR=1
-DHAVE_STRTOL=1 -DHAVE_TMPNAM=1 -DHAVE_WAITPID=1 -DNO_VALUES_H=1
-DNO_DLFCN_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYS_PARAM_H=1 -DUSE_TERMIOS=1
-DHAVE_SYS_TIME_H=1 -DTIME_WITH_SYS_TIME=1 -DHAVE_TM_ZONE=1
-DHAVE_TM_GMTOFF=1 -DHAVE_ST_BLKSIZE=1 -DSTDC_HEADERS=1 -DNEED_MATHERR=1
-DHAVE_SIGNED_CHAR=1 -DHAVE_SYS_IOCTL_H=1 -DHAVE_SYS_FILIO_H=1
-DSTATIC_BUILD=1         -DTCL_SHLIB_EXT=\"\"
/Users/sean/brlcad6/.libtcl8.3.pmac/../libtcl8.3/unix/../unix/tclAppInit.c
.
.
.



The fix_makefile.sh file looks like this:
bash2.04 sean@dhcp-32-233 ~/brlcad6/.libtcl8.3.pmac % less ../libtcl8.3/fix_makefile.sh 
#!/bin/sh

sed -e s@lib/tcl\$\(VERSION\)@tcl\$\(VERSION\)@ Makefile |\
         sed -e s@\(prefix\)/include@\(prefix\)/include/brlcad@ |\
         sed -e "s@\${\C\C}  \${TCLSH_OBJS}@\${\C\C} $LDFLAGS \${TCLSH_OBJS}@" |\
         sed -e "s@\${\C\C}  \${TCLTEST_OBJS}@\${\C\C} $LDFLAGS \${TCLTEST_OBJS}@"




Resulting in the following diff in the Makefile:

bash2.04 sean@dhcp-32-233 ~/brlcad6/.libtcl8.3.pmac % diff Makefile.pmac
Makefile
42c42
< TCL_LIBRARY           = $(prefix)/tcl$(VERSION)
---
> TCL_LIBRARY           = $(prefix)/lib/tcl$(VERSION)
432c432
<       ${CC} -O3  -fno-common -ffast-math -fstrength-reduce -fexpensive-optimizations   ${TCLSH_OBJS} -L/Users/sean/brlcad6/.libtcl8.3.pmac -ltcl8.3${TCL_DBGX} ${LIBS} \ 
---
>       ${CC}  ${TCLSH_OBJS} -L/Users/sean/brlcad6/.libtcl8.3.pmac -ltcl8.3${TCL_DBGX} ${LIBS} \
436c436
<       ${CC} -O3  -fno-common -ffast-math -fstrength-reduce -fexpensive-optimizations   ${TCLTEST_OBJS} -L/Users/sean/brlcad6/.libtcl8.3.pmac -ltcl8.3${TCL_DBGX} ${LIBS} \ 
---
>       ${CC}  ${TCLTEST_OBJS} -L/Users/sean/brlcad6/.libtcl8.3.pmac -ltcl8.3${TCL_DBGX} ${LIBS} \


Cheers!

Sean

Re: [MACTCL] Bugs in Tclapplescript.shlb

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

On 3/12/02 12:31 PM, "Bernard Desgraupes   (by way of Jon Guyer)"
<bde...@ea...> wrote:

> [Originally reported to alphatcl-developers]:
> 
> 
> Hello,
> 
> I'm currently developping an AppleScript Menu and enhancing the
> AppleScript mode for
> Alpha8 : everything goes fine except for two problems (a bug and a
> mistake) I have found
> in the Tclapplescript shared library. I'm not sure if this is the
> right place to report
> them, so I'll mention them here and please forward them or tell me
> whom I should send them
> to.
> 

This is the right place...

> Here are the two problems
> 1-  this is with the "AppleScript execute" command. When the first
> two characters of your
> script are a comment sign (double dash) the interpreter gets confused
> and thinks it is an
> option : it sends an error message :
> "Error, no value given for switch etc," followed by the entire text
> of your script.
> To avoid this, the code for the tclOSAExecuteCmd (in tclMacOSA.c)
> should be made more
> robust. To tell the truth I don't really see the necessity of a check
> for an "--" option
> since this command doesn't have any switch.

Yes it does, it takes the -context switch.  You can say:

AppleScript execute -context contextToken <Some Script Data>

And then the script will get executed in the context represented by
contextToken.  So the -- is necessary.  I guess we could be a little
fancier, and if there is ONLY one argument, then assume that that is script
data.  Tcl doesn't usually do this sort of second-guessing, however...

> Anyway, as a temporary and very simple workaround in my Tcl code, I
> have inserted a blank
> space at the beginning of the text of the script I transmit to
> "AppleScript execute" :
> proc Scrp::doExecute {text} {
>    AppleScript execute " $text"
> }
> 
> 2- Not really a bug, just a mistake in the doc. It says that the
> syntax to delete a
> context is
>    AppleScript delete scriptName
> 
> This is not true. The syntax must be
>    AppleScript delete what scriptName
> 
> where 'what' is either "context" or "script".
> 

Thanks.

Jim 
-- 
++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=++=
Jim Ingham                              ji...@ap...
Developer Tools - gdb

Re: [MACTCL] resources and environment variables

[Jack J. <Jac...@or...>]

On dinsdag, maart 12, 2002, at 07:21 , macnerd wrote:

> I was taking a look at MacPerl, and in their preferences, they
> maintain preferences for Libraries, Environment variables.
>
> However, I thought of something better, and I wanted to see
> what people think.  How about creating a tool, or modifying
> Internet Config, that will maintain Library and Environment
> variables for all programs that would ike to use a similar
> facility.

The question is: is it worth it? You would be investing work 
into an operating system that (a) never needed environment 
variables and (b) is on the way out anyway.

It's a much better idea (IMNSHO) to invest in opening up 
CFPreferences. That's a very nice preferences mechanism with 
inheritance and all, much better than what environment vars will 
ever give you.
--
- Jack Jansen        <Jac...@or...>        
http://www.cwi.nl/~jack -
- If I can't dance I don't want to be part of your revolution -- 
Emma Goldman -

Re: [MACTCL] BUILD: tcl8.3.4, WodeWarrior 4.1, TclShells.<PI>, sh*SimpleTcl

[Jon G. <jg...@hi...>]

At 9:00 PM +0100 3/12/02, Andreas Otto wrote:

>	the link fails, what I have to do ?

Provide more information about what you're building with... and keep 
it on the list, please.

-- 


   Jonathan E. Guyer
   <http://www.his.com/jguyer/>

[MACTCL] Bugs in Tclapplescript.shlb

[Bernard D. <bde...@ea...>]

[Originally reported to alphatcl-developers]:


Hello,

I'm currently developping an AppleScript Menu and enhancing the 
AppleScript mode for
Alpha8 : everything goes fine except for two problems (a bug and a 
mistake) I have found
in the Tclapplescript shared library. I'm not sure if this is the 
right place to report
them, so I'll mention them here and please forward them or tell me 
whom I should send them
to.

Here are the two problems
1-  this is with the "AppleScript execute" command. When the first 
two characters of your
script are a comment sign (double dash) the interpreter gets confused 
and thinks it is an
option : it sends an error message :
"Error, no value given for switch etc," followed by the entire text 
of your script.
To avoid this, the code for the tclOSAExecuteCmd (in tclMacOSA.c) 
should be made more
robust. To tell the truth I don't really see the necessity of a check 
for an "--" option
since this command doesn't have any switch.
Anyway, as a temporary and very simple workaround in my Tcl code, I 
have inserted a blank
space at the beginning of the text of the script I transmit to 
"AppleScript execute" :
proc Scrp::doExecute {text} {
     AppleScript execute " $text"
}

2- Not really a bug, just a mistake in the doc. It says that the 
syntax to delete a
context is
     AppleScript delete scriptName

This is not true. The syntax must be
     AppleScript delete what scriptName

where 'what' is either "context" or "script".

Cheers

Bernard


BTW this AppleScript Menu will help solving several problems of 
interapplication
communication when the Apple Events syntax is not available.






_______________________________________________
AlphaTcl-developers mailing list
Alp...@li...
https://lists.sourceforge.net/lists/listinfo/alphatcl-developers

RE: [MACTCL] How-to Changing Type/Creator?

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

Do you mean ResEdit? RegEdit is for Windows.

That information is in the resources as BNDL for
applications and determining what applications support.

The actual TYPE/CREATOR is not in the resource, but 
actually apart of Finder Info, which can be found in 
Get Finder Info... menu item under the File menu.

Also, Greg's Browser has these options available as 
well.

ciao, 
 Joaquin

> -----Original Message-----
> From: tcl...@li...
> [mailto:tcl...@li...]On Behalf Of Andreas Otto
> Sent: Tuesday, March 12, 2002 11:44 AM
> To: Jon Guyer; tc...@li...
> Subject: Re: [MACTCL] How-to Changing Type/Creator?
> 
> 
> Hi,
> 
>  I donload "RegEdit" which should do the job but I don't know how
>  to find the Creator resource
> 
> 
> mfg
> 
>   aotto :)
> 
> _______________________________________________
> Tcl-mac mailing list
> Tc...@li...
> https://lists.sourceforge.net/lists/listinfo/tcl-mac
> 

[MACTCL] Environment Variables, the Mac Way

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

I thought of a down and dirty idea that is totally Mac-like.  If we do =
an Environment
interface I would like to share it amongst Perl and Python users, and =
get them to=20
buy into it.

The ol' System stores everything in the System Folder.  This includes =
Preferences
and Extensions as well as Control Panels.

The MacPerl folks have store environment variables inside a preference =
file inside
the System folder, more specifically {System Preferences}:"MacPerl 5 =
Preferences",=20
where System Preferences refers to the "blessed" or active running =
System folder.

Inside the preferences there are some resources (PFNT, PPRF, STR#, and =
TFSS).=20
There is one string of ID #129, which simply store the environment =
variables like=20
this:

  USER=3D
  TMPDIR=3DClassical:Temporary Items:

*Classical is my drive name

When I ran DeRez in MPW I got

   data 'STR#' (129) {
      $"0002 0555 5345 523D 2154 4D50 4449 523D"            /* =
...USER=3D!TMPDIR=3D */
	$"436C 6173 7369 6361 6C3A 5465 6D70 6F72"            /* =
Classical:Tempor */
      $"6172 7920 4974 656D 733A"                           /* ary =
Items: */
   };=20

I was thinking that maybe we can create a preference file and simply =
call it
ENVIRONMENT, which would then include these strings in a similar =
pattern.

Does this sound good?

Re: [MACTCL] How-to Changing Type/Creator?

[Jon G. <jg...@hi...>]

At 8:43 PM +0100 3/12/02, Andreas Otto wrote:

>  I donload "RegEdit"

You mean ResEdit, I assume?

>  which should do the job but I don't know how
>  to find the Creator resource

The type and creator are not resources. They are file system 
meta-data. With ResEdit, you can manipulate them with File -> Get 
Info for ...
-- 


   Jonathan E. Guyer
   <http://www.his.com/jguyer/>

[MACTCL] How define TCLLIBRARY

[<AO...@t-...>]

Hi,

 If I have packages in Tcl which resist in some folders which are
 not known to Tcl.

 In Unix/Win I use the environment variable TCLLIBRARY
 to tell Tcl where to look for additional packages

 how I can tell Tcl to use some special folders as sources for
 Tck packages on MacOS ?




mfg

  aotto :)

Re: [MACTCL] How-to Changing Type/Creator?

[<AO...@t-...>]

Hi,

 I donload "RegEdit" which should do the job but I don't know how
 to find the Creator resource


mfg

  aotto :)

RE: [MACTCL] How-to Changing Type/Creator?

[Jon G. <jg...@hi...>]

At 10:30 AM -0800 3/12/02, macnerd wrote:
>Thanks.  Will these work on Mac OS 7.5.x?

No. They're Mac OS X tools.

-- 


   Jonathan E. Guyer
   <http://www.his.com/jguyer/>

RE: [MACTCL] How-to Changing Type/Creator?

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

Thanks.  Will these work on Mac OS 7.5.x?

> -----Original Message-----
> From: tcl...@li...
> [mailto:tcl...@li...]On Behalf Of Jon Guyer
> Sent: Tuesday, March 12, 2002 7:32 AM
> To: tc...@li...
> Subject: Re: [MACTCL] How-to Changing Type/Creator?
> 
> 
> At 10:31 AM +0100 3/12/02, Andreas Otto wrote:
> 
> >   how I get the DeveloperTool CD
> 
> <http://developer.apple.com/tools/macosxtools.html>
> 
> -- 
> 
> 
>    Jonathan E. Guyer
>    <http://www.his.com/jguyer/>
> 
> 
> _______________________________________________
> Tcl-mac mailing list
> Tc...@li...
> https://lists.sourceforge.net/lists/listinfo/tcl-mac
> 

RE: [MACTCL] resources and environment variables

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

I was taking a look at MacPerl, and in their preferences, they
maintain preferences for Libraries, Environment variables.

However, I thought of something better, and I wanted to see
what people think.  How about creating a tool, or modifying
Internet Config, that will maintain Library and Environment
variables for all programs that would ike to use a similar
facility.

All script environments and other programs can plug-in to
this interface and share environment variables.  This is 
similar to how Internet Config is used amongst internet
applications.  I would recomend adding a tab for Environment
variables for Internet Config, as this was originally
open source anyhow.

As for paramateres and STDIN, this can be done either 
through supporting standard apple events.  We can get
other scripts to support these apple events as well, 
so that way one program can pipe to another.

I would be curious is MPW supports some sort of 
facility for this.  I will look into MPW.  As MPW
supports tools and a CLI environment, I wonder if 
they support high level AppleEvents to call a tool
and pass parameters or pipe STDIN.  If MPW does, 
we can simply support the same type of AppleEvents
to have consistancy and get other groups to buy
into this.

 

> -----Original Message-----
> From: tcl...@li...
> [mailto:tcl...@li...]On Behalf Of Andreas Otto
> Sent: Tuesday, March 12, 2002 9:23 AM
> To: tc...@li...
> Subject: [MACTCL] resources and environment variables
> 
> 
> 
> 
> Hi,
> 
>  to get "Compiler" working on MacOs 9.1 some environment variables
>  are necessary.
> 
>  example COMPILER_HOME
> 
>  this points to the installation Folder of the "Compiler"
> 
>  in Tcl you can do "set env(COMPILER_HOME) ...."
> 
>  thats ok.
> 
>  My idea is setting a TEXT resourse to the Tcl
>  executable
> 
>  like it was done with the "tclshrc" resource for
>  every tcl like application and put the value
>  of "COMPILER_HOME" into the resource
> 
>  1) is this possible ?
>  2) can I patch a new value into the application resource
>      without breaking the executable using some kind of
>      Filter technology
> 
>      I use this technology called "active patching" on
>      UNIX and WIN very successful and I think this
>      would work for Mac too
> 
> 
> 
> 
> mfg
> 
>   aotto :)
> 
> _______________________________________________
> Tcl-mac mailing list
> Tc...@li...
> https://lists.sourceforge.net/lists/listinfo/tcl-mac
> 

Re: [MACTCL] exec on mac

[Jon G. <jg...@hi...>]

At 6:07 PM +0100 3/12/02, Andreas Otto wrote:

>  How does is get any information from the caller
>  to the called executable
>
>  there have to be any useable way to do it		??

AppleEvents, AppleEvents, AppleEvents, AppleEvents, AppleEvents, AppleEvents

-- 


   Jonathan E. Guyer
   <http://www.his.com/jguyer/>

Re: [MACTCL] OS9/OSX apps

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

Peter,

I used the Carbon libraries to port the MacOS 9 code to Mac OS X, but I 
did not attempt to Carbonize the MacOS 9 version.  And I didn't make any 
attempt to restrict myself to the subset of Carbon that is supported on 
9 for the X port.  So you can't recompile the AquaTk codebase to run on 
9...

However, you can package up a 9 & a X binary in the same App wrapper, 
and I don't think (though I have never tried) that the 9 version has to 
be a Carbon app for this to work.  The System Overview document has more 
details on this.  If this is true, then the remaining problems are how 
to find any extensions you have, and how to find where you have stashed 
away your Tcl scripts.  If you stuff everything into the App package, 
the bundle API's can be used on X to find things.  I don't think you can 
use these on 9 'cause Tk is not carbonized.  But you could hard-code the 
relative paths to find things for now there.

Jim


On Tuesday, March 12, 2002, at 09:10  AM, Peter Nye wrote:

> Hello,
>
> Does anyone know how to run Tk apps build as OSX projects in OS9?  
> Since it's carbonized, this should theoretically be possible.
>
> -- Peter Nye
>
> _______________________________________________
> Tcl-mac mailing list
> Tc...@li...
> https://lists.sourceforge.net/lists/listinfo/tcl-mac
>
--
Jim Ingham                                   ji...@ap...
Developer Tools - gdb
Apple Computer

Re: [MACTCL] BUG: file join ?

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

No, this is a relative path.  Absolute paths on the Mac look like:

My Disk:Documents:My File

Tcl has to do some fancy footwork with paths to try to get this right.  
Basically, if we see a path without any colons, we assume it is 
relative, and just a single file name.  If it has any colons at all, 
then if it begins with a colon, it is relative, and otherwise it is 
absolute.  There is some added complexity because we try to also handle 
"unix-looking" paths, but this is how the Mac part works.

Jim

On Tuesday, March 12, 2002, at 12:01  AM, Andreas Otto wrote:

>
>
> Hi,
>
>> file join a b
>> :a:b
>
> this is an absolut path name not relative
>
> I'm right ?
>
> mfg
>
>   aotto
>
> _______________________________________________
> Tcl-mac mailing list
> Tc...@li...
> https://lists.sourceforge.net/lists/listinfo/tcl-mac
>
--
Jim Ingham                                   ji...@ap...
Developer Tools - gdb
Apple Computer

Re: [MACTCL] exec on mac

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

On Monday, March 11, 2002, at 11:12  PM, Andreas Otto wrote:

> Am Montag 11 M=E4rz 2002 17:23 schrieben Sie:
>> At 3:16 PM +0100 3/11/02, Andreas Otto wrote:
>>>  there have to be a way to call additional executables from
>>>  a Tcl script
>>
>> and there is... just not the Tcl norm.
>
> Hi,
>
>  are examples available ...
>
> from main
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> void
> main(
>     int argc,                           /* Number of arguments. */
>     char **argv)                        /* Array of argument strings. =
*/
> {
>     char *newArgv[2];
>
>     if (MacintoshInit()  !=3D TCL_OK) {
>         Tcl_Exit(1);
>     }
>
>     argc =3D 1;
>     newArgv[0] =3D "tclsh";
>     newArgv[1] =3D NULL;
>     Tcl_Main(argc, newArgv, Tcl_AppInit);
> }
> <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
>
> why does tcl blow away the argv array ?

There is no way to start up a Macintosh executable and pass it an argc,=20=

argv.  So the argv will ALWAYS be empty.  But the rest of Tcl is unhappy=20=

with having nothing in the argv array, so we put this minimal entry into=20=

it.

Jim

>
>
>
>>
>>>  I need the channel output back into a string
>>>
>>>  I have an additional API for calling external SW ->
>>>  does Applescript helps ?
>>
>> Sure AppleScript/Tclapplescript is one option. My TclAE
>
> Is a download path available ?
>
>
>  is another.
>> In either case, you can get a reply, assuming the external app sends
>> one, but it's really not the same as the channel output you are
>> probably expecting.
>>
>>>  does "open |..." works ?
>>
>> Mac OS 9? No. No pipes.
>>
>>>  1) is a commandline interface available
>>>
>>>   cammandline + some kind of exec would be perfect
>>
>> Neither of these things really exist on Classic Mac. CodeWarrior
>> provides for a limited command-line interface in your apps (look for
>> docs on SIOUX and ccommand()). If you want your app to execute other
>> apps, you'll need to do it with AppleEvents. Tell us more about
>> exactly what you'd like to do and we can tell you more about how to
>> accomplish it.
>
> Hi,
>
>   the current strategic decision would be using the xml interface of
>  code-warrior. Yo can create a Code warrior project as xml file and
>  import it into the gui.
>
>  One help would be not only to cretae the xml files, it should be=20
> possible
>  to call code-warrior to do the compiling and linking themself without
>  using the user-interface. If this is possible it would be a big step=20=

> in the
>  right direction.
>
>
>>
>>>  2) is a cross compiler linux -> macOs9.1 ppc available
>>>    gcc does not support MacOs9.1 (this speak for them-
>>>    self) perhaps CodeWarrior ???
>>
>> CodeWarrior has a linux variant. I've never used it and don't know
>> what it's cross-compilation options are.
>
> _______________________________________________
> Tcl-mac mailing list
> Tc...@li...
> https://lists.sourceforge.net/lists/listinfo/tcl-mac
>
--
Jim Ingham                                   ji...@ap...
Developer Tools - gdb
Apple Computer

[MACTCL] resources and environment variables

[<AO...@t-...>]

Hi,

 to get "Compiler" working on MacOs 9.1 some environment variables
 are necessary.

 example COMPILER_HOME

 this points to the installation Folder of the "Compiler"

 in Tcl you can do "set env(COMPILER_HOME) ...."

 thats ok.

 My idea is setting a TEXT resourse to the Tcl
 executable

 like it was done with the "tclshrc" resource for
 every tcl like application and put the value
 of "COMPILER_HOME" into the resource

 1) is this possible ?
 2) can I patch a new value into the application resource
     without breaking the executable using some kind of
     Filter technology

     I use this technology called "active patching" on
     UNIX and WIN very successful and I think this
     would work for Mac too




mfg

  aotto :)

Re: [MACTCL] exec on mac

[<AO...@t-...>]

Hi,

 one thing I don't understand  ..)

 MacOs has the "exec" libc call .. 		OK
 MacOs does not support commandline-args 	KO
 MacOs does not support env arguments		KO

 How does is get any information from the caller
 to the called executable

 there have to be any useable way to do it		??


mfg

  aotto :)

Re: [MACTCL] BUILD: tcl8.3.4, WodeWarrior 4.1, TclShells.<PI>, sh*SimpleTcl

[<AO...@t-...>]

Am Dienstag 12 März 2002 17:06 schrieb Jon Guyer:
> At 1:59 PM +0100 3/12/02, Andreas Otto wrote:
> >  in the file "tclMacAppInit.c"
> >
> >
> >#elif defined(__MWERKS__)
> >#   include <SIOUX.h>
> >EXTERN short InstallConsole _ANSI_ARGS_((short fd));
> >#endif
> ><<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
> >
> >   the extern procedure "InstallConsole" was *not* defined in <SIOUX.h>
>
> No, it's not. That's why this EXTERN declaration is there.
>
> >   and the compilation failed
>
> The compilation failed or the link?

Hi,

  the link


mfg

 aotto :)

[MACTCL] OS9/OSX apps

[Peter N. <pe...@pi...>]

Hello,

Does anyone know how to run Tk apps build as OSX projects in OS9?  Since it's carbonized, this should theoretically be possible.

-- Peter Nye

Re: [MACTCL] BUILD: tcl8.3.4, WodeWarrior 4.1, TclShells.<PI>, sh*SimpleTcl

[Jon G. <jg...@hi...>]

At 1:59 PM +0100 3/12/02, Andreas Otto wrote:

>  in the file "tclMacAppInit.c"
>
>  >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>#elif defined(__MWERKS__)
>#   include <SIOUX.h>
>EXTERN short InstallConsole _ANSI_ARGS_((short fd));
>#endif
><<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
>
>   the extern procedure "InstallConsole" was *not* defined in <SIOUX.h>

No, it's not. That's why this EXTERN declaration is there.

>   and the compilation failed

The compilation failed or the link?

-- 


   Jonathan E. Guyer
   <http://www.his.com/jguyer/>

Re: [MACTCL] exec on mac

[Jon G. <jg...@hi...>]

At 8:12 AM +0100 3/12/02, Andreas Otto wrote:

>  are examples available ...

Generally, look for AppleScripting examples in the app you wish to 
call. Once you know how it can be scripted, you should be able to 
call TclAppleScript trivially. There may be reasons, depending on the 
nature of communication, why you'll want to go to the additional 
trouble of using my TclAE. One reason is that many apps support 
AppleEvents for which they have not provided an AppleScript 
interface. /If/ you can find documentation of those AppleEvents, then 
TclAE is pretty much your only option for exploiting them.

>why does tcl blow away the argv array ?

Because it is never meaningful in a Mac application. A Mac 
application cannot be launched from the command-line because there is 
no command-line so there can't be any command-line arguments. You can 
use MPW or tclsh or Alpha or any number of other tools to emulate a 
command-line on a Mac, but you cannot change the underlying truth 
that the Mac does not have and does not understand this mode of doing 
things.

>  > Sure AppleScript/Tclapplescript is one option. My TclAE
>
>Is a download path available ?

TclAppleScript is included with the standard Mac Tcl distribution: 
[package require Tclapplescript].

TclAE is presently documented at 
<http://www.his.com/jguyer/Alpha/TclAE%20Help/>. I don't recommend 
you download that library, as it's rather old. I should be uploading 
a current version soon to <http://sourceforge.net/projects/tclae/>. I 
will post here when that happens.

>  One help would be not only to cretae the xml files, it should be possible
>  to call code-warrior to do the compiling and linking themself without
>  using the user-interface. If this is possible it would be a big step in the
>  right direction.

The CW IDE has extensive support for AppleScript and general 
AppleEvents. I don't have my CW docs handy, but if you look through 
the manuals for the IDE, you should find it. Instructing the IDE to 
compile and link is certainly feasible.

-- 


   Jonathan E. Guyer
   <http://www.his.com/jguyer/>

Re: [MACTCL] How-to Changing Type/Creator?

[Jon G. <jg...@hi...>]

At 10:31 AM +0100 3/12/02, Andreas Otto wrote:

>   how I get the DeveloperTool CD

<http://developer.apple.com/tools/macosxtools.html>

-- 


   Jonathan E. Guyer
   <http://www.his.com/jguyer/>