<div dir="ltr">Hal,<div> Also note that they are replicating the build from <a href="http://build.pl">build.pl</a> down to the exact order of source file compilation. So the question arises, to what degree is is it invalid to even glance at their Cmakelist.txt for overall ideas on how to do this. Considering that they are simply emitting the same build commands as <a href="http://build.pl">build.pl</a> (to which we already have license), I imagine we would have to code in a very similar manner even if done from scratch, i.e., use instances of add_custom_command to manually emit the same <a href="http://build.pl">build.pl</a> commands. There probably aren't that many ways to code that in cmake.</div>
<div> Jack</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, May 30, 2014 at 7:10 PM, Jack Howarth <span dir="ltr"><<a href="mailto:howarth.mailing.lists@gmail.com" target="_blank">howarth.mailing.lists@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hal,<div> Even if that is problematic, starting over is fairly straight-forward. Their CMakelists.txt is simply a directly repetition of the commands emitted from the build as done by <a href="http://build.pl" target="_blank">build.pl</a>. So if they are difficult about it, just take a printout of the output for the current build with 'make compiler=clang" and code the Cmakelist.txt from that. If you look carefully, you will see that they are replicating this down to the exact order of the parameters on the compiler calls. It is very difficult to see how that could be intellectual property in any fashion since replicating the output of the <a href="http://build.pl" target="_blank">build.pl</a> currently in <a href="http://llvm.org" target="_blank">llvm.org</a>'s openmp results in the same ordering. Note that their files are only a crude starting point and nowhere near what we will need for llvm.</div>
<span class="HOEnZb"><font color="#888888">
<div> Jack</div></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, May 30, 2014 at 6:40 PM, Hal Finkel <span dir="ltr"><<a href="mailto:hfinkel@anl.gov" target="_blank">hfinkel@anl.gov</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Jack,<br>
<br>
Before you go too far with this, do we have Pathscale's explicit contribution of their build files? (I've cc'd C. Bergstrom so that he can comment directly).<br>
<br>
Thanks,<br>
Hal<br>
<div><div><br>
----- Original Message -----<br>
> From: "Jack Howarth" <<a href="mailto:howarth.mailing.lists@gmail.com" target="_blank">howarth.mailing.lists@gmail.com</a>><br>
> To: <a href="mailto:openmp-dev@dcs-maillist2.engr.illinois.edu" target="_blank">openmp-dev@dcs-maillist2.engr.illinois.edu</a><br>
> Sent: Friday, May 30, 2014 5:28:33 PM<br>
> Subject: [Openmp-dev] (no subject)<br>
><br>
><br>
><br>
> Attached is a first pass at modifying the cmakefiles from<br>
> <a href="https://github.com/pathscale/openmprtl/blob/master/itt/libomp_oss" target="_blank">https://github.com/pathscale/openmprtl/blob/master/itt/libomp_oss</a> to<br>
> build openmp. I noticed that the existing <a href="http://build.pl" target="_blank">build.pl</a> doesn't actually<br>
> build a fat shared library on darwin. The attached changes can does<br>
> this in an indirect fashion with…<br>
><br>
><br>
> % cd runtime<br>
> % mkdir build_32<br>
> % cd build_32<br>
> % cmake -DARCH="32" ..<br>
> % make VERBOSE=1<br>
> % cd ..<br>
> % mkdir build_32e<br>
> % cmake -DARCH="32e" ..<br>
> % make VERBOSE=1<br>
> % cd ..<br>
> % lipo ./build_32/src/libiomp5.dylib ./build_32e/src/libiomp5.dylib<br>
> -create -o libiomp5.dylib<br>
> % file libiomp5.dylib<br>
><br>
> libiomp5.dylib: Mach-O universal binary with 2 architectures<br>
> libiomp5.dylib (for architecture x86_64): Mach-O 64-bit dynamically<br>
> linked shared library x86_64<br>
> libiomp5.dylib (for architecture i386): Mach-O dynamically linked<br>
> shared library i386<br>
><br>
><br>
> Normally we could do this in cmake by passing '-arch i386 -arch<br>
> x86_64' but use of assembly code in the build gums that up.<br>
</div></div>> _______________________________________________<br>
> Openmp-dev mailing list<br>
> <a href="mailto:Openmp-dev@dcs-maillist2.engr.illinois.edu" target="_blank">Openmp-dev@dcs-maillist2.engr.illinois.edu</a><br>
> <a href="http://lists.cs.uiuc.edu/mailman/listinfo/openmp-dev" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/openmp-dev</a><br>
><br>
<span><font color="#888888"><br>
--<br>
Hal Finkel<br>
Assistant Computational Scientist<br>
Leadership Computing Facility<br>
Argonne National Laboratory<br>
</font></span></blockquote></div><br></div>
</div></div></blockquote></div><br></div>