search for: cmake_faq

...( -D_SECURE_SCL=0 ) With this setting the default LLVM build becomes incompatible with libraries compiled with _SECURE_SCL=1 (which is the default setting). The right thing here is to use an option. > - add_llvm_definitions("/${LLVM_USE_CRT}") > + # http://www.cmake.org/Wiki/CMake_FAQ#How_can_I_build_my_MSVC_application_with_a_static_runtime.3F > + foreach(flag_var > + CMAKE_C_FLAGS CMAKE_C_FLAGS_DEBUG CMAKE_C_FLAGS_RELEASE CMAKE_C_FLAGS_MINSIZEREL CMAKE_C_FLAGS_RELWITHDEBINFO > + CMAKE_CXX_FLAGS CMAKE_CXX_FLAGS_DEBUG CMAKE_CXX_FLAGS_RELEASE CMA...

...n a dependency is superfluous. >> Furthermore, recursive make is necessary for automatic generation of >> header dependencies, among other things. The makefiles generated by >> cmake are "partially" recursive for that reason: >> >> http://www.cmake.org/Wiki/CMake_FAQ#Why_does_CMake_generate_recursive_Makefiles.3F > > I don't understand, what does having one makefile per directory have > to do with header file generation? No one makefile per directory, but recursive make. Automatic header dependencies are usually supported by recursively invoking `...

...box. Whatever improvement can be achieved on this seems pretty insignifant. Furthermore, recursive make is necessary for automatic generation of header dependencies, among other things. The makefiles generated by cmake are "partially" recursive for that reason: http://www.cmake.org/Wiki/CMake_FAQ#Why_does_CMake_generate_recursive_Makefiles.3F >>> 2. The build system generated by cmake is absolute garbage, at least >>> for Xcode. The build times of it are really bad, and having to work >>> with it in the IDE is even more terrible. >> >> AFAIK there i...

On Oct 27, 2011, at 11:28 PM, Óscar Fuentes wrote: > Chris Lattner <clattner at apple.com> writes: > >> There are several major problems with CMake IMO: >> >> 1. It generates really slow build systems. > > In my Linux box, last time I checked (long time ago) the cmake build was > a bit faster than the Makefiles. But this is a tricky terrain, because >

thanks for the help ..I could build it with cmake generated project files Being a newbie with cmake one question, is it equivalent to configure in windows environment and so would need to be run everytime I change the source location ? thanks shrey On Wed, Oct 28, 2009 at 4:31 PM, shreyas krishnan <shreyas76 at gmail.com> wrote: > done > >

On 06/22/2012 01:08 AM, Óscar Fuentes wrote: > You can work with LLVM without installing, or install it on a specific > directory that you can delete afterwards. That's much better than > overwriting/removing the previous version. No, in general it's not. It's fairly common to install LLVM under a standard prefix such as /usr or /usr/local so that its headers and libraries

done http://llvm.org/bugs/show_bug.cgi?id=5331 shrey On Wed, Oct 28, 2009 at 3:29 PM, Óscar Fuentes <ofv at wanadoo.es> wrote: > shreyas krishnan <shreyas76 at gmail.com> writes: > >>     I am running into bunch of windows build issues. Can someone >> please provide help on what might be going wrong >> >> >>

...it synchronization between different sublibraries. > Furthermore, recursive make is necessary for automatic generation of > header dependencies, among other things. The makefiles generated by > cmake are "partially" recursive for that reason: > > http://www.cmake.org/Wiki/CMake_FAQ#Why_does_CMake_generate_recursive_Makefiles.3F I don't understand, what does having one makefile per directory have to do with header file generation? >>>> 2. The build system generated by cmake is absolute garbage, at least >>>> for Xcode. The build times of it are r...

Attached are two patches with MSVC build enchancements. They are quite trivial, but were necessary to correctly link LLVM libraries with Mesa3D on Windows. Jose -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Allow-to-build-against-static-MSVC-runtime.patch Type: text/x-patch Size: 2055 bytes Desc: not available URL:

...fluous. > >>> Furthermore, recursive make is necessary for automatic generation of >>> header dependencies, among other things. The makefiles generated by >>> cmake are "partially" recursive for that reason: >>> >>> http://www.cmake.org/Wiki/CMake_FAQ#Why_does_CMake_generate_recursive_Makefiles.3F >> >> I don't understand, what does having one makefile per directory have >> to do with header file generation? > > No one makefile per directory, but recursive make. Automatic header > dependencies are usually supported...

Albert Graef <Dr.Graef at t-online.de> writes: > On 06/21/2012 04:22 PM, Óscar Fuentes wrote: >> About the "many features" that cmake lacks, can you provide a list, >> please? > > Generally it works fairly well, but here are some differences to the > autoconf-based build I noticed: > > - No 'make uninstall'. That is a real deal breaker if you

Hi Oscar, For development, CMake is working great for me. I rarely get build errors related to the project file being out-of-date. Is it true that CMake only generates absolute paths? Any idea on the difficulty of generating relative paths? I consider this a pretty big obstacle... Thanks for all your hard work on this, snaroff On Jan 15, 2009, at 9:46 AM, Óscar Fuentes wrote: >

Hi all, As you might have inferred, I'm in the process of working on some changes to the way LLVM builds. I have outlined a rough proposal below, unless there are any major objections I will probably start committing stuff next week. This message may be verbose, if you want the executive summary, skip to 'What This Means For Jane "LLVM Developer" Doe' at the bottom.