similar to: [LLVMdev] Building pass out of source with cmake: undefined symbol error

Still no go. I'm going to experiment building out of source manually with the cmake build and autotools build. I should've mentioned that I'm attempting this with the hello world pass example. ________________________________ From: llvmdev-bounces at cs.uiuc.edu [llvmdev-bounces at cs.uiuc.edu] on behalf of Charles Jacobsen [charlie.jacobsen at utah.edu] Sent: Friday, June 14, 2013

Hmmm, I just thought of something. Perhaps I need to set the MODULE cmake flag (via -DMODULE=ON)? I will try this today. (I remembered the LOADABLE_MODULE=1 flag in the makefile, and the if ( MODULE ) check in the AddLLVM cmake module.) ________________________________ From: llvmdev-bounces at cs.uiuc.edu [llvmdev-bounces at cs.uiuc.edu] on behalf of Charles Jacobsen [charlie.jacobsen at

Ah! Think I figured it out -- it's rtti. When I build with -fno-rtti, the spurious symbol disappears. Blargh, that was complicated. I'm going to try an out-of-source cmake build now. So far this has been a soliloquy, hope it helps someone else. ________________________________ From: llvmdev-bounces at cs.uiuc.edu [llvmdev-bounces at cs.uiuc.edu] on behalf of Charles Jacobsen

When I see one book about llvm and choose the building method between autotools, cmake, and ninja building methods, I was confused. Is there any link about this content? Thanks for reply. -- My best regards to you. No System Is Safe! mudongliang

Hi, It looks like cmake currently defaults to no optimization, which I think is a bit unexpected for most users. I don't know how to do that in cmake, but it would be good to default to a "release" build with optimizations. Can you have a patch to do that? Also, is there a way to manually add flags to the compiler (like setting CFLAGS with autotools)? Cheers, Jean-Marc On

Thanks, it applies now. I think you'd also want to add some (all?) of these files to EXTRA_DIST in Makefile.am, otherwise your cmake files won't be included in release tarballs, which are generate using "make dist". To test, you should try running run "make dist" to generate a tarball yourself. From there, you try building the contents with your cmake files and see if

Hi Mark, Thanks for the feedback. By default CMake is building the static library in debug, to get other things one has to explicit turn it on. To build in release mode for CMake you use the following flag: -DCMAKE_BUILD_TYPE=Release https://cmake.org/cmake/help/latest/variable/CMAKE_BUILD_TYPE.html CMAKE_BUILD_TYPE — CMake 3.14.1

Hi Marcus, There seems to be a conflict between the autotools-created config.h.in and the same file added by your patch. Any way you can use use a different name? Cheers, Jean-Marc On 04/02/2019 01:39 AM, Marcus Asteborg wrote: > Hi, > > > Here is a proposal for adding CMake in addition of Autotools. > > > See the attached patch for changes or the pull request here:

On Sun, Oct 09, 2016 at 10:01:43PM +0800, Cong Monkey wrote: > Will tinc use cmake in the future? auto tools is really hard to port > to other platform like windows phone. I don't know. At the moment, I'm quite happy with autotools; it works very well on all the platforms tinc currently supports (Linux, *BSD, Windows, Mac OS/X, Android), does cross-compiling very well, comes with a

I tried the new cmake-based build system to build Opus on Linux and macOS. I'm not familiar with cmake but based on instructions I found online I used it as follows: - mkdir build - cd build - cmake -DCMAKE_INSTALL_PREFIX:PATH=<install-path> .. - make - ctest - make install Although the "make" command completed, it reported that optimizations were disabled:

I can't find a tinc work for no root android, so I try to port it to android by the right way. Auto tools does not integrate well with android studio ( cmake not too, but will work well in the future release)! 2016-10-09 22:16 GMT+08:00 Guus Sliepen <guus at tinc-vpn.org>: > On Sun, Oct 09, 2016 at 10:01:43PM +0800, Cong Monkey wrote: > >> Will tinc use cmake in the future?

@Chuck Robey Before you pass judgment on CMake quit using those existing makefiles or the configure scripts. They are NOT GENERATED BY CMAKE. Start by downloading CMAKE from http://cmake.org/ and continue the process outlined in the build instructions that we keep trying to tell you to use and you keep ignoring completely. Perhaps you didn't understand what I said earlier when I said we

Hi, Here is a proposal for adding CMake in addition of Autotools. See attached patch for changes or the pull request here: https://github.com/xiph/opus/pull/100 The CMake scripts are parsing the filelist from Autotools, so only one file list needs to be maintained. With this change the checked in Visual Studio solution can be removed and no longer need to be maintained and updated when

Hi Marcus, Thanks for the fixes. I did some more cmake build testing and encountered a few issues: The option -DFORTIFY_SOURCE=2 should be -D_FORTIFY_SOURCE=2, as the macro has a leading underscore. In the autotools build it defines this if it is not already defined (m4/ax_add_fortify_source.m4). When custom modes are not enabled, the cmake build is nevertheless installing the include file

On 03/11/2015 03:20 PM, Rafael Espíndola wrote: > On 11 March 2015 at 09:45, Renato Golin <renato.golin at linaro.org> wrote: >> On 11 March 2015 at 13:06, Rafael Espíndola <rafael.espindola at gmail.com> wrote: >>> So that we can drop autotools, which currently requires anyone wanting >>> to change the build to install an old version of autoconf, among other

Hi, Thanks for the quick feedback I have changed the name to avoid conflict. Attached is the updated patch. //Marcus ________________________________ From: Jean-Marc Valin <jmvalin at jmvalin.ca> Sent: Tuesday, April 2, 2019 00:07 To: Marcus Asteborg; opus at xiph.org Subject: Re: [opus] CMake support for Opus proposal (in addition to Autotools) Hi Marcus, There seems to be a conflict

I just tried cmake for the first time and it mostly worked. I had been using autotools to configure. With cmake configure environment when I try to do: make TESTSUITE=CodeGen/mblaze check it runs the whole test suite. Under autotools it would just run the mblaze tests. Is there an equivalent command in a camke configured environment or is this broken? I know nothing about cmake so I'm

Hi! When using LLVM there is a folder: llvm/projects/sample which contains a file structure aimed at developing own project. It seems it uses autotools. Is there anywhere such structure but cmake oriented? So I can use it to build my project as standalone project? I know I can make simple cmakes like in llvm/examples/... directories, but then I have to execute cmake from llvm source everytme I

On 2015-05-26 11:31 PM, Cristian Adam wrote: > Yes please. CMake support is somehow mandatory for any C/C++ project > nowadays. Fascinating. Do the Visual Studio projects it generates know how to invoke cmake to update themselves? > Death to autotools! But that's just my ignorance speaking :-) I don't like autotools _or_ cmake. Fortunately, I'm not libogg's only user...

On 11 March 2015 at 13:06, Rafael Espíndola <rafael.espindola at gmail.com> wrote: > So that we can drop autotools, which currently requires anyone wanting > to change the build to install an old version of autoconf, among other > pains. Having two build systems is a way bigger pain than someone > having to install cmake. Can you explain why we need to upgrade CMake to drop