Mantis - ISSUES

0010418: get_prerequisites() gives bad results if ldd couldn't find full path to item

ldd gives "not found" if the full path to a library could not be found.
GetPrerequisites.cmake interprets that as the target depending on "not" and I have to debug the script for which library it really is.
It should probably be fixed to return the name of the library, instead of the full path, so one can get relevant warnings/errors from BundleUtilities.cmake.

0008486: Additional platforms support (Windows CE and Symbian)

Hi, we have implemented the subj and you can find the source here: http://github.com/AlexeyS/cmake/tree/master [^]

There are two main branches in the repo:
* WindowsCE - Windows CE MSVS project generator
* Symbian - Symbian .mmp project generator

Also we have implemented one additional feature: defining a set of valid values for a CMake variable. This feature was inspired by the need to enter long and boring Windows CE platform name (like "Windows Mobile 5.0 Smartphone"). This feature introduces SET_VALID_VALUES command, so CMake now can validate all the values you assign to the variable. Most importantly this allows us to introduce comboboxes for such variables in the CMake GUIs. The comboboxes feature is also implemented for the Qt frontend and for the MFC one. You can find this code in the ValidValues branch.

The rest are merged branches:

* WindowsCEwithValidValues - [WindowsCE + ValidValues] - WindowsCE generator now fills the combobox with platform names for which installed SDKs were detected.

* all - [WindowsCEwithValidValues + Symbian]

We would be happy to contribute this code to the CMake upstream.
Thank you for such a great tool as CMake.

Looking forwards for your comments, criticism, else.

0010417: BundleUtilities/GetPrerequisites not doing bundleutilities example correctly

There is an example here:
http://www.cmake.org/Wiki/BundleUtilitiesExample [^]

That doesn't work correctly.

There are two problems.

1.
otool -L also returns the install id, if it exists, which means get_prerequistes can return the target itself as a dependency of the target. This causes problems for BundleUtilities.cmake.
The attached patch fixes this.

2.
BundleUtilities.cmake makes the assumptions that plugins have to reside in the same directory as the executable. In the example, the Qt plugins have a special layout.

Attached patch fixes both issues.

0009901: Support for CodeLite IDE

Hello,

Will be very appreciated codelite projects support in the next version of cmake.

Thanks in advance.
Pablo.

0010416: HDF5 dependencies detection

HDF5 library can depends on zlib and/or szip libaries.
Detection of this dependencies fails if when the HDF5_C_COMPILER_EXECUTABLE is not available (e.g. when one try to use pre-build HDF5 libraries on win32).

Please find attached the modified version of FindHDF5.cmake that
includes:

* improved logic for detecting zlib and szib dependencies when the
wrapper compiler is not available
* code for setting windows specific defines for using DLLs when the
wrapper compiler is not available
* code for setting component specific libraries
(HDF5_${LANGUAGE}_LIBRARIES). The variable was always empty in the
previous version

Please note that the modified module depends on Michael
Jackson's FindSZIP.cmake module available at

http://gitorious.org/hdf5/hdf5-v18/blobs/master/Resources/CMake/FindSZIP.cmake [^]

0010344: Windows CMake compilation under mingw-w64

When building CMake under Windows using a binary CMake 2.8.0 release and using a mingw-w64 toolchain, compilation fails because the Windows reserved keyword BOOL is used as a property name. Also, an #ifdef structure does not check for mingw, so it does not define a critical function.

These are all trivial patches (renaming 1 variable in +/- 11 files), and adding a conditional for mingw(-w64)

0009552: would like to build VTK with gcc visibility hidden

This says it all:
http://gcc.gnu.org/wiki/Visibility [^]

I did this on another app about the same size as ParaView and the first thing I saw was a big improvement in start up time.

0010176: Add Support for IAR compiler

Add support for IAR compiler. CMakeCCompilerId.c.in has such definition already
/* IAR Systems compiler for embedded systems.
http://www.iar.com [^]
Not supported yet by CMake
#elif defined(__IAR_SYSTEMS_ICC__)
# define COMPILER_ID "IAR" */

0010415: Problems recording tests

