Version 12 of Converting your Tcl extension to TEA2

Purpose:

Provide a developer with tips, suggestions and warnings regarding implementing a Tcl extension using the TEA 2000 guidelines.

Why bother?
Where is TEA2 documented?
What needs to be done to move a TEA1 extension to TEA2?
What needs to be done to move a non-TEA extension to TEA2?
What tools are available to help with TEA2?
What do you do when TEA2 changes or is fixed? Can you update your extension automatically?
On what platforms can one use TEA2 - does it work on MacOS, MacOS X, VMS, Unix, Windows, etc.?
Can it build/install into paths containing spaces, e.g. C:/Program Files ?
On Microsoft Windows, does the Mingw 3.x based compilers work with TEA2?

What tools are available to help with TEA2?

In a c.l.t. posting [L1 ] Donal Fellows mentioned teapot [L2 ], the TEA extension help mate a script helping to create the configure.in , aclocal.m4 and Makefile.in for a TEA2 compliant extension.

Can it build/install into paths containing spaces?

Yes it can, but the paths have to be quoted correctly and some peculiarities may happen. To install in C:/Program Files one has to invoke configure like this:

 ./configure --prefix="C:/Program\ Files"

Configure seems to look for a site script in C:/Program\ which is obviously incorrect, but has no negative consequences if no site script is used.

[ Category Porting | ]