hi
moved this to pd-dev, as i think this is more appropriate....
Hans-Christoph Steiner wrote:
That's the vague idea of the current makefiles there. But since many people didn't want to change the existing makefiles within each library folder, almost everything is stuck into externals/Makefile.
that's why i would suggest something as simple as using "Makefile.extended" which could live besides an existing "Makefile" and make use of it (if this is feasible).
we then schould provide a generic Makefile.extended for building those externals that do not need any more specific handling.
i would suggest following targets: configure, build (default), install, clean
and the rest is in the Wiki http://puredata.info/dev/ModularBuildSystem (by chance i sent the Wiki announcement before this email...)
fmgasd.r IOhannes
I just joined the pd-dev list so i can keep up with this discussion.
I added a link to the GNU makefile conventions information to that wiki page. The info on the wiki seems pretty good though I don't quite understand the Makefile.extended... it is my understanding that these new makefiles are not simply for 'extended', they are an effort to remove the 'extendedness' requirement that exists there. It seems to me that eventually each external should have one file simply called "Makefile"... maybe the existing makefiles should be renamed to Makefile.something in the mean time?
-Alex
On Mon, Oct 20, 2008 at 9:02 AM, IOhannes m zmoelnig zmoelnig@iem.at wrote:
hi
moved this to pd-dev, as i think this is more appropriate....
Hans-Christoph Steiner wrote:
That's the vague idea of the current makefiles there. But since many people didn't want to change the existing makefiles within each library folder, almost everything is stuck into externals/Makefile.
that's why i would suggest something as simple as using "Makefile.extended" which could live besides an existing "Makefile" and make use of it (if this is feasible).
we then schould provide a generic Makefile.extended for building those externals that do not need any more specific handling.
i would suggest following targets: configure, build (default), install, clean
and the rest is in the Wiki http://puredata.info/dev/ModularBuildSystem (by chance i sent the Wiki announcement before this email...)
fmgasd.r IOhannes
Alex wrote:
I just joined the pd-dev list so i can keep up with this discussion.
I added a link to the GNU makefile conventions information to that wiki page. The info on the wiki seems pretty good though I don't quite understand the Makefile.extended... it is my understanding that these new makefiles are not simply for 'extended', they are an effort to remove the 'extendedness' requirement that exists there. It seems to me that eventually each external should have one file simply called "Makefile"... maybe the existing makefiles should be renamed to Makefile.something in the mean time?
the idea is, to allow people to maintain their own build-systems fit to _their_ own needs for their externals. having a separate naming would just not interfere with these. (there are people who are quite allergic to other people f*ing up their build-systems, even if everything is by the best intentions)
in the "ideal" world, Makefile.extended would just "include Makefile" and they would be the same. with the noteable difference, that - "Makefile" would contain the actual build-system - "Makefile.extended" would serve as a flag to indicate that this external should be included in "full" builds.
for those externals with no existing Makefile, doing this Makefile will definitely be the first step.
fgamsdr IOhannes
I've made a makefile for mrpeach/osc/ This collection is pretty simple as each external is one file, I'm attaching my makefile, I'm wondering what changes should be made to form this into the example makefile to use for externals in the svn?
I'm not sure about the use of the word "TARGETS" here but I couldn't think of anything better.
-Alex
On Tue, Oct 21, 2008 at 12:27 AM, IOhannes m zmoelnig zmoelnig@iem.at wrote:
Alex wrote:
I just joined the pd-dev list so i can keep up with this discussion.
I added a link to the GNU makefile conventions information to that wiki page. The info on the wiki seems pretty good though I don't quite understand the Makefile.extended... it is my understanding that these new makefiles are not simply for 'extended', they are an effort to remove the 'extendedness' requirement that exists there. It seems to me that eventually each external should have one file simply called "Makefile"... maybe the existing makefiles should be renamed to Makefile.something in the mean time?
the idea is, to allow people to maintain their own build-systems fit to _their_ own needs for their externals. having a separate naming would just not interfere with these. (there are people who are quite allergic to other people f*ing up their build-systems, even if everything is by the best intentions)
in the "ideal" world, Makefile.extended would just "include Makefile" and they would be the same. with the noteable difference, that
- "Makefile" would contain the actual build-system
- "Makefile.extended" would serve as a flag to indicate that this external
should be included in "full" builds.
for those externals with no existing Makefile, doing this Makefile will definitely be the first step.
fgamsdr IOhannes
-
Alex -
IOhannes m zmoelnig