similar to: [LLVMdev] Bug in CMake Xcode projects

Hello, Here's a tiny patch to the VMKIT tools makefile, that allows you to build VMKIT without both Java and CLI. I'm working on a new bytecode front end so wanted a 'clean' mvm without building to two existing front ends. Currently it still tries to build VMJC even when its told not to build the JNJVM. This patch fixes that. Index: tools/Makefile

Hi Dean, Applies thanks! Out of curiosity, which part of mvm are you using? I guess the GC? Nicolas Dean Calver wrote: > Hello, > > Here's a tiny patch to the VMKIT tools makefile, that allows you to > build VMKIT without both Java and CLI. I'm working on a new bytecode > front end so wanted a 'clean' mvm without building to two existing > front ends.

Hi all 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. Unfortunately, after running cmake in the usual way, I found that many xcode schemes are missing on the resulting project. Particularly, I added -DLLVM_ENABLE_PROJECTS=clang to the terminal command line. The logs correctly state that ‘clang

I've been using make to build llvm but use Xcode for most other projects I work on. I decided to try running cmake to build an xcode project for llvm. The results were disappointing. The generated xcode project does not encode that executables link with static libraries. Instead, the static libraries are snuck in under "Other linker flags", then some pre- and post- scripts on

----- Original Message ---- > From: Óscar Fuentes <ofv at wanadoo.es> > To: Samuel Crow <samuraileumas at yahoo.com> > Cc: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> > Sent: Wed, January 5, 2011 5:00:00 PM > Subject: Re: Build problems and workarounds with CMake and XCode > > Samuel Crow <samuraileumas at yahoo.com> writes: > >

Samuel Crow <samuraileumas at yahoo.com> writes: [snip] > I tried making a separate build of LLVM SVN in XCode using build files created > with CMake. Surprisingly, it worked better than Eclipse! The Build_All target > completed its build. The install target was another story though. First of > all, the commands to install with the terminal command-line needed to be

Hello everyone, I finally gave up on trying to build under Eclipse on my Mac because I had a non-functioning installation on there that kept intercepting the command line entries on the path. Uninstalling the old MacPorts install of LLVM 2.6 helped but not completely. I tried making a separate build of LLVM SVN in XCode using build files created with CMake. Surprisingly, it worked better

Hi Samuel, I always just click the icon for CMake on the Mac. Then you select a destination directory for the headers from the graphical user interface and the source where the cmakefile.txt root is. Then you click on the configure button at the bottom. It will ask you if you want to make Unix Makefiles or XCode Projects or Eclipse Projects or a couple of other options. Pick the one you

Hi, In another post I was trying to find out how to use libc++ instead of libstdc++ when compiling llvm/clang. I couldnt find the a way to tell cmake to do that. So I switched to using configure to compile llvm/clang. But now I find that the artifacts produced are different. Here are the issues I see: - configure doesnt seem to respect '--prefix' option, it just puts

Hi Oscar, I tried that but it didn't work. However, it did work fine on Linux for me so I am now a bit confused. Here is the output from $ sudo make install Install the project... -- Install configuration: "Release" -- Installing: /usr/local/llvm-2.8/lib/libLLVMSupport.a -- Installing: /usr/local/llvm-2.8/lib/libLLVMSystem.a -- Installing: /usr/local/llvm-2.8/lib/libLLVMCore.a --

Hi! I'm trying to crosscompile llvm/clang to run Windows. But the compilation fails: gmake[2]: Entering directory `/usr/home/solskogen/obj/_build/llvm.native.x86_64-w64-mingw32/tools/lli' llvm[2]: Linking Release executable lli (without symbols) x86_64-w64-mingw32-g++ -I/usr/home/solskogen/mingw-w64-builder/bin/llvm/include -I/usr/home/solskogen/mingw-w64-builder/bin/llvm/tools/lli

What is the difference between Speex. xcodeproj and Speex_UB.xcodeproj? In building the Speex framework, I noticed that Speex_UB.xcodeproj is including several files that don't exist anymore as well as missing files that were added since it was last updated. Also, modes_wb.c is not included in either framework project which causes a link error when I call speex_lib_get_mode().

The new cmake 3.7.0-rc1 release produces a stage2 bootstrap failure in openmp project build on OS X 10.11 under Xcode 8.... In file included from /sw/src/fink.build/llvm40-4.0.0-1/llvm-4.0.0.src/projects/openmp/runtime/src/kmp_alloc.c:16: In file included from /sw/src/fink.build/llvm40-4.0.0-1/llvm-4.0.0.src/projects/openmp/runtime/src/kmp.h:98:

Hi, If you create an Xcode project with cmake -G Xcode ~/llvm and do a build, you end up with 68 warnings like this: -mdynamic-no-pic overrides -fpic or -fPIC This can be easily avoided doing: cmake -G Xcode -ULLVM_ENABLE_PIC ~/llvm But I think it would be nicer if it built warning-free with the simpler form. What do you think? Ray PS: CMake generated make style builds on

Hi, thanks for your answer. I confirm, mitigate this issue is very very easy. There are other issues with high severity for example CVE-2019-17558. Description: Apache Solr 5.0.0 to Apache Solr 8.3.1 are vulnerable to a Remote Code Execution through the VelocityResponseWriter I think for this issue there is only a solution, upgrade Solr to 8.4. It's Correct? So, with Dovecot is it possible

Hi, I am trying to use the new LLVM-2.7 release in Xcode for my analysis and development. However, I do not see the top level Xcode directory as in LLVM-2.6. Can someone tell me how to develop on top of LLVM-2.7 using Xcode? Best Regards, Raj

Jonathan Ragan-Kelley <katokop1 <at> gmail.com> writes: > > Slightly off-topic, but I imagine this crowd must have some experience > using Xcode 4 for projects linking to LLVM. I've actually started > using Xcode 4 as an IDE for C/C++ development thanks to the vastly > improved code analysis-based tools it's inherited largely thanks to > LLVM. But,

Downloaded Xcode 4.3 for Lion from the app store, and am following the tutorial for installing wine: http://www.davidbaumgold.com/tutorials/wine-mac/ When I get to part 3 and it tells me to type the following code into terminal Code: $ sudo port install wine I get the following message: Code: xxx-xxx-macbook-pro:~ Kaoss$ sudo port install wine Password: Warning: xcodebuild exists but

On Oct 7, 2008, at 12:40 AM, Cloud Strife wrote: > Hi everyone. > I am using Mac OS X to inspect the llvm source code. > Although the make command works perfectly when compiling the source > code, the Xcode tool prompted me: > > Makefile:26: Makefile.config: No such file or directory > Makefile:58: /Makefile.rules: No such file or directory > > I downloaded the latest

Hey, My projects are not compiling on 10.5 using llvm-gcc 4.2 in Xcode 3.1.4. These are caused by some llvm bugs that are now fixed. Since Apple will not release a Xcode update for 10.5, I am trying to compile a recent version of llvm-gcc 4.2 (from the LLVM 2.7 branch - but I could use ToT if this helps) to use on 10.5 intel. I easily built llvm-gcc-4.2 on 10.5 intel by following the README.LLVM