Check http://hg.youterm.com/acr
it's a gnu configure compatible replacement in a much smaller way and fully written in posix shellscript I use it for all my projects. It's just an autoconf like tool. So it misses all the makefile generation stuff.. Well. There's a little work in amr. But not ready for parvala. It would be easy to integrate it with parvala, .. I already use parvala in some projects of mine.. But i have to recognize that its not as simple as i would like to.. So mixing it with amr would be a perfect solution for an autotools replacement. Btw. I have also used waf with vala. And worked fine. But i dont know the current state or if its supports paralel compilation. Nevertheless sometimes is faster to run a single valac line with all the source files at once than creating a fastvapi and then compiling each file separatedly. If we think in other ides like xcode or visualstudio.. We fall in the same problem. Because there's no simple way to maintain dependencies and building rules for make and xcode/vs.. Thats not a big issue for me. Because make works great on osx and i can use mingw32/64 to crosscompile to windows. But maybe some users just want to use it natively. Just my 5bc On 25/08/2011, at 21:35, Carl <name.is.c...@gmail.com> wrote: > Funny you should say that, i'm working on a cross platform, native building > tool too :-) > > I'm not crazy about make autoconfigure intlool (and the perl requirement) > and all the dependencies (all the shell tools perl, libxml... > )whereas the point is, in most case, to invoke gcc (and friends : ld ar > pkgconfig...) with the proper parameters. > > So I decided to get down to it : building c and vala projects with only gcc > (and friends). No shell script, no perl, no configuration generation. > And no modification to my source folders : no file added, generated or > "cleaned". If the tool has to generate files, it will create its own temp > folder. Way cleaner, way safer. > > Each project is described declaratively with a easily readable and parsable > yaml file, and processed to build the exec or shared library or static > library. > All are supported :-) > > You can define build configurations (debug and release are the ones I use) : > each with specific settings (optimisation,symbols, warning levels, output > file names). > > I'm quite happy with the result so far : i can build vala(even gidl and > gen-introspect), valadoc and other projects without having to invoke > configure make or autogen. Just from the project file i wrote (a couple of > lines each) and the vala files of course. > The project file for the hello world program is 4 lines iirc. > > The tool can handle vala, c,language files, config.h (it should be able to > generate it from the project file very soon) and library/project > dependencies. > > Like with make, required projects are built automatically... > > I still have to generate pc deps files and handle application packaging > (debian package and simple Windows installer). And test it on Linux. And add > some documentation :-) > > Cheers, > Carl > _______________________________________________ > vala-list mailing list > vala-list@gnome.org > http://mail.gnome.org/mailman/listinfo/vala-list _______________________________________________ vala-list mailing list vala-list@gnome.org http://mail.gnome.org/mailman/listinfo/vala-list
