#4653 After build the dynamic lib,no TclpInitLibraryPath symbol

obsolete: 8.5.7
closed-invalid
None
5
2010-06-23
2010-06-23
blackcat
No

I build the tcl in windows via the command "nmake -f makefile.vc OPTS=threads", build success. But when I used the tcl8.*.lib in my code, there is the link error. There is not "TclFindEncodings" and "TclpInitLock" symbol in the lib. You told me use Tcl_MutexLock to instead of TclpInitLock. But which one I should use to instead of TclFindEncodings??

I have another question that I used tcl8.3 before, and these symbol can be used in 8.3 release, why I can not use in the latest release?

Discussion

  • blackcat

    blackcat - 2010-06-23

    sorry, the symbol that i can not find in the lib is TclpInitLibraryPath, not TclFindEncodings

     
  • blackcat

    blackcat - 2010-06-23
    • summary: After build the dynamic lib, there is no TclFindEncod symbol --> After build the dynamic lib,no TclpInitLibraryPath symbol
     
  • Jan Nijtmans

    Jan Nijtmans - 2010-06-23
    • assigned_to: nobody --> nijtmans
    • status: open --> closed-invalid
     
  • Jan Nijtmans

    Jan Nijtmans - 2010-06-23

    My answer is: please use the public Tcl API. Apparently, your application
    uses internal API functions, which are not meant to be called from outside
    of Tcl. The problem with that is that those functions are undocumented
    and might change between Tcl releases. So, you are really on your own.

    However, initializing a Tcl interpreter from another application is not
    difficult. Just use Tcl_Main or Tk_Main (the easiest) or
    Tcl_FindExecutable/Tcl_CreateInterpreter/Tcl_Init. You will
    find everything you need starting with <http://wiki.tcl.tk/6276>

     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks