<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Mar 21, 2014 at 9:45 AM, Vijay S. Mahadevan <span dir="ltr"><<a href="mailto:vijay.m@gmail.com" target="_blank">vijay.m@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Where is FindMOAB.cmake and how is that currently being used ? We<br>
could give you a template for usage but this depends on some other<br>
things detailed below.<br></blockquote><div><br></div><div>HI Vijay!</div><div><br></div><div>Here is our FindMOAB.cmake file: <a href="https://github.com/pyne/pyne/blob/staging/cmake/FindMOAB.cmake">https://github.com/pyne/pyne/blob/staging/cmake/FindMOAB.cmake</a></div>
<div>I am not sure if this is really sufficient.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
There are additions/fixes to the current CMake build system in the<br>
pipeline along with some major autoconf changes to enhance the current<br>
configuration capability. It is possible that the current<br>
MOABConfig.cmake file generated out of autoconf is insufficient to<br>
fully describe the configuration when used from downstream codes. I'll<br>
be merging the outstanding CMake changes (within the next week or so),<br>
which will hopefully fix some simple configuration issues. </blockquote><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
I can also create a FindMOAB.cmake for consumption by other codes using MOAB if<br>
that will be useful.<br></blockquote><div><br></div><div>This would be super useful! We would use this immediately. Thanks!<br><br></div><div>Be Well</div><div>Anthony</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<span class=""><font color="#888888"><br>
Vijay<br>
</font></span><div class=""><div class="h5"><br>
<br>
On Thu, Mar 20, 2014 at 10:50 PM, Anthony Scopatz <<a href="mailto:scopatz@gmail.com">scopatz@gmail.com</a>> wrote:<br>
><br>
> On Sat, Mar 15, 2014 at 4:52 PM, Andrew Davis <<a href="mailto:andrewdavis.davis@gmail.com">andrewdavis.davis@gmail.com</a>><br>
> wrote:<br>
>><br>
>> Comping with verbose mode suggests that headers variable is not set<br>
>> correctly<br>
>><br>
>> cd /data/opt/pyne/build/pyne && /usr/bin/c++ -D_dagmc_EXPORTS<br>
>> -D__LINUX__ -DJSON_IS_AMALGAMATION -O3 -DNDEBUG -fPIC<br>
>> -I/data/opt/dagmc/hdf5/include<br>
>> -I/usr/lib/python2.7/dist-packages/numpy/core/include -I/data/opt/pyne/cpp<br>
>> -I/usr/include/python2.7 -o CMakeFiles/_dagmc.dir/_dagmc.cxx.o -c<br>
>> /data/opt/pyne/build/pyne/_dagmc.cxx<br>
>><br>
><br>
>><br>
>> So is there somekind of mismatch between the MOAB_INCLUDE_DIRS env wanted<br>
>> by cmake/FindMOAB and the MOAB_INCLUDE_DIR suggested by the cmake build<br>
>> echo.<br>
><br>
><br>
> Hey Andy,<br>
><br>
> There very well might be. I am not super confident in the FindMOAB.cmake.<br>
> This seems like the thing that MOAB itself should support. Maybe they do and<br>
> I missed it when I wrote the dagmc wrapper. For expediency, I just used the<br>
> best thing that I found online. It could probably use love & official<br>
> support.<br>
><br>
> Be Well<br>
> Anthony<br>
><br>
>><br>
>><br>
>> Andy<br>
>><br>
>><br>
>><br>
>><br>
>> On Sat, Mar 15, 2014 at 4:44 PM, Andrew Davis<br>
>> <<a href="mailto:andrewdavis.davis@gmail.com">andrewdavis.davis@gmail.com</a>> wrote:<br>
>>><br>
>>> Can anyone confirm is this is true? When I try it I get the following<br>
>>><br>
>>> python setup.py install --user --<br>
>>> -DMOAB_INCLUDE_DIR=/data/opt/dagmc/moab/include<br>
>>> -DMOAB_LIBRARY=/data/opt/dagmc/moab/lib/libMOAB.so<br>
>>><br>
>>> It finds MOAB,<br>
>>><br>
>>> -- Found MOAB: /data/opt/dagmc/moab/lib/libMOAB.so<br>
>>> -- MOAB header files: /data/opt/dagmc/moab/include<br>
>>> -- MOAB library: /data/opt/dagmc/moab/lib/libMOAB.so<br>
>>> -- MOAB Found: TRUE<br>
>>><br>
>>> Then fails during build<br>
>>><br>
>>> /data/opt/pyne/build/pyne/_dagmc.cxx:322:26: fatal error: moab/Types.hpp:<br>
>>> No such file or directory<br>
>>> #include "moab/Types.hpp"<br>
>>> ^<br>
>>> compilation terminated.<br>
>>> make[2]: *** [pyne/CMakeFiles/_dagmc.dir/_dagmc.cxx.o] Error 1<br>
>>> make[1]: *** [pyne/CMakeFiles/_dagmc.dir/all] Error 2<br>
>>> make: *** [all] Error 2<br>
>>> Traceback (most recent call last):<br>
>>> File "setup.py", line 106, in <module><br>
>>> main()<br>
>>> File "setup.py", line 100, in main<br>
>>> main_body()<br>
>>> File "setup.py", line 91, in main_body<br>
>>> rtn = subprocess.check_call(['make'] + make_args, cwd='build')<br>
>>> File "/usr/lib/python2.7/subprocess.py", line 540, in check_call<br>
>>> raise CalledProcessError(retcode, cmd)<br>
>>> subprocess.CalledProcessError: Command '['make']' returned non-zero exit<br>
>>> status 2<br>
>>><br>
>>> My MOAB is setup correctly, this is a fresh pull from staging, I can<br>
>>> confirm that the header is where it should be.<br>
>>><br>
>>> Any ideas?<br>
>>><br>
>>> Thanks<br>
>>><br>
>>> Andy<br>
>>><br>
>>><br>
>>> On Mon, Mar 10, 2014 at 1:31 PM, Elliott Biondo <<a href="mailto:Biondo@wisc.edu">Biondo@wisc.edu</a>> wrote:<br>
>>>><br>
>>>> I actually ran into this last week. Anthony helped me with the cmake<br>
>>>> flags:<br>
>>>><br>
>>>> python setup.py install --user --<br>
>>>> -DMOAB_INCLUDE_DIR=/PATH/TO/MOAB/include<br>
>>>> -DMOAB_LIBRARY=/PATH/TO/MOAB/lib/libMOAB.so<br>
>>>><br>
>>>><br>
>>>> On Mon, Mar 10, 2014 at 12:42 PM, Matthew Gidden <<a href="mailto:gidden@wisc.edu">gidden@wisc.edu</a>><br>
>>>> wrote:<br>
>>>>><br>
>>>>> It will involve setting pyne's cmake flags, where the setup looks like<br>
>>>>><br>
>>>>> ```<br>
>>>>> setup.py install <python flags> -- <cmake flags><br>
>>>>> ```<br>
>>>>><br>
>>>>> You can see such an example in moab_build.sh in pyne-ci.<br>
>>>>><br>
>>>>><br>
>>>>> On Mon, Mar 10, 2014 at 12:41 PM, Paul Wilson <<a href="mailto:wilsonp@engr.wisc.edu">wilsonp@engr.wisc.edu</a>><br>
>>>>> wrote:<br>
>>>>>><br>
>>>>>> Hmmmm... I guess I can look in the pyne-ci repo... I'll do that.<br>
>>>>>><br>
>>>>>> Paul<br>
>>>>>><br>
>>>>>><br>
>>>>>> On 03/10/2014 12:31 PM, Paul Wilson wrote:<br>
>>>>>>><br>
>>>>>>> Hi all,<br>
>>>>>>><br>
>>>>>>> Do we have any install instructions that describe how to pass the<br>
>>>>>>> right path and variable info to build PyNE with MOAB? I don't see it at<br>
>>>>>>> <a href="http://pyne.io" target="_blank">pyne.io</a> or the README.<br>
>>>>>>><br>
>>>>>>> Paul<br>
>>>>>>><br>
>>>>>><br>
>>>>>> --<br>
>>>>>> -- ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~<br>
>>>>>> --<br>
>>>>>> Paul Wilson ~ UW-Madison ~ <a href="tel:608-263-0807" value="+16082630807">608-263-0807</a> ~ cal: <a href="http://bit.ly/pphw-cal" target="_blank">http://bit.ly/pphw-cal</a><br>
>>>>>> Professor, Engineering Physics. ~ <a href="http://cnerg.engr.wisc.edu" target="_blank">http://cnerg.engr.wisc.edu</a><br>
>>>>>> Faculty Director, Advanced Computing Infrastructure<br>
>>>>>><br>
>>>>>><br>
>>>>><br>
>>>>><br>
>>>>><br>
>>>>> --<br>
>>>>> Matthew Gidden<br>
>>>>> Ph.D. Candidate, Nuclear Engineering<br>
>>>>> The University of Wisconsin -- Madison<br>
>>>>> Ph. <a href="tel:225.892.3192" value="+12258923192">225.892.3192</a><br>
>>>>><br>
>>>>> --<br>
>>>>><br>
>>>>> ---<br>
>>>>> You received this message because you are subscribed to the Google<br>
>>>>> Groups "PyNE" group.<br>
>>>>> To unsubscribe from this group and stop receiving emails from it, send<br>
>>>>> an email to <a href="mailto:pyne-dev%2Bunsubscribe@googlegroups.com">pyne-dev+unsubscribe@googlegroups.com</a>.<br>
>>>>> For more options, visit <a href="https://groups.google.com/d/optout" target="_blank">https://groups.google.com/d/optout</a>.<br>
>>>><br>
>>>><br>
>>>><br>
>>>><br>
>>>> --<br>
>>>> Elliott D. Biondo<br>
>>>> Nuclear Regulatory Commission Fellow<br>
>>>> Computational Nuclear Engineering Research Group (CNERG)<br>
>>>> Department of Nuclear Engineering and Engineering Physics<br>
>>>> University of Wisconsin - Madison<br>
>>>><br>
>>>> 434 Engineering Research Building<br>
>>>> 1500 Engineering Drive<br>
>>>> Madison, WI 53706<br>
>>>><br>
>>>> Calendar<br>
>>>><br>
>>>> --<br>
>>>><br>
>>>> ---<br>
>>>> You received this message because you are subscribed to the Google<br>
>>>> Groups "PyNE" group.<br>
>>>> To unsubscribe from this group and stop receiving emails from it, send<br>
>>>> an email to <a href="mailto:pyne-dev%2Bunsubscribe@googlegroups.com">pyne-dev+unsubscribe@googlegroups.com</a>.<br>
>>>> For more options, visit <a href="https://groups.google.com/d/optout" target="_blank">https://groups.google.com/d/optout</a>.<br>
>>><br>
>>><br>
>><br>
>> --<br>
>><br>
>> ---<br>
>> You received this message because you are subscribed to the Google Groups<br>
>> "PyNE" group.<br>
>> To unsubscribe from this group and stop receiving emails from it, send an<br>
>> email to <a href="mailto:pyne-dev%2Bunsubscribe@googlegroups.com">pyne-dev+unsubscribe@googlegroups.com</a>.<br>
>> For more options, visit <a href="https://groups.google.com/d/optout" target="_blank">https://groups.google.com/d/optout</a>.<br>
><br>
><br>
</div></div></blockquote></div><br></div></div>