hi hans,
yup this is a great idea and a feature of the template that i've already integrated into my revised buildsys
a few questions:
does autotools have a 'make dist' feature by default?
what is it that you want to package - the source with the binaries? or just the objects/help as they would be installed?
is the path of the package 'extra/mylib' or just 'mylib', or something more specific?
is a true nightly build really necessary as most of the libs in the repository don't get that much regular attention. would it be better to autobuild when theres been an actaul revision in the working folder or change to an object dependency?
should the libs be zipped in win32, dmg'd on osx and tar'gz/bz for linux? or do you have other conditions?
cheers, dmotd
Hans-Christoph Steiner wrote:
I think it would be super useful to have nightly builds for standalone libs, not only Pd-extended. I think the easiest way to handle this would be to have "make dist" be the interface. Basically have a script that has a listing of the libraries to build, then it would run thru them and "make dist" then post the result.
Here are the ground rules as I see them for making a workable system:
- a script in scripts/autobuild that has the list of libs to built
- look in a folder named the same as the library in externals (i.e.
externals/mylibrary)
- if exists, call "./configure" in that folder
- call "make dist" in that folder
- then uploads the resulting tarball, also named like the lib
(mylibrary-0.1.tar.bz2)
Allowing too many special cases will make things ugly fast, so I think it makes sense to follow the autotools standard layout.
.hc
All information should be free. - the hacker ethic
Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev