Re: Using system tcl/tk version 8.5

[Gene Smith <gds at chartertn dot net>]

Gene Smith wrote, On 04/06/2010 11:11 PM:
> If I try a native 64bit build with system tcl/tk like this,
>
> ../insight_sources/configure -v --quiet --prefix=$PREFIX \
> --with-tcl=/usr/lib64 --with-tk=/usr/lib64 --with-itcl=/usr/lib64 \
> --with-itk=/usr/lib64
>
> I see this error:
>
> Configuring in ./itcl
> config.status: WARNING: ../../../insight_sources/itcl/itcl/Makefile.in
> seems to ignore the --datarootdir setting
> config.status: WARNING: ../../../insight_sources/itcl/itk/Makefile.in
> seems to ignore the --datarootdir setting
> configure: error: Can't find Itcl source. Use --with-itcl to specify the
> the toplevel incr Tcl directory on your system. (This directory should
> contain itcl/library/itcl.tcl, itk/library/itk.tcl, and
> config/mkinstalldirs.)
> configure: error: ../../../insight_sources/itcl/iwidgets/configure
> failed for iwidgets
> make[1]: *** [configure-itcl] Error 1
> make[1]: Leaving directory `/home/gene/addons/insight-cvs/insight_build'
> make: *** [all] Error 2

This error seems to be due to the fact that I left insight's tcl and tk 
dirs in the tree. When I rename or delete them the build works and 
installs. Don't know that it actually debugs correctly but it runs. Was 
able to build for 64 or 32bit host.

The --with-itcl=... is not needed but doesn't hurt.

To build for 32 bit host I do this:
../insight_sources/configure -v --quiet --prefix=$PREFIX \
   --target=$TARGET --enable-interwork --enable-multilib \
   --with-gnu-ld --with-gnu-as --with-tcl=/usr/lib \
   --with-tk=/usr/lib \
   --disable-werror --host=i686-pc-linux-gnu --build=i686-pc-linux-gnu \
   CFLAGS="-m32" LDFLAGS="-m32"

Also, today built CVS head on a 32-bit f8 system w/ insight's own 
tk/tcl. It ran but the source gui window would not debug. I was able to 
see code, load code to flash etc but no stepping or GREEN highlight line 
was ever visible. Was able to step and set BPs using console/gdb window 
however. Gdb does not inform the GUI source window as to what is going 
on, it seems. This is configured as target arm-none-eabi so I guess that 
has something to do with it since a default/native x86_64 or i686 target 
works OK with cvs head.

-gene