Running current ParaView head, when I go to tools, record new test, save the file name the output messages window pops up with the message, "Internal error: playEvent called without a valid event source." The test seems to record successfully, but if I change the view type it fails with an error such as, "Event error "activate" object QMenu(0x2195f80, name = "FrameContextMenu")". This was working for me when I recorded the original tests for the charts.

0010414: vtkVoxelModeller produces VTK_BIT array, should produce VTK_INT

If you try to write the output of vtkVoxelModeller with a vtkXMLImageDataWriter (like this: http://www.vtk.org/Wiki/VTK/Examples/VoxelModeller), [^] it complains that VTK_BIT is not supported. I have converted all instances of vtkBitArray and VTK_BIT with vtkIntArray and VTK_INT, respectively, and it now works as expected.

Can we commit this?

0010386: Marks: Log scale doesn't work for bottom/top axes

Log scale doesn't seem to work for bottom or top axes, it works for left/right axes.

0010413: Bug with vtkEnSightWriter about writing vector cell data

There is a bug with vtkEnSightWiriter.cxx about writing vector cell data.
Specifically, the loop order around the comment "write the Cell Data for this part" is not correct

Please look at the attached file:
1. I changed the for-loop order.
2. I added VTK_POLYGON and VTK_CONVEX_POINT_SET to the types of cells.

kenichiro yoshimi

0010412: Infovis: Icicle view errors when area labels turned off

I'm getting errors when I try to turn off the area labels in an icicle view. As a demonstration, if you modify [vtk_source]/Examples/Infovis/Python/icicle_view_simple.py line 12 so that view.SetAreaLabelVisibility(False) instead of True, at least on my machine I get three instances of:

ERROR: In /Users/emonson/Programming/VTK_cvs/VTK/Filtering/vtkAlgorithm.cxx, line 422
vtkPointSetToLabelHierarchy (0x104b8e970): Attempt to get vertex or edge data from a non-graph

right as the program starts up. It seems to work okay after that, but there's something small wrong somewhere...

0010410: Development install tree: cannot clean intermediate targets

With PARAVIEW_INSTALL_DEVELOPMENT turned on.

- make && make install
- the bin/ and lib/ are built

Since the install directory contains about 5800 "*.cxx.o" files (273MB
worth), it needs to be cleaned up before distributing the development
install tree for building plugins.

Using the make target 'clean' removes the "*.cxx.o* files, but also
removes all of the bin/ files - rendering the installation useless.

On a positive note, the contents of lib/paraview-MAJOR are left
intact.

It seems that a clean development install tree cannot be realized
without writing external cleanup scripts.

0010411: Development install tree cannot find documentation

With PARAVIEW_INSTALL_DEVELOPMENT turned on.

same problem as previously reported
www.mail-archive.com/paraview@paraview.org/msg06349.html">http://www.mail-archive.com/paraview@paraview.org/msg06349.html [www.mail-archive.com/paraview@paraview.org/msg06349.html" target="_blank">^]

- make && make HTMLDocumentation && make install

Both Documentation/ and doc/ directories exist in the install
directory, but paraview reports the following:

QTextBrowser: No document for qthelp://paraview.org/paraview/ParaViewFilters.html [^]

0009775: FindwxWidgets does not support new wxWidgets 2.9 libraries

In wxWidgets 2.9+ the stc and wxscintilla modules were moved from contrib into the main library. I have attached a patch against the FindwxWigets.cmake file in 2.8-rc2 which adds support for them.

0005943: cmake -E command should be improved with more commands

Often you need some basic commands.
But you can't use other commands, e.g. FILE(), because the source file you generate will be used or have been generated during your build process.

So for simply file manipulation the user should be able to do this by using a cmake -E command as it can be done now.
But at the moment the cmake -E commands are a small subset of usefull commands. In order to make cmake more powerfull, cmake -E should support following commands:

1. move: To move a file from one point to an other. If some output will be generated during build only for information (e.g with third party things) and it will harm the build, then it will be usefull to move the file to an other destination.
2. rename: sometimes it is usefull to rename a file. (can be done also by a copy + move)
3. prepend and append: Usefull to add before and after a file some text description. E.g. you need a licence or you want to generate a file with the information: This file is generated. Do not edit!. Then this information could be added.

