Hello & thank you for the answer.

...

in the subfolder ./trunk/pd i can read the INSTALL.TXT file... which tells me to make a ./configure in /trunk/pd/src ...

this INSTALl.txt is a) outdated

i thought so.

b) meant for the source release(!) rather than an SVN-snapshot

the latter means: it is considered bad style to put anything "generated" (mostly binaries, but also scripts, like "configure") into VCS. hence configure (which is generated from configure.ac) is missing in the SVN.

ok.

to generate everything needed in order to run "configure" (btw, nowadays this is in .../pd rather than .../pd/src) just run (in .../pd): $ ./autogen.sh

so, since autogen.sh is also a script, it is not included in the svn-snapshot...? can you please tell me what to do, if i want to compile the snapshot then? - copy the scripts into?? or better copy the source out of the svn-maintained folder, and copying the scripts needed to create the configure script... etc...?

where do i get those scripts from...? copying them from a source-release? copying the snapshot-sources into a source-release??

is there a step-by-step tutorial for compiling a svn-snapshot?

thanks. ingo

On Feb 19, 2011, at 12:14 PM, Martin Peach wrote:

On 2011-02-19 11:29, Ingo Randolf wrote:

...

Hello& thank you for the answer.

...

...

in the subfolder ./trunk/pd i can read the INSTALL.TXT file... which tells me to make a ./configure in /trunk/pd/src ...

this INSTALl.txt is a) outdated

i thought so.

...

b) meant for the source release(!) rather than an SVN-snapshot

the latter means: it is considered bad style to put anything "generated" (mostly binaries, but also scripts, like "configure") into VCS. hence configure (which is generated from configure.ac) is missing in the SVN.

ok.

...

to generate everything needed in order to run "configure" (btw, nowadays this is in .../pd rather than .../pd/src) just run (in .../pd): $ ./autogen.sh

so, since autogen.sh is also a script, it is not included in the svn-snapshot...? can you please tell me what to do, if i want to compile the snapshot then?

• copy the scripts into?? or better copy the source out of the svn-

maintained folder, and copying the scripts needed to create the configure script... etc...?

where do i get those scripts from...? copying them from a source- release? copying the snapshot-sources into a source-release??

is there a step-by-step tutorial for compiling a svn-snapshot?

I was using this: http://puredata.info/docs/developer/BuildingPdExtended But recently I have been unable to build Pd this way because trunk is inconsistent ATM. I think the idea is to choose a version in /branches and build that, starting in the packages directory. It worked for me with Pd- extended 0.42.5 on linux at least. For the latest versions of externals build them separately from trunk/externals.

Yes, its true, its a bit of a mess. We haven't figured out out to bridge from git to svn very well yet, and both pure-data and pd- extended are now developed out of git.

If you want to build like the nightly builds, then use the 'rsync' method of getting the source.

.hc

----------------------------------------------------------------------------

"A cellphone to me is just an opportunity to be irritated wherever you are." - Linus Torvalds

On Feb 19, 2011, at 2:05 PM, Martin Peach wrote:

On 2011-02-19 13:50, Hans-Christoph Steiner wrote:

...

On Feb 19, 2011, at 12:14 PM, Martin Peach wrote:

...

On 2011-02-19 11:29, Ingo Randolf wrote:

...

is there a step-by-step tutorial for compiling a svn-snapshot?

I was using this: http://puredata.info/docs/developer/BuildingPdExtended But recently I have been unable to build Pd this way because trunk is inconsistent ATM. I think the idea is to choose a version in /branches and build that, starting in the packages directory. It worked for me with Pd- extended 0.42.5 on linux at least. For the latest versions of externals build them separately from trunk/externals.

Yes, its true, its a bit of a mess. We haven't figured out out to bridge from git to svn very well yet, and both pure-data and pd-extended are now developed out of git.

If you want to build like the nightly builds, then use the 'rsync' method of getting the source.

It's weird, I remember the shift from cvs to svn took a few months of discussion on the list but I don't remember seeing anything about moving to git...

Martin

Hey Martin,

Miller moved to git a while ago, and with 0.43 started pushing his git to a public repository. Since then, it made sense to develop the Pd- extended fork of the Pd core also out of git so that we can manage the flow of patches between Pd and Pd-extended. So this only applies to the core, i.e what's in the 'pd' folder. Everything else remains in SVN.

I personally have moved all my work on the 'core' to git, I believe IOhannes has as well. If you wanted to work on the 'pd' core stuff in Pd-extended out of SVN, I suppose that would be possible, but I think it would be much easier for everyone if you also did your core work out of git. I am thinking that the Pd-extended release branches will remain entirely in SVN.

You are right, its not really been announced, I think my own Pd- extended work in git has only reached an announceable state in the past couple of days. So I'm curious what your thoughts on all this are, since you contribute quite a bit to the core.

.hc

----------------------------------------------------------------------------

I hate it when they say, "He gave his life for his country." Nobody gives their life for anything. We steal the lives of these kids. - Admiral Gene LeRocque