<div dir="ltr">Ben,<div><br></div><div>Any updates? We should clean this up before the release.</div><div><br></div><div>Utkarsh</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jan 3, 2014 at 4:02 PM, Burlen Loring <span dir="ltr"><<a href="mailto:bloring@lbl.gov" target="_blank">bloring@lbl.gov</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">that's how it was handled it in the past, prior the recent refactoring, and I think that's the way to go. Where does the refactoring stand is Ben B finished? It would be great if Ben B could clean this up, but if not I can make a pass next week.<span class="HOEnZb"><font color="#888888"><br>
<br>
Burlen</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
On 01/03/2014 11:47 AM, Utkarsh Ayachit wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Burlen,<br>
<br>
CUDA is confusing more people than not. Also it's adding too many<br>
variables. A cleanup to FindCUDA.cmake is certainly in the order.<br>
Until then, I propose we swicth SQTK_CUDA variable to do a<br>
find_package(CUDA) only if SQTK_CUDA is enabled. What do you think?<br>
BTW, I want to tag the release soon, so we should try to keep changes<br>
to a minimal at this point.<br>
<br>
Utkarsh<br>
<br>
<br>
On Thu, Jan 2, 2014 at 5:33 PM, Burlen Loring <<a href="mailto:bloring@lbl.gov" target="_blank">bloring@lbl.gov</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hey Patrick and Ben, Thanks for the feedback.<br>
<br>
In this case I think it's confusing to be dumped into a separate ccmake<br>
screen. I'd say it's really an issue in the FindCUDA.cmake module, which<br>
does<br>
<br>
message("CUDA_TOOLKIT_ROOT_DIR not found or specified")<br>
<br>
according to the documentation a naked message command is supposed to mean<br>
"Important information". In this case it's not. I think this message should<br>
probably be downgraded to STATUS type. just my 2 cents.<br>
<br>
At any rate, we could avoid the problem in PV if in the plugin we used<br>
<br>
find_package(CUDA QUIET)<br>
<br>
but initially all the cuda stuff, including find_package, was controlled by<br>
a cache variable so that this confusing behavior could be avoided and I<br>
wouldn't have to use the QUIET option because when you're actually trying to<br>
configure for cuda the output is helpful if things go wrong.<br>
<br>
Burlen<br>
<br>
<br>
On 01/02/2014 02:01 PM, Benjamin Spencer wrote:<br>
<br>
You're right. I didn't realize this was just an informational message, and<br>
not an error that has to be resolved. After I hit that message the first<br>
time, then configure a second time and hit that message again, I can<br>
successfully generate the makefile.<br>
<br>
Thanks,<br>
Ben<br>
<br>
On Thu, Jan 2, 2014 at 2:37 PM, Patrick O'Leary <<a href="mailto:patrick.oleary@kitware.com" target="_blank">patrick.oleary@kitware.com</a>><br>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Dear Ben and Burlen,<br>
<br>
On my Mac Book Pro with NVidia card, I received the same informational<br>
message but it builds if I exit the informational screen with 'e' and hit<br>
'g'.<br>
<br>
Best regards,<br>
Patrick<br>
<br>
<br>
On Thu, Jan 2, 2014 at 2:33 PM, Burlen Loring <<a href="mailto:bloring@lbl.gov" target="_blank">bloring@lbl.gov</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Benjamin,<br>
<br>
This is of interest to me as I haven't been involved in the recent plugin<br>
changes and need to look through them more closely.<br>
<br>
You reported an informational message that is not an error. Could you<br>
report the actual error?<br>
<br>
btw, I also see the message on my ATI based system, but it doesn't<br>
prevent me from building. For example in ccmake I can press "e" to exit the<br>
informational screen where the message is displayed and then hit "g" to<br>
generate the make files and go on to compile without issue.<br>
<br>
Burlen<br>
<br>
<br>
On 01/02/2014 12:41 PM, Benjamin Spencer wrote:<br>
<br>
I'm trying to build ParaView 4.1.0-RC2 from source on Mac OS (10.8.5).<br>
This machine does not have CUDA installed (and has no nvidia graphics<br>
hardware).<br>
<br>
When running ccmake, I get this error:<br>
<br>
CUDA_TOOLKIT_ROOT_DIR not found or specified<br>
<br>
This seems to be coming from the call:<br>
find_package(CUDA)<br>
in<br>
Plugins/SciberQuestToolKit/<u></u>SciberQuest/CMakeLists.txt<br>
<br>
If I comment that line out, I can successfully compile. I'm no cmake<br>
guru, but it seems like if I don't have CUDA installed, find_package(CUDA)<br>
should just set CUDA_FOUND to OFF and not require any paths to CUDA to be<br>
set. Maybe this is an issue with the CUDA module in CMake rather than<br>
ParaView. I'm using the latest CMake (2.8.12.1).<br>
<br>
Thanks,<br>
Ben<br>
<br>
Benjamin Spencer<br>
Fuels Modeling and Simulation<br>
Idaho National Laboratory<br>
<br>
<br>
______________________________<u></u>_________________<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at<br>
<a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/<u></u>opensource/opensource.html</a><br>
<br>
Please keep messages on-topic and check the ParaView Wiki at:<br>
<a href="http://paraview.org/Wiki/ParaView" target="_blank">http://paraview.org/Wiki/<u></u>ParaView</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.paraview.org/mailman/listinfo/paraview" target="_blank">http://www.paraview.org/<u></u>mailman/listinfo/paraview</a><br>
<br>
<br>
<br>
______________________________<u></u>_________________<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at<br>
<a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/<u></u>opensource/opensource.html</a><br>
<br>
Please keep messages on-topic and check the ParaView Wiki at:<br>
<a href="http://paraview.org/Wiki/ParaView" target="_blank">http://paraview.org/Wiki/<u></u>ParaView</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.paraview.org/mailman/listinfo/paraview" target="_blank">http://www.paraview.org/<u></u>mailman/listinfo/paraview</a><br>
<br>
</blockquote></blockquote>
<br>
<br>
______________________________<u></u>_________________<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at<br>
<a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/<u></u>opensource/opensource.html</a><br>
<br>
Please keep messages on-topic and check the ParaView Wiki at:<br>
<a href="http://paraview.org/Wiki/ParaView" target="_blank">http://paraview.org/Wiki/<u></u>ParaView</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.paraview.org/mailman/listinfo/paraview" target="_blank">http://www.paraview.org/<u></u>mailman/listinfo/paraview</a><br>
<br>
</blockquote></blockquote>
<br>
</div></div></blockquote></div><br></div>