Include paths in CMake files should be cleaned up
This issue was created automatically from an original Mantis Issue. Further discussion may take place here.
The build files in ParaView 3.8.0 contain several include paths that don't seem exist in this version. It would be great if these were cleaned up. When building with Eclipse Helios / CDT 7 / Unix Makefiles, Eclipse reports the following warnings:
Invalid project path: Include path not found (/home/cw/prj/ParaView/build/Plugins/PointSprite/ParaViewPlugin/Resources). Invalid project path: Include path not found (/home/cw/prj/ParaView/build/Plugins/PrismPlugins/Client/Resources/UI). Invalid project path: Include path not found (/home/cw/prj/ParaView/build/Qt/ApplicationComponents/Resources/UI). Invalid project path: Include path not found (/home/cw/prj/ParaView/build/Qt/Chart). Invalid project path: Include path not found (/home/cw/prj/ParaView/build/Qt/Components/Resources/UI). Invalid project path: Include path not found (/home/cw/prj/ParaView/build/Qt/Core/Resources/UI). Invalid project path: Include path not found (/home/cw/prj/ParaView/build/Qt/Widgets/Resources/UI). Invalid project path: Include path not found (/home/cw/prj/ParaView/build/VTK/netcdf/netcdf-3.6.1/src/libsrc). Invalid project path: Include path not found (/home/cw/prj/ParaView/src/Qt/Chart). Invalid project path: Include path not found (/home/cw/prj/ParaView/src/Utilities/VTKClientServer/ClientServer). Invalid project path: Include path not found (/home/cw/prj/ParaView/src/Utilities/Xdmf2/libsrc/test/MPI_INCLUDE_PATH). Invalid project path: Include path not found (/home/cw/prj/ParaView/src/VTK/GenericFiltering/Testing/Cxx/Bridge). Invalid project path: Include path not found (/home/cw/prj/ParaView/src/VTK/netcdf/netcdf-3.6.1/src/libsrc). Invalid project path: Include path not found (/Utilities/vtksqlite).
I know this sounds only like an irrelevant cosmetic thing, but it's been bugging me for some time while developing a custom ParaView client application. There is actually a practical reason why I am reporting this: Since this issue generates lots of warnings in Eclipse, I have already overlooked an important compiler warning, leading to many hours of unnecessary debugging - and I am afraid this might happen again.