On 19 Mar 2006, at 05:53, Hans-Christoph Steiner wrote:
I forgot to mention, it would be nice to have some help with the 0.39.2 build of Pd-extended. Because of all of the patches need to build Pd-extended, it doesn't easily work for multiple versions at the same time. So it would be great if you could work on the 0.39.2 stuff too. Anyway, the current version in CVS doesn't have any changes except for the patches that are in Pd-extended AFAIk.
Ok, I'm trying to get ready to help you; I've been trying to build extended so I could then offer help if needed. Main thing stopping me right now is I haven't managed a clean build yet. But, I'm almost there I think.
Could you point at things I might be able to help you with? I'm kinda lost as to where to begin (other than continuously testing on darwin). Please assume n00b-level expertise unless I tell you otherwise ;-)
d
-- David Plans Casal Researcher, UEA Studios d.casal at uea dot ac dot uk http://www.davidcasal.com
On Mon, 20 Mar 2006, David Plans Casal wrote:
On 19 Mar 2006, at 05:53, Hans-Christoph Steiner wrote:
I forgot to mention, it would be nice to have some help with the 0.39.2 build of Pd-extended. Because of all of the patches need to build Pd-extended, it doesn't easily work for multiple versions at the same time. So it would be great if you could work on the 0.39.2 stuff too. Anyway, the current version in CVS doesn't have any changes except for the patches that are in Pd-extended AFAIk.
Ok, I'm trying to get ready to help you; I've been trying to build extended so I could then offer help if needed. Main thing stopping me right now is I haven't managed a clean build yet. But, I'm almost there I think.
Could you point at things I might be able to help you with? I'm kinda lost as to where to begin (other than continuously testing on darwin). Please assume n00b-level expertise unless I tell you otherwise ;-)
I was under the impression that you were trying to compile Pd-extended against the latest CVS code, that's why I say you should work with 0.39.2. At the very least its very helpful that you are going about trying to get this working and reporting back so we can iron out the glitches in the process.
As to what you can help with, that's really up to what you want to do. There are so many things that need doing, many long TODO lists.
.hc
d
-- David Plans Casal Researcher, UEA Studios d.casal at uea dot ac dot uk http://www.davidcasal.com
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
zen \ \ \[D[D[D[D
On 20 Mar 2006, at 14:39, Hans-Christoph Steiner wrote:
On Mon, 20 Mar 2006, David Plans Casal wrote:
I was under the impression that you were trying to compile Pd- extended against the latest CVS code, that's why I say you should work with 0.39.2. At the very least its very helpful that you are going about trying to get this working and reporting back so we can iron out the glitches in the process.
I get confused as to what is meant by latest CVS code versus 0.39.2 and versus devel branch. I mean, the current release of millerPD is 0.39.2, then there's the CVS state, then there's the devel branch, which right now stands at 0.38.4.
So. When you say I should work with 0.39.2, do you mean I should get the tarball release, and compile against it instead of the cvs release which sits amongst:
abstractions extensions packages scripts doc externals *pd*
?
As to what you can help with, that's really up to what you want to do. There are so many things that need doing, many long TODO lists.
Where do you keep those lists? I realise there's the PD bug tracker, but that's for different purposes...Would you welcome using something like Backpack to share todos and progress and to be able to easily assign (or take ownership of) pending todos?
I've used Backpack for a few projects, and I think if there is to be a coordinated effort to help you do the huge job you're trying to do here, it would help. It's free, too ;-)
d
-- David Plans Casal Researcher, UEA Studios d.casal at uea dot ac dot uk http://www.davidcasal.com
On Mon, 20 Mar 2006, David Plans Casal wrote:
On 20 Mar 2006, at 14:39, Hans-Christoph Steiner wrote:
On Mon, 20 Mar 2006, David Plans Casal wrote:
I was under the impression that you were trying to compile Pd-extended against the latest CVS code, that's why I say you should work with 0.39.2. At the very least its very helpful that you are going about trying to get this working and reporting back so we can iron out the glitches in the process.
I get confused as to what is meant by latest CVS code versus 0.39.2 and versus devel branch. I mean, the current release of millerPD is 0.39.2, then there's the CVS state, then there's the devel branch, which right now stands at 0.38.4.
So. When you say I should work with 0.39.2, do you mean I should get the tarball release, and compile against it instead of the cvs release which sits amongst:
abstractions extensions packages scripts doc externals *pd*
Everything above should be the latest in CVS except for the "pd" directory, which is 0.39.3. You can either use the tarball, or CVS to get 0.39.2. Its nice to use CVS because then you can use CVS to run diffs and retreive files if you delete them, etc. You can check out 0.39.2 by doing this:
cvs checkout -r v0_39_2 pd
As to what you can help with, that's really up to what you want to do. There are so many things that need doing, many long TODO lists.
Where do you keep those lists? I realise there's the PD bug tracker, but that's for different purposes...Would you welcome using something like Backpack to share todos and progress and to be able to easily assign (or take ownership of) pending todos?
I've used Backpack for a few projects, and I think if there is to be a coordinated effort to help you do the huge job you're trying to do here, it would help. It's free, too ;-)
There are the bug and feature trackers plus many files called TODO embedded in the source.
.hc
d
--
ÄÄ> David Plans Casal
Researcher, UEA Studios d.casal at uea dot ac dot uk http://www.davidcasal.com
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
zen \ \ \[D[D[D[D