similar to: [LLVMdev] CMake builds clang.

Kenneth Boyd <zaimoni at zaimoni.com> writes: >>> Isn't is possible for cmake just to glob everything in the corresponding >>> directory? >>> >> >> Yes, but then the build would not notice a change on the file >> structure. You'll need to explicitly invoke cmake for being sure that >> whatever changes were made by the last svn

Duncan Sands <baldrick at free.fr> writes: > Hi, > >> CMake just requires one plain text file named CMakeLists.txt on every >> source directory, and the only maintenance is to keep up to date the >> list of source files of the directory. > > can it be kept up-to-date automagically? After all, you can query > subversion to get the list of all files in a

Argiris Kirtzidis <akyrtzi at gmail.com> writes: >> I recall some discussion about the behavior you describe on the cmake >> ml, but can't find it right now. >> >> IIRC, once generated the project files, you shouldn't need to re-run >> cmake, ever. CMake inserts something in the project files for detecting >> that a re-generation is needed and

"Anton Korobeynikov" <asl at math.spbu.ru> writes: >> at all, it would be great if you reflect your changes on the file list >> inside the corresponding CMakeLists.txt when you add, remove or rename >> a .cpp file. > > Isn't is possible for cmake just to glob everything in the corresponding > directory? Yes, but then the build would not notice a

Hi, Oscar > at all, it would be great if you reflect your changes on the file list > inside the corresponding CMakeLists.txt when you add, remove or rename a > .cpp file. Isn't is possible for cmake just to glob everything in the corresponding directory? -- WBR, Anton Korobeynikov

Óscar Fuentes wrote: > Kenneth Boyd <zaimoni at zaimoni.com> writes: > > >>>> Isn't is possible for cmake just to glob everything in the corresponding >>>> directory? >>>> >>>> >>> Yes, but then the build would not notice a change on the file >>> structure. You'll need to explicitly invoke

Hi Oscar, Is there a way to make it work with CMake 2.6? That is what the public win32 buildbot has and I hate messing around with it. - Daniel On Tue, Aug 3, 2010 at 7:59 AM, Óscar Fuentes <ofv at wanadoo.es> wrote: > Aaron Gray <aaronngray.lists at gmail.com> writes: > >> I am getting the following error from CMake :- >> >>     CMake Error at

Óscar Fuentes <ofv at wanadoo.es> writes: > Yep, llvm_map_components_to_libraries gets confused by the existence of > both gtest and gtest_main and enters an infinite loop. A workaround is > to not pass "all" to llvm_map_components_to_libraries but a list of > required components. This patch *seems* to fix the problem (cmake regexps are not thoroughly documented):

Óscar Fuentes wrote: > "Anton Korobeynikov" <asl at math.spbu.ru> writes: > > >>> at all, it would be great if you reflect your changes on the file list >>> inside the corresponding CMakeLists.txt when you add, remove or rename >>> a .cpp file. >>> >> Isn't is possible for cmake just to glob everything in the

IMHO, the CMake-based build system is almost complete enough to replace current MSVC++ project files (modulo some community review and bug-fixing). Is this enough for adding it to the LLVM repo? >From the point of view of a MSVC++ user, the new build system is trivial to maintain: you can add a new library or tool executable in less time that it takes to open the project file on MSVC++, it

On Oct 26, 2008, at 11:17 AM, Óscar Fuentes wrote: >> It would be simpler for autoconf builds to have a Perl script that >> updates the CMakeLists.txt files when necessary. (This doesn't look >> *that* hard, but I can't say when I'll surface long enough to work >> on that.) > > In theory, it is possible to do this with cmake itself. In practice, >

This isn't meant to be a sample, but I can share with you the cmake files I use for my compiler. It builds in both windows user MSVC, and linux using G++, but should work with MinGW. the structure is src/ CMakeLists.txt # root make file front/ CMakeLists.txt # library middle/ CMakeLists.txt # library back/ CMakeLists.txt # library npp/ CMakeLists.txt # executable

Ah, thank you so much. How did you get the list of target_link_libraries() ? Did you use llvm-config? If you did not have access to llvm-config, how would you get list of libraries to link to? Thanks. Sam On Sun, Jun 13, 2010 at 2:44 PM, Nathan Jeffords <blunted2night at gmail.com>wrote: > This isn't meant to be a sample, but I can share with you the cmake files I > use for my

Hi Óscar, Thank you for the reply. I indeed got an impression (may be incorrect) that projects/ directory is intended for users' projects that are not committed to LLVM repository. Otherwise, of course, the patch doesn't make much sense. Anyway, I've added a comment about the need of explicit CMake invocation to projects/CMakeLists.txt. Thanks, Victor -----Original Message-----

"Viktar Zviarovich" <Viktar.Zviarovich at brunel.ac.uk> writes: > The suggested patch enables addition of all subdirectories of > llvm/projects to CMake build. > > It somewhat simplifies the process of creating new projects that use > CMake instead of make, eliminating the need of editing > llvm/CMakeLists.txt and llvm/projects/CMakeLists.txt. This is not

I am getting the following error from CMake :- CMake Error at CMakeLists.txt:227 (set_property): set_property given invalid scope CACHE. Valid scopes are GLOBAL, DIRECTORY, TARGET, SOURCE, TEST. Can someone familiar with CMake deal with this please, Aaron -------------- next part -------------- An HTML attachment was scrubbed... URL:

Well for one thing, it gives one example of a CMakeLists.txt file that correctly uses LLVM, and nothing else. It gives no information on how to find out what set of components I need to map for what APIs. Neither does llvm-config list out the names of the actual components. I can use either the CMake modules or llvm-config to find the library names once I've got the component names, but

Aaron Gray <aaronngray.lists at gmail.com> writes: > I am getting the following error from CMake :- > > CMake Error at CMakeLists.txt:227 (set_property): > > set_property given invalid scope CACHE. Valid scopes are GLOBAL, > > DIRECTORY, TARGET, SOURCE, TEST. > > > Can someone familiar with CMake deal with this please, Please upgrade to cmake

[I'm cc-ing the mailing list because there are some topics here of general interest] HyperQuantum <hyperquantum at gmail.com> writes: >> CMAKE_SOURCE_DIR should be the same as LLVM_MAIN_SRC_DIR. If you know an >> scenario where this is not true, please describe it. > > In my case it's not true. I have put LLVM in a subdirectory of my > project

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): >