<div>I would like to say thanks for addressing this issue. I didn't get a chance to say it on the bug report. I really appreciated it.</div><div><br></div><div>I would like to add a pointer to the fix (commitdiff).</div>
<div><a href="http://cmake.org/gitweb?p=stage/cmake.git;a=commitdiff;h=4167be052f3f68e637bb491a0b725f476bc3d46b">http://cmake.org/gitweb?p=stage/cmake.git;a=commitdiff;h=4167be052f3f68e637bb491a0b725f476bc3d46b</a></div>
<div>
<br></div><div>Best regards,</div><div>Hari</div><div><br></div><div><br><div><div><br><div class="gmail_quote">On Wed, Feb 16, 2011 at 9:53 AM, Clinton Stimpson <span dir="ltr"><<a href="mailto:clinton@elemtech.com">clinton@elemtech.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><br>
This might need some deeper looking into. If you could file a bug report, that<br>
would be nice.<br>
<br>
Clint<br>
<div><div></div><div class="h5"><br>
On Wednesday, February 16, 2011 09:15:25 am Harinarayan Krishnan wrote:<br>
> Hi All,<br>
><br>
> Any thoughts on this subject? or should I file a bug report and see what<br>
> happens?<br>
><br>
> Thanks,<br>
> Hari<br>
><br>
> On Tue, Feb 15, 2011 at 10:59 AM, Harinarayan Krishnan<br>
<<a href="mailto:hkrishnan@lbl.gov">hkrishnan@lbl.gov</a>>wrote:<br>
> > Hi All,<br>
> ><br>
> > I reran my code using cmake 2.8.4rc and still get the same issue where<br>
> > FIND_PATH is picking the system directory for QT_CORE over my install<br>
> > directory passed through HINTS ${qt_headers}. If this is not related to<br>
> > CMAKE_FIND_FRAMEWORK should I file a bug report on this?<br>
> ><br>
> > Thanks,<br>
> > Hari<br>
> ><br>
> > On Tue, Feb 15, 2011 at 10:23 AM, Andreas Pakulat <<a href="mailto:apaku@gmx.de">apaku@gmx.de</a>> wrote:<br>
> >> On 15.02.11 06:34:07, Harinarayan Krishnan wrote:<br>
> >> > Hi All,<br>
> >> ><br>
> >> > Thanks for the help so far, I will check and see if CMake 2.8.4rc has<br>
> >><br>
> >> the<br>
> >><br>
> >> > same issue meanwhile I noticed that FIND_PATH seems to have special<br>
> >> > instructions for Darwin machines with the use of CMAKE_FIND_FRAMEWORK<br>
> >> > on page<br>
> >><br>
> >> <a href="http://www.cmake.org/cmake/help/cmake-2-8-docs.html#command:find_path" target="_blank">http://www.cmake.org/cmake/help/cmake-2-8-docs.html#command:find_path</a><br>
> >><br>
> >> > The notes are a little confusing: it says CMAKE_FIND_FRAMEWORK<br>
> >> > defaults<br>
> >><br>
> >> to<br>
> >><br>
> >> > "FIRST" on Darwin systems which I can interpret one of two ways.<br>
> >> ><br>
> >> > First, If a standard library and a framework are found in the same<br>
> >><br>
> >> search<br>
> >><br>
> >> > order then CMAKE will use this variable to determine which to pick<br>
> >><br>
> >> first.<br>
> >><br>
> >> > Second, if a framework is found regardless of where it is in the<br>
> >> > search order it will be picked. I suspect the choice is the first<br>
> >> > one. However,<br>
> >><br>
> >> in<br>
> >><br>
> >> > my test I found that if I set CMAKE_FIND_FRAMEWORK to be "LAST" then<br>
> >><br>
> >> CMAKE<br>
> >><br>
> >> > picks the proper path. This would make me think the second option is<br>
> >> > at<br>
> >><br>
> >> play<br>
> >><br>
> >> > or it is just pure coincidence that this option happened to give me<br>
> >> > the correct result.<br>
> >> ><br>
> >> > Any of you know what the correct option is? To me it would make sense<br>
> >><br>
> >> that<br>
> >><br>
> >> > FIND_PATH honors the search order which would mean that the HINTS<br>
> >> > option<br>
> >><br>
> >> in<br>
> >><br>
> >> > FindQt4 should have higher precedence than the Framework in the<br>
> >> > CMAKE_SYSTEM_FRAMEWORK_PATH.<br>
> >><br>
> >> This cannot be answered without looking at the source code (as its not<br>
> >> documented properly) to check what exactly the algorithm does. That is<br>
> >> wether it iterates of the individual path in each of the steps and then<br>
> >> checks for framework and afterwards for standard headers in that path or<br>
> >> if it first checks all paths in a step for frameworks and then again<br>
> >> checks all paths for standard headers. Depending on which of the two it<br>
> >> is, the outcome of a find_path may depend on the order of the input<br>
> >> path-variables (like CMAKE_PREFIX_PATH) or not.<br>
> >><br>
> >> Andreas<br>
> >><br>
> >> --<br>
> >> You are the only person to ever get this message.<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<br>
> >> <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
> >><br>
> >> Please keep messages on-topic and check the CMake FAQ at:<br>
> >> <a href="http://www.cmake.org/Wiki/CMake_FAQ" target="_blank">http://www.cmake.org/Wiki/CMake_FAQ</a><br>
> >><br>
> >> Follow this link to subscribe/unsubscribe:<br>
> >> <a href="http://www.cmake.org/mailman/listinfo/cmake" target="_blank">http://www.cmake.org/mailman/listinfo/cmake</a><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>
Please keep messages on-topic and check the CMake FAQ at: <a href="http://www.cmake.org/Wiki/CMake_FAQ" target="_blank">http://www.cmake.org/Wiki/CMake_FAQ</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.cmake.org/mailman/listinfo/cmake" target="_blank">http://www.cmake.org/mailman/listinfo/cmake</a><br>
</div></div></blockquote></div><br></div></div></div>