0010385: Marks: Top axis labels are incorrectly positioned.

* Plot Over Line
* New XY Plot
* Open View Settings
* Click "Show Axis" for Top Axis.
Bugs:
- Labels appear under the top axis instead of above it. (Same is true for right axes, labels should appear on the right of the axis).
- Labels from bottom axis disappear (and don't reappear even if you turn off top axis).

0008607: (Venus - Medium) Axis layout with logarithmic scale writes numbers on top of each other

ParaView trunk, XP, local server.
Open disk_out_ref.exo
Plot Over Line.
View options (then labeled as Chart Options).
Bottom Axis - Make sure that Show Axis Labels when Space is Available is checked.
Bottom Axis/ Layout/ Specify Each of the Axis Labels.
Select Use Logarithmic Scale When Available.
Generate - From 1 To 1e4 Steps 50. Unselect Use Logarithmic Scale. OK.

Everything is on top of each other. This is a bug.

0008609: (Venus - Med) Chart Show Axis Labels When Space Is Available doesn't work

ParaView trunk, XP, local server.
Open disk_out_ref.exo
Plot over line.
Chart Options/ Bottom Axis/ Layout/ Specify each of the Axis Labels.
New Label - 0.00
New Label - 55.00
New Label - 56.00
New Label - 100.00
Apply.

Note that 55.00 and 56.00 are on top of each other. This is a bug, since "Show Axis Labels when Space Is Available" is selected.

0010229: FindGTest.cmake doesn't work with gtest built via CMake on Windows

The googletest project now includes a CMakeList.txt file (see here: http://code.google.com/p/googletest/source/browse/trunk/CMakeLists.txt). [^] However, if you build googletest via this method, FindGTest.cmake will not be able to find the gtest libraries on Windows.

0010401: Cannot build dll's with MinGW due to 32k limit

The variable archiveCommandLimit in cmMakefileLibraryTargetGenerator.cxx is used to generate static libraries even if there is an issue with the 32k limit under windows.

Unfortunately this variable is not applied when building shared libraries only.
I have a library here that consists of more then 700 (generated) code files and cannot build it as a dll with MinGW because of the"The parameter is incorrect" error.

I'd suggest setting the archiveCommandLimit to 30k by default wether or not there is a static library being build.

0010409: Add revision column to update in dashboard

It would be very helpful to see what revision the build information is relating to, without following the link to the update information.
For subversion this could be easily shown in single column, as it is represented by a single revision number.
It might be more difficult for other version control systems as CVS, which do have such a concept of one single revision number for everything, but a timestamp might be used instead in these cases.

0010408: Time based reload for project dashboard page

It would be very helpful if the dashboard page could automatically reload itself
for example once every five minutes.

0010208: Add support for Clang Static Analyzer (similar to 1st class valgrind support)

CTest/CDash currently have great integrated support for valgrind. It can be invoked to run tests, and the HTML dashboard page shows those results in a special section.

I'd like to see something similar for the Clang Static Analyzer.

If you're not familiar with it, see:
http://clang-analyzer.llvm.org/ [^]

Here is their summary:
"The term "static analysis" is conflated, but here we use it to mean a collection of algorithms and techniques used to analyze source code in order to automatically find bugs. The idea is similar in spirit to compiler warnings (which can be useful for finding coding errors) but to take that idea a step further and find bugs that are traditionally found using run-time debugging techniques such as testing.

Static analysis bug-finding tools have evolved over the last several decades from basic syntactic checkers to those that find deep bugs by reasoning about the semantics of code. The goal of the Clang Static Analyzer is to provide a industrial-quality static analysis framework for analyzing C and Objective-C programs that is freely available, extensible, and has a high quality of implementation."

The project is cross platform and open source. One downside is that it does not yet support C++.

I used it to find 4 bugs in freetype, a component of VTK.

I imagine two possible UIs
- a special section for analyzer warnings, like for valgrind
- an additional column to the right of compiler warnings, showing the number of warnings flagged by the analyzer