Home/ Questions/Q 8894993
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-14T23:39:16+00:00

I’m attempting to build and fix UCL RAT for running on windows compiled with

  • 0

I’m attempting to build and fix UCL RAT for running on windows compiled with VS 2010.
I’ve compiled TCL 8.5.12 successfully under Visual studio 2010 and the main RAT executable.

RAT uses TCL to drive it’s user interface.

The problem arose when I started to modify RAT to embed the TCL code normally stored as a string into a zip file instead using zvfs. The intention is to eventually embed the zip at the end of the executable to minimise disk usage and the number of distribution files.

So I downloaded some code for zvfs from the TOBE project to see if I could use it to make the process quicker (specifically the zvfs.c file that is basically the zvfs extension to tcl)

This required Zlib in order to run which built and integrated fine.

But the problem is the zvfs code doesn’t link properly with TCL. It passes compilation but has the following errors upon linking:

2>zvfs.obj : error LNK2019: unresolved external symbol _TclOpenFileChannelInsertProc referenced in function _Zvfs_Init
2>zvfs.obj : error LNK2019: unresolved external symbol _TclStatInsertProc referenced in function _Zvfs_Init
2>zvfs.obj : error LNK2019: unresolved external symbol _TclAccessInsertProc referenced in function _Zvfs_Init

not being as experienced with c/c++ and the linker as I could be this has become somewhat of a road block in fixing RAT for more modern versions of windows.

The version of RAT is the latest from the UCL subversion server, Zlib is at version 1.2.7 if this has any impact.

Cheers

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Those particular functions are obsolete, but still supported in the correct build up to Tcl 8.5 (including 8.5.12). You need to use a compile where you define the preprocessor symbol USE_OBSOLETE_FS_HOOKS (to be anything) during a clean build of the Tcl library. Alas, this means you need to edit the build instructions away from the default, and that’s where I can’t help as I use a totally different build chain (on a different platform) from you.

    Also, when linking you need to link against the Tcl library itself and not its stub library.

    • 0