From: Kevin Walzer <sw@wo...> - 2005-07-25 14:37:28
-----BEGIN PGP SIGNED MESSAGE-----
I'm trying to reduce the size of my applications while still maintaining
convenience for end users. My plan is to start using my own build of the
TkAqua standalone bundle (Wish with the frameworks installed) and also
build/bundle only the extensions that aren't available on Tiger.
My question is this: if I call an extension that is pre-installed on
Tiger (i.e. Tk Image, TclApplescript, or tcllib) from a TkAqua
standalone that's built from CVS Head, will my build of Wish see it? Is
/System/Library/Tcl one of the default search paths for extensions on
Tiger? Or do packages need to be built against the same version of
Tcl/Tk (8.4.7 on Tiger if I recall correctly) to be visible?
My reason for asking is that this is a problem with Python--extensions
linked against Python 2.4.1 cannot be seen by Tiger's system
installation of Python (2.3.5). I hope the case is different with TkAqua.
Thanks for clarifying.
Kevin Walzer, PhD
WordTech Software--Open Source Applications and Packages for OS X
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
On Mon, 25 Jul 2005, Kevin Walzer wrote:
> My reason for asking is that this is a problem with Python--extensions
> linked against Python 2.4.1 cannot be seen by Tiger's system
> installation of Python (2.3.5). I hope the case is different with TkAqua.
Is Python very strict about matching versions? Doesn't have a stub
In any case, you are likely to have only very few problems, if any. Just
make sure the extension path is in the auto_path list variable or in the
TCLLIBPATH environment variable.
On 25 July 2005 15:37, Kevin Walzer wrote:
> My question is this: if I call an extension that is pre-
> installed on Tiger (i.e. Tk Image, TclApplescript, or tcllib)=20
> from a TkAqua standalone that's built from CVS Head, will my=20
> build of Wish see it?=20
Yes, there is some magic - the "stubs" mechanism - that in principle
releases extensions from dependence on a particular version of Tcl/Tk
libraries. (Of course, some extensions don't work with some versions
because of the functionality they require, but that's not a linker =
> Is /System/Library/Tcl one of the default search paths for=20
> extensions on Tiger?=20
Probably; if it isn't, simply lappend it to the auto_path variable.
Of course, this isn't much help to any user who hasn't upgraded to 10.4.