<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Apr 18, 2017, at 11:20 AM, Chris Bieneman via cfe-dev <<a href="mailto:cfe-dev@lists.llvm.org" class="">cfe-dev@lists.llvm.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=us-ascii" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Those instructions for building libcxx are a bit out of date and incomplete.<div class=""><br class=""></div><div class="">If you are planning to develop and build libcxx you'll need a checkout and build of LLVM. That is required for running libcxx's tests. </div></div></div></blockquote><div><br class=""></div><div>The libc++ bot does not checkout LLVM: <a href="http://green.lab.llvm.org/green/view/Libcxx/job/libcxx_master_cmake/" class="">http://green.lab.llvm.org/green/view/Libcxx/job/libcxx_master_cmake/</a></div><div><br class=""></div><div>It is checking out libc++ and lit (`svn checkout <a href="http://llvm.org/svn/llvm-project/llvm/trunk/utils/lit%60" class="">http://llvm.org/svn/llvm-project/llvm/trunk/utils/lit`</a>), then run cmake, and the tests can be ran with `python path/to/lit/lit.py -v --show-xfail --show-unsupported $WORKSPACE/build/test`</div><div><br class=""></div><div>I have a patch in review to run the tests against a pre-built libc++.</div><div><br class=""></div><div>— </div><div>Mehdi</div><div><br class=""></div><div><br class=""></div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">After you've built LLVM on your system, one of the generated tools is a program called llvm-config. When you run CMake for libcxx you need to set the CMake option "LLVM_CONFIG_PATH" to point to the llvm-config binary, and libcxx's build system should handle the rest. Libcxx is not tightly bound to LLVM, so when developing libcxx you will not need to update the LLVM sources frequently.</div><div class=""><br class=""></div><div class="">If you just want to build and use libcxx, specifying the LLVM_CONFIG_PATH or LLVM_PATH variables are not required, in the absence of an LLVM source and build tree libcxx will disable the testing functionality in the build, but everything else should work.<br class=""><div class=""><div class=""><br class=""></div><div class="">-Chris</div><div class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Apr 18, 2017, at 8:35 AM, Nico Weber via cfe-dev <<a href="mailto:cfe-dev@lists.llvm.org" class="">cfe-dev@lists.llvm.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Erika: On some Linux distributions, if you want to use the distributions's package manager, you need to install package "ninja-build" since "ninja" is some ancient database iirc. See <a href="https://github.com/ninja-build/ninja/wiki/Pre-built-Ninja-packages" class="">https://github.com/ninja-build/ninja/wiki/Pre-built-Ninja-packages</a><div class=""><br class=""></div><div class="">`ninja --help` should print something like this:</div><div class=""><div class="">$ ninja --help</div><div class="">usage: ninja [options] [targets...]</div><div class=""><br class=""></div><div class="">if targets are unspecified, builds the 'default' target (see manual).</div><div class=""><br class=""></div><div class="">options:</div><div class=""> --version print ninja version ("1.7.2")</div><div class=""><br class=""></div><div class=""> -C DIR change to DIR before doing anything else</div><div class=""> -f FILE specify input build file [default=build.ninja]</div><div class=""><br class=""></div><div class=""> -j N run N jobs in parallel [default=10, derived from CPUs available]</div><div class=""> -k N keep going until N jobs fail [default=1]</div><div class=""> -l N do not start new jobs if the load average is greater than N</div><div class=""> -n dry run (don't run commands but act like they succeeded)</div><div class=""> -v show all command lines while building</div><div class=""><br class=""></div><div class=""> -d MODE enable debugging (use -d list to list modes)</div><div class=""> -t TOOL run a subtool (use -t list to list subtools)</div><div class=""> terminates toplevel options; further flags are passed to the tool</div><div class=""> -w FLAG adjust warnings (use -w list to list warnings)</div></div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Tue, Apr 18, 2017 at 10:18 AM, Brian Cain via cfe-dev <span dir="ltr" class=""><<a href="mailto:cfe-dev@lists.llvm.org" target="_blank" class="">cfe-dev@lists.llvm.org</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote"><div class="">Bringing this thread back onto the list, looks like we went off list at some point.</div><div class=""> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="m_-5906474004150077820gmail-HOEnZb"><div class="m_-5906474004150077820gmail-h5"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="m_-5906474004150077820gmail-m_-4991655120434373639HOEnZb"><div class="m_-5906474004150077820gmail-m_-4991655120434373639h5"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="m_-5906474004150077820gmail-m_-4991655120434373639m_4374003061014107539m_3348615170357721056HOEnZb"><div class="m_-5906474004150077820gmail-m_-4991655120434373639m_4374003061014107539m_3348615170357721056h5"><div class="gmail_extra"><div class="gmail_quote">On Apr 17, 2017 10:51 PM, "Erika Butler" <<a href="mailto:beneficii@gmail.com" target="_blank" class="">beneficii@gmail.com</a>> wrote:<br type="attribution" class=""><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr" class="">It's version 2.3 of ninja. This is the latest I could find for Windows.<div class=""><br class=""></div><div class="">I can't find the cmake version, but it was built on April 10, 2017, so I think that's new enough.</div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">2017-04-17 20:46 GMT-07:00 Brian Cain <span dir="ltr" class=""><<a href="mailto:brian.cain@gmail.com" target="_blank" class="">brian.cain@gmail.com</a>></span>:<br class=""><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto" class="">Not sure. Are you certain your version of ninja and cmake are new enough?</div><div class="m_-5906474004150077820gmail-m_-4991655120434373639m_4374003061014107539m_3348615170357721056m_-6616400841576022024m_-4752073125759043091HOEnZb"><div class="m_-5906474004150077820gmail-m_-4991655120434373639m_4374003061014107539m_3348615170357721056m_-6616400841576022024m_-4752073125759043091h5"><div class="gmail_extra"><br class=""><div class="gmail_quote">On Apr 17, 2017 10:38 PM, "Erika Butler" <<a href="mailto:beneficii@gmail.com" target="_blank" class="">beneficii@gmail.com</a>> wrote:<br type="attribution" class=""><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr" class="">I added the Ninja directory to my PATH variable and reopened the admin Command Prompt. I changed CMAKE_MAKE_PROGRAM to this:<div class=""><br class=""></div><div class="">-DCMAKE_MAKE_PROGRAM=ninja<br class=""></div><div class=""><br class=""></div><div class="">I executed the command again, Ninja still reported an error, now saying in ninja.exe.log:</div><div class=""><br class=""></div><div class=""><div class="">usage: ninja [-h] [-f file [file ...]] [-l lineno [lineno ...]]</div><div class=""> [-p project [project ...]] [--plugin plugin [plugin ...]]</div><div class=""> [--loglevel loglevel] [--logfile logfile]</div><div class=""> [file [file ...]]</div><div class="">ninja: error: unrecognized arguments: --version</div></div><div class=""><br class=""></div><div class="">It seems cmake wants to pass a "--version" argument to its command to open ninja, which causes ninja to complain.</div><div class=""><br class=""></div><div class="">What can I do?</div><div class=""></div></div></blockquote></div></div></div></div></blockquote></div></div></blockquote></div></div></div></div></blockquote></div></div></blockquote></div></div></div></div></blockquote></div></div></div></div></blockquote></div><div class="gmail_extra"><br class=""></div><div class="gmail_extra"><br class=""></div><div class="gmail_extra">My ninja version is 1.3.4 and when I run "ninja --version" it reports "1.3.4". It does not give this error message. When I run "ninja --help" it shows something very different from the help message you're showing here.</div><div class="gmail_extra"><br class=""></div><div class="gmail_extra"><a href="https://ninja-build.org/" target="_blank" class="">https://ninja-build.org/</a> claims that the latest version available is "The last Ninja release is v1.7.2, released 7 Nov 2016." But you said you have version 2.3.<br class=""></div><div class="gmail_extra"><br class=""></div><div class="gmail_extra">I think that you have another executable called "ninja" in your PATH. Can you check it? See if you get different results with binaries from here -- <a href="https://github.com/ninja-build/ninja/releases" target="_blank" class="">https://github.com/ninja-<wbr class="">build/ninja/releases</a><br class=""></div></div><div class="gmail_extra"><br class=""><div class="m_-5906474004150077820gmail_signature">-Brian</div>
</div></div>
<br class="">______________________________<wbr class="">_________________<br class="">
cfe-dev mailing list<br class="">
<a href="mailto:cfe-dev@lists.llvm.org" class="">cfe-dev@lists.llvm.org</a><br class="">
<a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev" rel="noreferrer" target="_blank" class="">http://lists.llvm.org/cgi-bin/<wbr class="">mailman/listinfo/cfe-dev</a><br class="">
<br class=""></blockquote></div><br class=""></div>
_______________________________________________<br class="">cfe-dev mailing list<br class=""><a href="mailto:cfe-dev@lists.llvm.org" class="">cfe-dev@lists.llvm.org</a><br class=""><a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev" class="">http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev</a><br class=""></div></blockquote></div><br class=""></div></div></div></div>_______________________________________________<br class="">cfe-dev mailing list<br class=""><a href="mailto:cfe-dev@lists.llvm.org" class="">cfe-dev@lists.llvm.org</a><br class="">http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev<br class=""></div></blockquote></div><br class=""></body></html>