We run into a JIT failure when I do this on Linux I believe due to the way ELF forwards symbols (and my needing to work around it). I still need to bump the version check in CMake. On Jul 22, 2016, at 1:31 PM, Michael Gottesman wrote: Swift-dev mailing where do I find the "starter bugs for the humanities" how-to section? Is there a checklist that goes beyond fix this code and explains tests, comments, etc? On Jul 20, 2016, at 2:07 PM, Erica Sadun via swift-dev > wrote: On Jul 21, 2016, at 9:37 AM, Arnold Schwaighofer > wrote: On Jul 21, 2016, at 11:53 PM, Erica Sadun via swift-dev > wrote: I deleted a very old /usr/local/bin/cmake and linked /usr/local/bin/cmake to /Applications/CMake.app/Contents/bin/cmake. So I got a successful build, and your suspicion was right. On Jul 22, 2016, at 12:26 PM, Erica Sadun via swift-dev wrote: If that was set, you would have gotten a nice error saying you needed to upgrade your cmake. Swift-dev mailing mailing is partially my fault TBH. On Jul 21, 2016, at 11:53 PM, Erica Sadun via swift-dev wrote: Thank you all for pointing me in the right direction. Git clone GitHub - apple/swift: The Swift Programming Language I deleted everything (including my github fork), and started with fresh cloning: Now when I `where cmake`, every possible candidate is 3.6. Swift-dev mailing I got a successful build, and your suspicion was right. On Jul 21, 2016, at 9:37 AM, Arnold Schwaighofer wrote: ninja check-clang This will run the clang tests. \llvm ninja clang This will build just clang. On Jul 21, 2016, at 8:37 AM, Arnold Schwaighofer via swift-dev wrote: set CCcl (necessary to force CMake to choose MSVC over mingw GCC if you have it installed) set CXXcl cmake -GNinja -DLLVMENABLEPROJECTSclang. Anyone able to give me some pointers to get past this? Configuring incomplete, errors occurred! Provides a separate development package or SDK, be sure it has beenĬmake/modules/SwiftSharedCMakeConfig.cmake:212 (swift_common_standalone_build_config_clang)ĬMakeLists.txt:398 (swift_common_standalone_build_config) ![]() "Clang_DIR" to a directory containing one of the above files. To do `export PATH=/Applications/CMake.app/Contents/bin:$PATH`,ĬMake Error at cmake/modules/SwiftSharedCMakeConfig.cmake:155 (find_package):Ĭould not find a package configuration file provided by "Clang" with any ofĪdd the installation prefix of "Clang" to CMAKE_PREFIX_PATH or set Usage This variable can be set by the user during the first time a build tree is configured. Once set, you can not change this variable. This is the command that will be used as the compiler. I started with an absolutely clean re-clone, used bash (normally I use tcsh), made sure Documentation CMAKECOMPILER The full path to the compiler for LANG.On Jul 20, 2016, at 2:07 PM, Erica Sadun via swift-dev wrote: I think we started requiring some 3ish version recently. What is the version of your cmake install? I canât find the UNIX variable in the CMake files: how should I set it? I tried running CMake like cmake -DLLVM_ENABLE_PROJECTS=clang -DCMAKE_BUILD_TYPE=Debug -DLLVM_USE_LINKER=lld -DLLVM_PARALLEL_LINK_JOBS=1 -G "Ninja" -B. Alternate clangd binary: set the clangd.path string in settings.json. Command-line flags: these can be passed in the clangd.arguments array in your settings.json. MESSAGE(SEND_ERROR "Unable to determine platform") // <- HERE Debug logs: when clangd is running, you should see Clang Language Server in the dropdown of the Output panel (View-> Output).However, when building, CMake complains CMake Error at /home/alessandro/tesi/LLVM-embedded-toolchain-for-Arm/repos/llvm-project/llvm/cmake/modules/HandleLLVMOptions.cmake:150 (MESSAGE): ![]() ![]() I separately cloned the LLVM repo as instructed (Iâm on tag llvmorg-16.0.0, commit 08d094a0e457). ![]() Iâm trying to build the LLVM-embedded-toolchain-for-Arm.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |