Bug 136324 - VTK 4.2.6. Is TCLTK an option or not?
|
Bug#:
136324
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: x86
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: normal
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: markusle@gentoo.org
|
Reported By: daniel.tourde@bredband.net
|
|
Component: Ebuilds
|
|
|
URL:
|
|
Summary: VTK 4.2.6. Is TCLTK an option or not?
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2006-06-10 14:26 0000
|
Hello,
In VTK 4.2.6, is TCLTK optional or not? Even though I do not wish to have TCLTK
support in VTK, the ebuild triggers the build of TCL and TK:
mhordraid ted # emerge -pv vtk
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild N ] dev-util/cmake-2.0.6-r1 USE="-debug" 1,593 kB
[ebuild N ] dev-lang/tcl-8.4.9 USE="-threads" 3,414 kB
[ebuild N ] dev-lang/tk-8.4.9 USE="-threads" 3,189 kB
[ebuild N ] sci-libs/vtk-4.2.6 USE="doc java python -examples -mpi
-patented -tcltk -threads" 26,413 kB
Total size of downloads: 34,611 kB
So, if TCLTK is really optional to VTK, the RDEPENDS list should reflect that.
Otherwise, let's get rid of the unnecessary flag.
Daniel
Hi Daniel,
Thank you very much for your report. Tcl/Tk is indeed optional and was
incorrectly pulled in by the ebuild in case tcltk is not selected. I've just
fixed this in the vtk-5.0.0 ebuild which is the version that I'd strongly
recommend you to use since vtk-4.2.6 is fairly broken and will be
removed from the tree/replaced by a more recent 4.x version
soon. Please let us know if this works for you so I can close this
bug.
Thanks,
Markus
It worked indeed. I could build vtk-5.0.0 on a glibc 2.4, gcc 4.1.1 machine
(x86).
I used cmake 2.4.2
I have no programs to check if vtk works though. The idea is to use paraview,
as soon as an ebuild is ready.
Will vtk 4.4.x be released as an ebuild as well?
Hi Daniel,
Thanks for testing and I'll close this bug then.
Regarding testing vtk itself, vtk comes with a bunch of example
files that you can compile/run yourself and see if things
work properly.
Regarding a 4.4.x ebuild, please watch bug #135965.
Unfortunately, I haven't had time yet to look into this
in more detail.
Thanks,
Markus