Re: [Plplot-general] Compile for tcl binding

[Shen-Yeh C. <she...@ho...>]

OK......I think I have done something right now, so at least I am seeing ENABLD_tcl set to on.

For some specific reason I do have to use my own built version of Tcl, so this is what I have done

1. I copy tchsh86t.exe to tchsh.exe, and copy tcl86t.lib to tcl86.lib
2. the following commands are used to call cmake and nmake. And I have attached their output here too.

set PATH=%PATH%;c:/DISK0001/Optimizer01/Worksp/SOURCE/Tcltk/Tcltk_8_6_0/tcl/win/Install_AMD64/bin
set CMAKE_INCLUDE_PATH=c:/DISK0001/Optimizer01/Worksp/SOURCE/Tcltk/Tcltk_8_6_0/tcl/win/Install_AMD64/include
set CMAKE_LIBRARY_PATH=c:/DISK0001/Optimizer01/Worksp/SOURCE/Tcltk/Tcltk_8_6_0/tcl/win/Install_AMD64/lib

cmake "C:/DISK0001/Optimizer01/Worksp/SOURCE/plplot/plplot-5.10.0/SOURCE" -G "NMake Makefiles" -DPL_DOUBLE=ON -DLIB_TAG="sud" -DBUILD_TEST=ON -DCMAKE_INSTALL_PREFIX="C:\DISK0001\Optimizer01\Worksp\SOURCE\plplot\plplot-5.10.0\INSTALL" -DCMAKE_CONFIGURATION_TYPES="Release" -DBUILD_SHARED_LIBS=OFF -DSTATIC_RUNTIME=ON -DENABLE_tcl=ON -DTCL_LIBRARY_VERSION=86t > log_cmake04_tcl.out 2>&1

nmake > log_nmake04_tcl.out

Now the problem is......where do I find the .dll of plplot, that I can load into tcl ?

Thanks again for the help.

Regards
Chen



> Date: Fri, 10 Apr 2015 12:55:32 -0700
> From: ir...@be...
> To: she...@ho...
> CC: arj...@de...; plp...@li...
> Subject: RE: [Plplot-general] Compile for tcl binding
> 
> Hi Shen-Yeh:
> 
> Thanks for that captured output from the cmake command.  Notice in
> there it says:
> 
> Could NOT find Tclsh (missing:  TCL_TCLSH)
> 
> which means indeed our build system is not finding any of your current
> Tcl installation at all.
> 
> On 2015-04-10 08:24-0700 Shen-Yeh Chen wrote:
> 
> > Here is the path of the executable
> >
> > C:/DISK0001/Optimizer01/Worksp/SOURCE/Tcltk/Tcltk_8_6_0/tcl/win/Install_AMD64/bin/tclsh86t.exe
> >
> > The /lib directory has the following files (along with other directories)
> > tcl86t.lib
> > tclConfig.sh
> > tclooConfig.sh
> > tclstub86.lib
> 
> Arjen gave you advice about how to modify our build system so it will
> find your non-standard names for Tcl components.  That might work, but
> if you run into trouble with that approach, I suggest you adjust your tcl
> installation to be more standard instead.
> 
> For example, Arjen mentioned using a binary installation of Tcl instead of
> your own build.  That should work fine, but if you want to use your
> own build for some reason you could take a look at the binary version
> to see what the disk layout is, and then make sure the layout for your
> own build is similar.
> 
> For example, it is virtually a Tcl Windows standard that tclsh.exe must be
> defined as a copy of the versioned file that is installed so you
> should do that copy (of tclsh86t.exe in your case)
> in the
> 
> C:/DISK0001/Optimizer01/Worksp/SOURCE/Tcltk/Tcltk_8_6_0/tcl/win/Install_AMD64/bin
> 
> directory, make that directory part of the list of directories on your
> PATH, and then after that the tclsh command should "just work"
> regardless of what directory you are in.  Under bash.exe you could do
> that using
> 
> export \
> PATH=/c/DISK0001/Optimizer01/Worksp/SOURCE/Tcltk/Tcltk_8_6_0/tcl/win/Install_AMD64/bin:$PATH
> 
> but Arjen will have to advise you how to do that under DOS command line.
> 
> Similarly, you have to set the CMAKE_INCLUDE_PATH and
> CMAKE_LIBRARY_PATH environment variables I mentioned before so
> that our CMake-based build system can find your non-standard disk
> locations.  Under bash.exe you would do that using
> 
> export \
> CMAKE_INCLUDE_PATH=/c/DISK0001/Optimizer01/Worksp/SOURCE/Tcltk/Tcltk_8_6_0/tcl/win/Install_AMD64/include:$CMAKE_INCLUDE_PATH
> 
> (subject to adjustment as to wherever the tcl.h file is located on
> your system), and
> 
> export \
> CMAKE_INCLUDE_PATH=/c/DISK0001/Optimizer01/Worksp/SOURCE/Tcltk/Tcltk_8_6_0/tcl/win/Install_AMD64/lib:$CMAKE_LIBRARY_PATH
> 
> In both cases you might have to do some file copies to work around the
> non-standard t suffix that seems to be in some of your Tcl-related
> file names.  For example, you might have to create
> tcl86.lib as a copy of tcl86t.lib.
> 
> I think I have come to the end of my limited Tcl/Windows expertise so
> I will let Arjen guide you further.  Good luck in getting this
> all to work.
> 
> Alan
> __________________________
> Alan W. Irwin
> 
> Astronomical research affiliation with Department of Physics and Astronomy,
> University of Victoria (astrowww.phys.uvic.ca).
> 
> Programming affiliations with the FreeEOS equation-of-state
> implementation for stellar interiors (freeeos.sf.net); the Time
> Ephemerides project (timeephem.sf.net); PLplot scientific plotting
> software package (plplot.sf.net); the libLASi project
> (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
> and the Linux Brochure Project (lbproject.sf.net).
> __________________________
> 
> Linux-powered Science
> __________________________