Re: version conflict for package "Tcl": TCL_VERSION vs TCL_PATCH_LEVEL

Neil Madden <nem@xxxxxxxxxxxxx>:

That's what the stubs mechanism is for -- maintains forward and backward
binary compatibility. For instance, you can link against the 8.5 stub
lib and then load the resulting extension into an 8.4 interpreter fine
(so long as you don't need specific 8.5 APIs, of course). Likewise an
extension linked against the 8.4 stub lib should load into an 8.5 interp
no problem.

Yes, however, I want to provide a version without stubs support (in
addition to the recommended stubs version).

(The reason for the no-stubs version is that building the stubs
version can sometimes cause additional problems; see e.g.
the thread next door about the build problems of a stubs-enabled
extension with lcc-win32 and ActiveTcl).

Olaf
.

Relevant Pages

  • Re: Need help with loading .SO file
    ... Its the wrong lib. ... stubs lib and define -DUSE_TCL_STUBS during compile. ... file shells with extra static packages included. ...
    (comp.lang.tcl)
  • Re: How the linker imports DLL functions
    ... > Apparently, the stubs really aren't in the .lib, for two reasons: ... > So the stubs simply aren't there. ... Microsoft MVP - Visual C++ ...
    (microsoft.public.vc.language)
  • Re: How to cope with version conflicts?
    ... In order to use an extension across releases with 100% confidence, ... able to build a version without stubs support. ... function since Tcl 8.5. ...
    (comp.lang.tcl)
  • Re: [ANNOUNCE] [dict] command backport for tcl8.4
    ... > C API as provided by Tcl-8.5, with the note that the C API is not binary ... > * The extension export a stubs table, ... If there are no volunteers, the first user will have to ... how would I use the stubs? ...
    (comp.lang.tcl)
  • Re: [PATCH] compat: add compat functions for *at syscalls
    ... In which case you need to to stubs for all the *at syscalls. ... char * tmp; ... this is sufficient to get the 32 to 64 bit sign extension ...
    (Linux-Kernel)