similar to: [LLVMdev] Switching LLVM CMake build to use explicit dependencies, and completely removing implicit dependency re-generation

Kenneth Boyd <zaimoni at zaimoni.com> writes: >> I'm seeing a failure related to circular library references while >> building LLVM with CMake and MSYS. This didn't happen on the >> past. Building with the configure script works, so it seems something >> related to CMake. Do you have any insight on this? >> > I'll get back on this tonight or

Kenneth Boyd <zaimoni at zaimoni.com> writes: >>> * I am seeing desynchronization between the configure-generated >>> Makefiles and the CMakeFile.txt files. [e.g., llc; makefile doesn't >>> have asmprinter, CMakeFile.txt does]. That much I should be able to >>> construct a patch for "blind", if no-one gets to it first. >>>

Argiris Kirtzidis <akyrtzi at gmail.com> writes: > I have some more requests: > > -Is it possible to also have the include files in the projects ? All the headers in include/llvm? Or just those local to each library? > -Can llvm-config or something like it be used to sort the dependencies > of the executables ? I plan to implement a poor's man llvm-config on the CMake

Dawie Joubert <djjoubert at csir.co.za> writes: > Recently (approximately a week ago) Clang and LLVM started to failed at > building. Assuming it was my incompetence, I cleared everything and > started witha fresh checkout (not that I changed it though). I am on > Ubuntu 10.04 LTS 64-Bit. And I configure and compile with CMake. > > The error message I get at approximatley

Kenneth Boyd <zaimoni at zaimoni.com> writes: [snip] >> That does not really surprise me about CMake, but then mingw is not a >> primary compiler on Windows, more so is VC++ or Intel, either way a >> bug should be submitted to the CMake devs. > I do not want to troll the CMake devteam, so I will not submit the bug > report without a full-blown patch. The CMake

Dear llvm, Recently (approximately a week ago) Clang and LLVM started to failed at building. Assuming it was my incompetence, I cleared everything and started witha fresh checkout (not that I changed it though). I am on Ubuntu 10.04 LTS 64-Bit. And I configure and compile with CMake. The error message I get at approximatley 66% is as follows: Linking CXX executable ../../bin/llvm-mc

Now that we have a "-why" option to the GenLibDeps.pl utility (which is used by llvm-config to deduce library dependencies), a review of the output has led to a few dubious library dependencies. Here they are: All of the following dependencies are singletons (the dependent library depends on only a single symbol from the dependency library): libLLVMCodeGen.a:

Óscar Fuentes wrote: > Kenneth Boyd <zaimoni at zaimoni.com> writes: > > [snip] > >> My internal priority for that CMake patch is low, as I need only minimal >> patching to use the autoconf-generated configure script to build LLVM. >> Right now it's just llvm.config.in.in that needs patching (the failsafed >> GenLibDeps.pl script went in

Hello, I'm facing some problems while building LLVM 2.8 shared libraries from source using CMake: cmake -DBUILD_SHARED_LIBS=true .. This is the output error: CMake Error: The inter-target dependency graph contains the following strongly connected component (cycle): "LLVMARMCodeGen" of type SHARED_LIBRARY depends on "LLVMARMAsmPrinter"

Óscar Fuentes wrote: > Kenneth Boyd <zaimoni at zaimoni.com> writes: > >> * I am seeing desynchronization between the configure-generated >> Makefiles and the CMakeFile.txt files. [e.g., llc; makefile doesn't >> have asmprinter, CMakeFile.txt does]. That much I should be able to >> construct a patch for "blind", if no-one gets to it first.

Hi, I want to write unit tests for a project I am working on. I need to create object files, preferably I want to have yaml files in the source tree and have cmake generate object files using yaml2obj. Does anyone know what I would put in the CMakeLists.txt to get this behavior? For a concrete example if I didn’t explain clearly: In llvm/unittests/Object I would maybe have an Inputs directory,

On 25/06/2019 11:24, James Henderson via llvm-dev wrote: > Hi Alex, > > Would you recommend that I do what is done in > unittest/ObjectYAML/MinidumpYAMLTest.cpp which just uses a string > inside the source file, or use an Inputs directory? Both are not > great, as you point out about using an Inputs directory > > > I'd be inclined to go with the

Hello, Everyone > On this specific case, IIRC, MinGW chokes if asmprinter is not on the > list of components. This may be another consequence of the malfunctoning > of llvm-config/GenLibDeps.pl on MinGW/MSYS. This works for me without any problems on mingw32. What are the problems you're seeing? -- WBR, Anton Korobeynikov

I discovered that I can hack around my particular problem by placing set_property(TARGET clang PROPERTY INTERFACE_LINK_LIBRARIES) at the end of tools/driver/CMakeLists.txt. I'd prefer to fix this properly though, of course. On 12/1/17, 4:18 PM, "llvm-dev on behalf of Shoaib Meenai via llvm-dev" <llvm-dev-bounces at lists.llvm.org on behalf of llvm-dev at lists.llvm.org>

Hi everyone, I have felt for quite some time that during my regular LLVM workflow, CMake recompiles a lot of files after I update to the latest ToT (which I do more than once per week). Of course, this wasn't really based on any real data, just felt like every time I update (even if it's a day or two later), we end up recompiling everything. For a while I assumed that patches touch a few

Thanks James! Thanks for the help. I certainly see your point. > In either case, if you wanted to change the test input, you'd need to rerun CMake again This is unfortunate, I would have hoped I could have CMake create $(wildcard *.yaml) type of output in the make files. But it sounds like this doesn't exist on make alternatives, so this wont work. There is actually a function to get

I think the reasons we would like to have CMake for clang are the same as for LLVM, manually maintaining the project files is a big pain and not done by that many developers. I don't have any experience with CMake but I did try it out and it seemed to work well, unfortunately I only have VS 2003 so I got blocked on C++ issues building with that compiler. However, the project file generation

So where could I find a list of LLVM libraries so I can figure out which ones I actually need to link into my program? Oscar Fuentes <ofv at wanadoo.es> writes: > Óscar Fuentes <ofv at wanadoo.es <http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev>> writes: > > >/ This patch *seems* to fix the problem (cmake regexps are not thoroughly > />/ documented): >

Chris Lattner <clattner at apple.com> writes: [snip] > That said, I don't really think the file globbing is that big of a > "feature". If it turns out that we don't get it with cmake, that's > ok. Automatic file globbing is, at least on GNU systems, possible with CMake. It would require some added complexity, and this I want to avoid. File globbing saves a

Argiris Kirtzidis <akyrtzi at gmail.com> writes: > I gave it a try and unfortunately it doesn't seem practical to use > CMake-produced VC++ projects. Every time you run CMake so that the VC++ > projects include new files, the entire solution gets rebuilt. I recall some discussion about the behavior you describe on the cmake ml, but can't find it right now. IIRC, once