[vtkusers] VTK + Tcl 8.3.0 + Itcl 3.1.0 (NT)
David J. Netherway
djn at elan.mad.adelaide.edu.au
Tue Feb 27 03:35:49 EST 2001
Dear Hugo,
Thanks for your help.
Your last suggestion was correct. There are no executables. You simply use the 8.3.2 version
of wish and access the Itcl, Itk and Iwidgets packages.
It all seems to be working now.
I haven't quite worked out why I had installation errors yesterday. But
uninstalling everything and starting again seemed to clear whatever mess I was in yesterday
- probably had incompatible versions floating arround.
The clue I needed was that there was no need for an itkwish.
Thanks again, David
However
Hugo Korwaser wrote:
> Dear David,
> my memory isn't very good.
> My 'instructions' were for using cygwin to compile using MSVC++.
>
> It is a pity that my 'instructions' are not consistent as you spotted.
> Particularly:
>
> c - configure using script in itcl3.2
> <path to tcl/win/configure> --prefix=<path of where to install>
>
> should be
>
> c - configure using script in itcl3.2
> <path to itcl3.2/configure> --prefix=<path of where to install>
>
> I do not know why the executables are not built for you. Possible things
> are:-
> - version of cygwin
> I most probably used 1.06
> - version of MSVC++
> I think you have to use 6.0
>
> Did you save the echo of the make. Maybe the compilations or links
> failed.
>
> Itcl3.2 is a loadable extention to tcl/tk 8.3 so you shouldn't need to
> have the executables.
>
> Regards
>
> Hugo
>
> "David J. Netherway" wrote:
> >
> > I have installed Cygwin and used it to compile tcl8.3.2 and tk8.3.2 successfully.
> > After recompiling VTK to use the new libraries that is also working.
> > But I have not been able to install itcl3.2. There is no win directory in the itcl3.2
> > directory.
> > I am assuming under your point 3 that you meant <path to itcl/win/configure> and not
> > <path to tcl/win/configure>.
> >
> > Running <path to itcl/configure> creates makefile etc.
> >
> > After "make" itcl and itk libs and dlls are created but no executables for
> > itkwish or itclsh.
> >
> > There is also a problem with "make install" tranferring the
> > dlls and libs to the install directory as well, but this can be done manually.
> >
> > I have used the default directories right though for tcl, tk and itcl so that
> > libs go into /usr/local/lib and binaries into /usr/local/bin. This works for
> > tcl and tk as I said earlier.
> >
> > Any ideas as to the problem?
> >
> > Thanks, David
> >
> > Hugo Korwaser wrote:
> >
> > > Further to my previous e-mail.
> > >
> > > There are differences in building tcl/tk8.3.2 on Windows NT ( I assume
> > > this will happen with W95/W98 etc.) between using Microsoft nmake and
> > > using the tea/cygwin approach.
> > > It manifests it self with tcl in that with nmake the tcltest package is
> > > not installed. It manifests itself with tk in that the fix that I
> > > mentioned in my previous e-mail causes a problem with duplicate symbols.
> > > In the tea build the tk resource files are concatinated into one. My fix
> > > will then bring in the cursors et al. a 2nd time. From this I infer that
> > > the tea method is the way to install.
> > >
> > > My quick guide to building tcl8.3.2/tk8.3.2/itcl3.2 using tea on NT
> > > assuming cygwin 1.0x is already installed. The commands should be
> > > entered in a cygwin bash shell window.
> > >
> > > 1 - Build tcl
> > > a - create a build directory
> > > mkdir build
> > > b - change directory to build directory
> > > cd build
> > > c - configure using script in tcl8.3.2/win
> > > <path to tcl8.3.2/win/configure> --prefix=<path of where to \
> > > install> --enable-threads
> > > the prefix and the enable threads parameters are optional
> > > d - compile and link
> > > make
> > > e - install
> > > make install
> > > 2 - Build tk
> > > a - create a build directory
> > > mkdir build
> > > b - change directory to build directory
> > > cd build
> > > c - configure using script in tk8.3.2/win
> > > <path to tk8.3.2/win/configure> --prefix=<path of where to install>
> > > --with-tcl=<pathname to where tcl was built> --enable-threads
> > > the prefix is optional and the enable threads parameters is
> > > required if tcl compiled with it.
> > > d - compile and link
> > > make
> > > e - install
> > > make install
> > > 3 - Build itcl
> > > a - create a build directory
> > > mkdir <build>
> > > b - change directory to build directory
> > > cd <build>
> > > c - configure using script in itcl3.2
> > > <path to tcl/win/configure> --prefix=<path of where to install>
> > > --with-tcl=<pathname to where tcl was built>
> > > --with-tk=<pathname to where tk was built> --enable-threads
> > > the prefix is optional and the enable threads parameters is
> > > required if tcl compiled with it.
> > > d - compile and link
> > > make
> > > e - install
> > > make install
> > >
> > > Hope this is of some use.
> > >
> > > Regards
> > >
> > > Hugo
> > >
> > > Hugo Korwaser wrote:
> > >
> > > > Hi Sebastein and David,
> > > > I have got vtk3.2beta to work with tcl/tk8.3.2 on NT4.0sp4 with VC++sp4.
> > > > The test examples also work using itkwish3.2.
> > > >
> > > > I did have a problem with tk in that the cursor definitions were not
> > > > compiled into the tk83 dll. This problem can be solved by editing
> > > > tk8.3.2/win/res/tk.res and adding the line
> > > >
> > > > #include "tk_base.rc"
> > > >
> > > > at the end of the file.
> > > > Rerunning the make should cause the resource file to be recompiled and
> > > > the dll rebuilt.
> > > >
> > > > I must say I struggled a bit with building itcl3.2 in that I didn't read
> > > > the readme file, assumed that the makefile.vc's were the things to use.
> > > > I then came across the reference to tea. There is an explanation on the
> > > > scriptics site, http://dev.scriptics.com/doc/tea/windows.html, that
> > > > provides the promised information. From a quick read I think that if you
> > > > do download the current version of cygwin some of the steps are
> > > > redundant or need modification.
> > > > 1 - is required
> > > > 2 - the installation is done by setup (cygwin's own version) which both
> > > > transfers the distribution and installs.
> > > > 3 - you can use an icon intstalled on your desktop or
> > > > start>programs->cygnus solutions
> > > > 4 - this is done by the current version
> > > > 5 - if you use vcvars.bat to setup the enviroment variables for visual
> > > > c++ to be run in a dos box you must call then from cygwin.bat so that
> > > > they are available from bash.
> > > > 6 & 7 this can be done when downloading and installing rather than
> > > > seperatly.
> > > > 8 9 & 10 depends on what you are doing.
> > > >
> > >
> > > _______________________________________________
> > > This is the private VTK discussion list.
> > > Please keep messages on-topic. Check the FAQ at: <http://public.kitware.com/cgi-bin/vtkfaq>
> > > Follow this link to subscribe/unsubscribe:
> > > http://public.kitware.com/mailman/listinfo/vtkusers
More information about the vtkusers
mailing list