Mike Stump <mrs at apple.com> writes:> On Oct 23, 2008, at 5:04 PM, Óscar Fuentes wrote: >> Now tblgen.exe builds fine with my CMake build system. Guess it is >> the same case for the VC++ project files. > > Oh, does clang building work with CMake? If not, wanna cons it > up? :-) Thanks.Giving a compelling reason why you'll like to build clang using CMake instead of configure && make would help to speed up things :-) Apart from me, I only know of one person that tried CMake, and it was by accident. Right now CMake works for me and does what I need. It achieved the primary goal of being a replacement for the VC++ project files (it needs to be described on the LLVM docs, but this will happen soon). I know there are lots of things to be done for being a general replacement of LLVM's build system, but if there is no feedback, this will progress slowly. Please note that I'm, mostly, a Windows guy with a very limited set of requirements on LLVM (just the JIT) so I'm totally unaware of the expectations most of you have. I'm specially interested on why you dislike the current build system (for not doing the same mistakes again), what you'll like to see implemented (to improve on what we have) and what features are mandatory for using the new system on a regular basis. -- Oscar
On Friday 24 October 2008, Óscar Fuentes wrote:> Apart from me, I only know of one person that tried CMake, and it was by > accident.Well I tried it on linux, and it sounds like it worked. Well llvm was build without error, but since I prefer to stick to released llvm, I didn't if the results of the compilation was usuable ;) -- Cyrille Berger
Le 24 oct. 08 à 10:01, Cyrille Berger a écrit :> On Friday 24 October 2008, Óscar Fuentes wrote: >> Apart from me, I only know of one person that tried CMake, and it >> was by >> accident. > > Well I tried it on linux, and it sounds like it worked. Well llvm > was build > without error, but since I prefer to stick to released llvm, I > didn't if the > results of the compilation was usuable ;) > > --The last time I tried it on OS X, the cmake file did not correctly generate the config.h. (There is a lots of hardcoded value in config.h.cmake that should be replaced by cmakedefine equivalent).
How does updating the CMake produced VC++ project files work ? I mean: -I have CMake produce VC++ project files -Compile the solution -Do a svn update and pick up a couple of files -Have CMake produce new project files -Now, do I have to rebuild the entire solution again ? -Argiris
Argiris Kirtzidis <akyrtzi at gmail.com> writes:> How does updating the CMake produced VC++ project files work ? > I mean: > > -I have CMake produce VC++ project files > -Compile the solution > -Do a svn update and pick up a couple of files > -Have CMake produce new project files > -Now, do I have to rebuild the entire solution again ?AFAIK, it should do the right thing automatically, regenerating the project files on the fly and recompiling only what is outdated. You don't even need to explicitly invoke cmake after a svn update. This is my understanding from reading the CMake ml. I tend to use nmake. -- Oscar