Archived issue #0024316
Make building with different versions of Tcl easier
Description
Tcl is different from other third-party libraries used by OCCT in that it uses version number of the package name as part of the name of its shared library. Hence, library name to be linked with OCCT depends on Tcl version used.
Currently Tcl library name is hard-coded in WOK scripts, which causes problem (at least on Windows with MSVC, you have to change name of the library in properties of the generated project files) if you have different version of Tcl.
It is highly desirable to have Tcl library name defined automatically for actual Tcl being used. With MSVC, it is possible using #pragma comment statement.
Currently Tcl library name is hard-coded in WOK scripts, which causes problem (at least on Windows with MSVC, you have to change name of the library in properties of the generated project files) if you have different version of Tcl.
It is highly desirable to have Tcl library name defined automatically for actual Tcl being used. With MSVC, it is possible using #pragma comment statement.
Public activity
2 archived notes
Participants are labeled by their role within this record.
Fixes pushed to branch CR24316 in WOK repository and CR0-abv-IR-2013-11-01 in OCCT repository, please review
I have no objections against the patch, although only Windows platform has been modified.
I consider using "-framework Tcl, -framework Tk" on Mac OS X platform and detection of tcl85 on Linux platform, since 8.6 is not yet mainstream - in dedicated patch.
I consider using "-framework Tcl, -framework Tk" on Mac OS X platform and detection of tcl85 on Linux platform, since 8.6 is not yet mainstream - in dedicated patch.
Related records