Re: [MACTCL] Compiling extensions

[Daniel A. S. <da...@us...>]

At 14:09 +1100 on 8/3/01, Daniel A. Steffen wrote:

>this is the scriptics sample extension from 
>ftp://ftp.ajubasolutions.com//pub/tcl/examples/tea/SampleTclExtension.tar.SIT.hqx
>you're referring to, correct?
>
>I'll try to update it to Pro6 and post it somewhere ASAP

I've had a go at this, you can get it from

http://www.maths.mq.edu.au/~steffen/tcltk/Mac_sampleextension-0.2.1.bin

Please test and let me know if this works for you.


 From "README-MacSample":

Quick notes for 0.2.1:

* I've included an xml export of the Pro6 project, Pro5 seems to be able to
   import it and not loose access paths in the process (which is what
   happens when opening the Pro6 project in Pro5 :-( )

   Note that on Pro5 you have to add
   "{Project}:::(Pro6 Build Support):Runtime Libraries:"
   to System Access Paths ABOVE
   "{Compiler}:MacOS Support"

* I've added a Merge target which produces the final ExampleA.shlb
   extension, it merges the PPC and the CFM68k shared libraries, this allows
   for a unique binary and "package ifneeded" statement on both platforms.
   As a consequence however, the unmerged ExampleAPPC.shlb and
   ExampleACFM68K.shlb files will not load without changing their pkgIndex
   resource.

* At the moment the extension uses an .exp file to specify what symbols to
   export from its shared library, the #pragma export approach never worked
   well for me (exports too may symbols, e.g. TclStub.lib symbols).

   However, with my current patches for 8.4 TOT (which I'll hopefully get
   around to backport in time for 8.3.3), the standard Tcl DLLEXPORT macros
   now work on Mac as well, so be sure to use standard Tcl EXTERN
   declarations for symbols you want exported (i.e. for extensions, this is
   in general only your _Init (and _SafeInit if you have one) routine, see
   the Examplea_Init declaration in exampleA.h), that way you'll be able to
   switch to the "#pragma export" method and remove the .exp file with
   minimal effort in the future.


Cheers,

Daniel

-- 
** Daniel A. Steffen                  **
** <mailto:da...@us...> **