search for: fbuild

...d BSD license, which is compatible with llvm's license, right? I just have to make sure any code I use from llvm's autoconf directory is properly attributed? Anyway, if anyone is interested in yet-another-buildsystem, I've got the (pre-alpha) code up here: http://git.felix-lang.org/?p=fbuild.git;a=summary It's designed to be used for cross compiling, configuration, and being really simple to extend, since it's written in python (3.0b2). It's also only ~3500 lines, which is way smaller than any other build system I've seen for what it supports. I'll be on #llvm and...

Kenneth Boyd <zaimoni at zaimoni.com> writes: > I'm indulging in this exercise to enable testing a native MingW32 build > of LLVM in Windows. If LLVM's DejaGNU usage is the same as GCC's, I'll google or ask on the MinGW mailing list how MinGW testers run the GCC testsuite, before trying to fix something that maybe is not broken. > There are more portability

...ject structure as necessary to > support > builds. This means explicitly specifying how the project is organized, > and > the dependencies among the components required to build (e.g., Intrinsics > before VMCore). > > I believe a number of other projects/users (FreeBSD, fbuild) have > built there own > build system for LLVM. Encoding the project structure clearly should make > it > easier for such projects, or for other future users that want to do the > same. > > This should make it easier to experiment with the build system, for > example...

...ly describe as much of the project structure as necessary to support builds. This means explicitly specifying how the project is organized, and the dependencies among the components required to build (e.g., Intrinsics before VMCore). I believe a number of other projects/users (FreeBSD, fbuild) have built there own build system for LLVM. Encoding the project structure clearly should make it easier for such projects, or for other future users that want to do the same. This should make it easier to experiment with the build system, for example we could just directly generate g...

...icitly describe as much of the project structure as necessary to support builds. This means explicitly specifying how the project is organized, and the dependencies among the components required to build (e.g., Intrinsics before VMCore). I believe a number of other projects/users (FreeBSD, fbuild) have built there own build system for LLVM. Encoding the project structure clearly should make it easier for such projects, or for other future users that want to do the same. This should make it easier to experiment with the build system, for example we could just directly generate good...

Hi, I’d just like to interject to say that building within Visual Studio isn’t really that bad. Running the lit tests is a bit painful because the LLVM build tools that are integrated with the build system don’t play nice with msbuild. Particularly, I’ve never been able to actually cancel an invocation of lit or tablegen via visual studio. That said, there is a huge upside to building with

...f the project structure as necessary to support > builds. This means explicitly specifying how the project is organized, and > the dependencies among the components required to build (e.g., Intrinsics > before VMCore). > > I believe a number of other projects/users (FreeBSD, fbuild) have > built there own > build system for LLVM. Encoding the project structure clearly should make it > easier for such projects, or for other future users that want to do the same. > > This should make it easier to experiment with the build system, for example > we coul...

...roject structure as necessary to support > builds. This means explicitly specifying how the project is organized, and > the dependencies among the components required to build (e.g., Intrinsics > before VMCore). > > I believe a number of other projects/users (FreeBSD, fbuild) have > built there own > build system for LLVM. Encoding the project structure clearly should make it > easier for such projects, or for other future users that want to do the same. > > This should make it easier to experiment with the build system, for example >...