<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hey Joan,<div class=""><br class=""></div><div class="">CMake's support for generating Xcode schemes is fairly new (CMake 3.9 added it). If no schemes are generated by CMake (and LLVM's build is not configured to generate them by default), Xcode should prompt when it first opens the project to auto-generate schemes for each target.</div><div class=""><br class=""></div><div class="">WRT this specific issue, I honestly have no idea what would cause it. Possibly a bug in CMake, possibly something that changed in LLVM.</div><div class=""><br class=""></div><div class="">All of these issues that you are having using Xcode are the byproduct of the lack of any contributors in LLVM who care about using Xcode as their build generator. You seem to care a lot about it. Our community would greatly benefit from having someone who cares willing to contribute patches and work on improving Xcode build support.</div><div class=""><br class=""></div><div class="">Thanks,</div><div class="">-Chris</div><div class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Jul 26, 2019, at 9:56 AM, Joan Lluch via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Ok, I am replying to myself.<div class=""><br class=""></div><div class="">I saved the xcode xcuserdata folder in a safe place and trashed the entire ‘buid’ and ‘install’ directories (deleting cmakecache alone was not helpful). Ran again the cmake command. Copied the saved xcuserdata folder to its previous place, and boom, incidentally everything appeared just right on the newly created xcode project. It complied just fine, and as a bonus I’m now getting very fast incremental compiles.</div><div class=""><br class=""></div><div class="">So now the issue is solved but I don’t know why cmake messed up the previous xcode project when I ran it on the existing build directory. </div><div class=""><br class=""></div><div class="">I assume we are supposed to simply pull remote changes, merge them to our own working branch (which in my case contains an additional custom backend) and then simply run cmake on top of it, rather than recreating everything every time. Is this right, or am I missing some step?.</div><div class=""><br class=""></div><div class="">Thanks,</div><div class=""><br class=""></div><div class="">Joan</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On 26 Jul 2019, at 11:52, Joan Lluch via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi all<div class=""><br class=""></div><div class="">In order to get ready for the upcoming final 9.0 release code I have now switched to the 'release/9.x' branch that I pulled from github.</div><div class=""><br class=""></div><div class="">Unfortunately, after running cmake in the usual way, I found that many xcode schemes are missing on the resulting project.</div><div class=""><br class=""></div><div class="">Particularly, I added -DLLVM_ENABLE_PROJECTS=clang to the terminal command line. The logs correctly state that ‘clang project is enabled’. However, the ‘clang’ schema, and anything related with clang, is completely missing in the generated xcode project, so clang can’t be compiled.</div><div class=""><br class=""></div><div class="">This is the full command line that I used from the 'llvm-project/build' directory:</div><div class=""><br class=""></div><div class=""><div style="margin: 0px; font-size: 10px; line-height: normal; font-family: Monaco; background-color: rgb(255, 255, 255);" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">cmake -G Xcode -DCMAKE_INSTALL_PREFIX=/Users/joan/LLVM-9/install -DLLVM_OPTIMIZED_TABLEGEN=On -DLLVM_ENABLE_PROJECTS="clang" ../llvm</span></div></div><div class=""><br class=""></div><div class="">I know that the quick reply to my issue is: 'just use Ninja’, but I have already replied to that in the past. My work on LLVM+clang to create a compiler backend is essentially completed and the compiler is just a small part of a bigger project. I need to dedicate time now to something else. I am increasingly disappointed that something that worked fine, just keeps breaking every time I pull changes from the remote repo, by not being able to even compile it.</div><div class=""><br class=""></div><div class="">So, please, can anybody give me a clue on what can be wrong now with LLVM and xcode, and a possible workaround?</div><div class=""><br class=""></div><div class="">Thanks in advance.</div><div class=""><br class=""></div><div class="">John</div></div>_______________________________________________<br class="">LLVM Developers mailing list<br class=""><a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a><br class=""><a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" class="">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br class=""></div></blockquote></div><br class=""></div></div>_______________________________________________<br class="">LLVM Developers mailing list<br class=""><a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a><br class="">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev<br class=""></div></blockquote></div><br class=""></div></body></html>