It has no effect. But it would be a good idea for tests to not bring in extra modules.<div> <div>When Group_Imaging is enabled it also switches on:</div><div>Module_vtkCosmo</div><div>Module_vtkFiltersParallel</div><div><div>
Module_vtkFiltersParallelImaging</div><div>Module_vtkInteractionImage</div>
<div>Module_vtkParallelMPI</div><div>Module_vtkRenderingImage</div><div><br></div><div>For some reason ParallelMPI gets called in. </div><div>I am sure that an earlier build worked Ok with Group_Imaging enabled so somewhere in the DAG's this module has been inadvertently added.</div>
<div><br></div>Regards</div><div> Andrew</div><div><br><div class="gmail_quote">On Thu, Apr 12, 2012 at 6:30 AM, Pat Marion <span dir="ltr"><<a href="mailto:pat.marion@kitware.com" target="_blank">pat.marion@kitware.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Not sure if this is relevant, but I've noticed that when BUILD_TESTING is enabled, which is the default, the testing code of enabled modules has the ability to request modules that otherwise would be OFF.<span><font color="#888888"><br>
<br>Pat</font></span><div><div><br>
<br><div class="gmail_quote">On Wed, Apr 11, 2012 at 3:37 PM, Cory Quammen <span dir="ltr"><<a href="mailto:cquammen@cs.unc.edu" target="_blank">cquammen@cs.unc.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
For me, using the default settings in CMake with a clean build<br>
directory compiles just fine.<br>
<br>
When I then enable VTK_Group_Imaging, CMake starts looking for MPI.<br>
<br>
I'm using commit cfb0881e8468e4219a3bb6386cffe3a5037a9c65.<br>
<span><font color="#888888"><br>
Cory<br>
</font></span><div><div><br>
On Wed, Apr 11, 2012 at 3:24 PM, Marcus D. Hanwell<br>
<<a href="mailto:marcus.hanwell@kitware.com" target="_blank">marcus.hanwell@kitware.com</a>> wrote:<br>
> What other groups do you have enabled? I think Rendering and<br>
> StandAlone are pretty clear, but it looks like some of the other<br>
> groups may not be. One of the issues we are having is that groups have<br>
> members, without conditional memberships.<br>
><br>
> In addition to the Rendering group, do we want a ParallelRendering<br>
> group for example, or just leave out those components (as I have for<br>
> now). We don't want MPI bringing in all of rendering either. The<br>
> groups are certainly a work in progress, we are open to suggestions<br>
> (and would like to keep the list reasonably short so as not to<br>
> duplicate all the possibilities of just selecting modules for<br>
> example).<br>
><br>
> Marcus<br>
><br>
> On Tue, Apr 10, 2012 at 7:41 PM, Andrew Maclean<br>
> <<a href="mailto:andrew.amaclean@gmail.com" target="_blank">andrew.amaclean@gmail.com</a>> wrote:<br>
>> Hi Marcus,<br>
>> I think there is a dependency issue:<br>
>> I have VTK_Group_MPI deselected and it looks as if CMake is still looking<br>
>> for MPI:<br>
>><br>
>> Could NOT find MPI_C (missing: MPI_C_LIBRARIES MPI_C_INCLUDE_PATH)<br>
>><br>
>> Could NOT find MPI_CXX (missing: MPI_CXX_LIBRARIES MPI_CXX_INCLUDE_PATH)<br>
>><br>
>> Could NOT find MPI_C (missing: MPI_C_LIBRARIES MPI_C_INCLUDE_PATH)<br>
>><br>
>> Could NOT find MPI_CXX (missing: MPI_CXX_LIBRARIES MPI_CXX_INCLUDE_PATH)<br>
>><br>
>> CMake Error: The following variables are used in this project, but they are<br>
>> set to NOTFOUND.<br>
>><br>
>> Please set them or make sure they are set and tested correctly in the CMake<br>
>> files:<br>
>><br>
>> MPI_LIBRARY (ADVANCED)<br>
>><br>
>> linked by target "vtkParallelMPI" in directory<br>
>> C:/Users/amaclean/Code/Kitware/src/VTK/Parallel/MPI<br>
>><br>
>><br>
>> Regards<br>
>> Andrew<br>
>><br>
>> --<br>
>> ___________________________________________<br>
>> Andrew J. P. Maclean<br>
>><br>
>> ___________________________________________<br>
> _______________________________________________<br>
> Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
><br>
> Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
><br>
> Follow this link to subscribe/unsubscribe:<br>
> <a href="http://www.vtk.org/mailman/listinfo/vtk-developers" target="_blank">http://www.vtk.org/mailman/listinfo/vtk-developers</a><br>
><br>
<br>
<br>
<br>
</div></div><div>--<br>
Cory Quammen<br>
Research Associate<br>
Department of Computer Science<br>
The University of North Carolina at Chapel Hill<br>
</div><div><div>_______________________________________________<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.vtk.org/mailman/listinfo/vtk-developers" target="_blank">http://www.vtk.org/mailman/listinfo/vtk-developers</a><br>
<br>
</div></div></blockquote></div><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>___________________________________________<br>Andrew J. P. Maclean<br><br>___________________________________________<br>
</div>
</div>