similar to: [LLVMdev] Is there room for another build system?

Óscar Fuentes wrote: > I'm evaluating CMake (1) primarily as an alternative build system for > Visual Studio users, although it can easily be a replacement for > `configure' and hand-made makefiles too, providing a single build system > for all platforms. CMake is a tool that takes a project description and > configures, generates makefiles, project files for IDEs, etc as

Hi Oscar, On 30-Jul-08, at 9:41 AM, Óscar Fuentes wrote: > 1. General LLVM users: Are you so happy with `configure' and hand-made > makefiles that you wont consider an alternative? If you are > interested, > I can steer my work to cover all platforms. We (RapidMind) are very interested. We would very much like to see a unified build system across MSVC/Windows and gcc/Linux/OS

Stefanus Du Toit <sdt at rapidmind.com> writes: [snip] > We have considered contributing such a build system, and if we were to > do so would probably base it on SCons (http://www.scons.org/) because > we already use SCons extensively. At first, SCons is what I intended too. But then I read about the KDE experience and took the safe route :-) [snip] > Are you intending

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 directory. > 1. General LLVM users: Are you so happy with `configure' and

On Jul 30, 2008, at 9:41 AM, Óscar Fuentes wrote: > I'm evaluating CMake (1) primarily as an alternative build system for > Visual Studio users, although it can easily be a replacement for > `configure' and hand-made makefiles too, providing a single build > system > for all platforms. CMake is a tool that takes a project description > and > configures, generates

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

On May 17, 2008, at 2:44 PM, Óscar Fuentes wrote: > I don't know how much LLVM build system is tied to the GNU toolchain > or > how much it depends on *nix features, but suppossing that adding > support > for MSVC++ is impractical, perhaps it would be simpler to implement a > Makefile-based build system for MSVC++ than to keep up to date the > project files. This would

Chris Lattner <clattner at apple.com> writes: > Ok. Killing off autoconf would be a huge bonus, but should probably > be done as a second step. My plan is a staged one: First, support MSVC++. Second, implement what `configure' does now. MSVC++ users would be the first ones to take advantage of this, instead of the current hack Visual Studio does. Finally, add capabilities

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

I too have done some work on an alternative build system for llvm. It is based on boost.build. Of course, it's quite a large project and I'm not ready to contribute the work yet. Ideally I was hoping to replace all of makefile functionality with jamfiles. Boost.build is attractive because support for new compilers/tools comes with new releases of boost.build and need not be added

On Sunday 18 May 2008, Óscar Fuentes wrote: > Chris Lattner <sabre at nondot.org> writes: > > [snip] > > > Others have suggested alternative build systems before like cmake. > > Apparently cmake can autogenerate VC++ and Xcode project files from > > the same thing that it builds from on unix systems. > > cmake creating VC++ project files does not appeal

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

2 more roadblocks for Visual Studio users are the inability to compile gcc and the inability to compile and run the test suite. I would not want to submit a change unless I could still compile/run gcc and pass the test suite. (Testing before submission is the way we do it where I come from - I am assuming it's the same here). On a related note, has anyone gotten the LLVM test suite working

Óscar Fuentes wrote: > Albert Graef <Dr.Graef at t-online.de> writes: >> Here are some points worth considering: >> http://www.remlab.net/op/cmake.shtml (Some of these may already be >> addressed in newer cmake versions, I haven't checked recently.) > > [...] > > Please, some LLVM release manager (Tanya?), read Albert's web page and > evaluate

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

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

On Sun, Sep 21, 2008 at 9:27 AM, Óscar Fuentes <ofv at wanadoo.es> wrote: > This is an updated version of the patch that fixes some issues on VC++ > builds. Hi, FYI I just tried this (from r56534). I get an "error" (below) from cmake (2.6.1) about Intrinsics.gen but it seems to write out sln/vcproj anyway. Project.sln opens and builds OK (modulo a build error in llvmc2

Óscar Fuentes wrote: > 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. Has anyone read "Recursive Make Considered Harmful"? http://miller.emu.id.au/pmiller/books/rmch/ http://aegis.sourceforge.net/auug97.pdf I have been using single

I'm evaluating CMake (1) primarily as an alternative build system for Visual Studio users, although it can easily be a replacement for `configure' and hand-made makefiles too, providing a single build system for all platforms. CMake is a tool that takes a project description and configures, generates makefiles, project files for IDEs, etc as requested. There are three MS C++ compilers

On Wed, Jul 30, 2008 at 6:41 PM, Óscar Fuentes <ofv at wanadoo.es> wrote: > I'm evaluating CMake (1) primarily as an alternative build system for > Visual Studio users, although it can easily be a replacement for > `configure' and hand-made makefiles too, providing a single build system > for all platforms. CMake is a tool that takes a project description and >