For anyone curious, I attached my result. It's pretty basic; define required packages (gobject-2.0 is always included), the name of the executable, customize cflags and directories if you wish (defaults to src/ for source and build/ for compiled results), and then run make. It doesn't build shared libraries or do installation, but I don't think it would be too hard to add once I get some time.
Unlike Carl's approach, this isn't a full-fledged build tool, just a convenient makefile for people who want to be able to build a project without worrying about autotools syntax. ~Damien On Thu, Aug 25, 2011 at 2:00 PM, Andrea Bolognani <[email protected]> wrote: > On Thu, Aug 25, 2011 at 09:35:02PM +0200, Carl wrote: > > > […] handle application packaging (debian package […] > > Please, please, please don’t do this. > > I’ve already explained on this list ([1] and follow–up messages) why > mixing upstream releases and Debian packages is a Really Bad Idea™. > > Just make your tool generate a tarball containing the source files > along with the recipe your tool needs in order to build them, and let > the ${DISTRIBUTION} maintainer handle the ${DISTRIBUTION}-specific bits. > > > [1] http://mail.gnome.org/archives/vala-list/2009-October/msg00018.html > -- > Andrea Bolognani <[email protected]> > Resistance is futile, you will be garbage collected. > > _______________________________________________ > vala-list mailing list > [email protected] > http://mail.gnome.org/mailman/listinfo/vala-list > >
vala-Makefile
Description: Binary data
_______________________________________________ vala-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/vala-list
