I have just put my externals in the sourceforge CVS. ff/ forcefeedback externals for linux jackx/ patching and connection querying for linux beatpipe/ a beat oriented scheduler/quantizer for any pd.
I don't have vi installed, so I need to figure out how to change the editor for log messages.
Now the question, how does the build system work, do I have to do anything to add my externals to them?
Gerard
Hallo, gml@xs4all.nl hat gesagt: // gml@xs4all.nl wrote:
I have just put my externals in the sourceforge CVS. ff/ forcefeedback externals for linux jackx/ patching and connection querying for linux beatpipe/ a beat oriented scheduler/quantizer for any pd.
I don't have vi installed, so I need to figure out how to change the editor for log messages.
$ export EDITOR=yourfaveditor
should help.
ciao
There really should be documentation for how to do this. Its on my todo list...
Basically, if your external can be compiled as a standalone object and its only dependencies are standard ones, then you can add them to the 'pd-externals' package. You do this by adding files to externals/build/src. Open up the files there to see how its done, its pretty simple. Then each platform has a directory with what it needs to build all those objects. There is currently externals/build/linux, externals/build/darwin, and externals/build/win.
If the externals have other dependencies, then currently it needs to be build as a standalone package for each platform. zexy, flext, cyclone are examples of that. But ideally everything would be in a unified build system. That's what Günter is working on for Debian, Nando for RPMs, and Adam Lindsay and I for MacOS X, and me for Windows.
.hc
On Saturday, Oct 18, 2003, at 11:12 America/New_York, gml@xs4all.nl wrote:
I have just put my externals in the sourceforge CVS. ff/ forcefeedback externals for linux jackx/ patching and connection querying for linux beatpipe/ a beat oriented scheduler/quantizer for any pd.
I don't have vi installed, so I need to figure out how to change the editor for log messages.
Now the question, how does the build system work, do I have to do anything to add my externals to them?
Gerard
PD-dev mailing list PD-dev@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-dev
So what are the standard dependencies ? Just libc and pd ?
I assume you mean dependencies to compile, not requirements to run.
How about my jackx externals. Obviously they need jack installed. Should I remove them from the externals/ directory and move them somewhere else?
Gerard
On Sunday 19 October 2003 05:49, Hans-Christoph Steiner wrote:
There really should be documentation for how to do this. Its on my todo list...
Basically, if your external can be compiled as a standalone object and its only dependencies are standard ones, then you can add them to the 'pd-externals' package. You do this by adding files to externals/build/src. Open up the files there to see how its done, its pretty simple. Then each platform has a directory with what it needs to build all those objects. There is currently externals/build/linux, externals/build/darwin, and externals/build/win.
I think I understand the build system a little bit now. What do I do with the help patches. There are copies in the build directory. And the linux makefile uses those, but the darwin makefile uses those in the original directories.
And I guess I should set the helpsymbol in the source, didn't the default change to help-myexternal.pd with 0.37?
Gerard
On Sunday, Oct 19, 2003, at 09:57 America/New_York, gml@xs4all.nl wrote:
I think I understand the build system a little bit now. What do I do with the help patches. There are copies in the build directory. And the linux makefile uses those, but the darwin makefile uses those in the original directories.
The old style was to copy all of the helpfiles into externals/build/src. Going forward, the helpfiles should be copied directly from the source by the Makefile so that we only need to maintain one copy of each helpfile. MacOS X and Windows work this way (Windows does it in the Inno pd.iss file instead of the Makefile), but Debian needs to be updated to the new way. In the meantime, if you want your helpfiles in Debian, you need to also add them to externals/build/doc.
And I guess I should set the helpsymbol in the source, didn't the default change to help-myexternal.pd with 0.37?
You actually should not use class_sethelpsymbol() unless your helpfile has a different name than your object, according to Miller. So if your external is called 'myexternal' and your help patch is called either 'help-myexternal.pd' or 'myexternal-help.pd' (the preferred style), then you don't need class_sethelpsymbol(), pd will find it automatically.
.hc
Gerard
PD-dev mailing list PD-dev@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-dev
________________________________________________________________________ ____
There is no way to peace, peace is the way. -A.J. Muste
On Sunday, Oct 19, 2003, at 06:50 America/New_York, vanDongen/Gilcher wrote:
So what are the standard dependencies ? Just libc and pd ?
I assume you mean dependencies to compile, not requirements to run.
Basically yes.
How about my jackx externals. Obviously they need jack installed. Should I remove them from the externals/ directory and move them somewhere else?
Hmm, limiting factor is that this whole thing has to be compiled by the Debian auto-builders, so the dependencies have to be set up. My guess is that the jackx externals would have to be their own package but Guenter is the expert there.
As for the MacOS X and Windows, there are no auto-builders (unless you consider me to be an auto-builder), so the system is a bit more tolerant.
.hc
Gerard
On Sunday 19 October 2003 05:49, Hans-Christoph Steiner wrote:
There really should be documentation for how to do this. Its on my todo list...
Basically, if your external can be compiled as a standalone object and its only dependencies are standard ones, then you can add them to the 'pd-externals' package. You do this by adding files to externals/build/src. Open up the files there to see how its done, its pretty simple. Then each platform has a directory with what it needs to build all those objects. There is currently externals/build/linux, externals/build/darwin, and externals/build/win.
-- electronic & acoustic musics-- http://www.xs4all.nl/~gml
________________________________________________________________________ ____
"[W]e have invented the technology to eliminate scarcity, but we are deliberately throwing it away to benefit those who profit from scarcity." -John Gilmore
On Sun, 19 Oct 2003, vanDongen/Gilcher wrote:
So what are the standard dependencies ? Just libc and pd ?
I assume you mean dependencies to compile, not requirements to run.
How about my jackx externals. Obviously they need jack installed. Should I remove them from the externals/ directory and move them somewhere else?
Hi,
Yes, ideally the "core" externals should only depend on libraries that make them compile on all platforms (which is libc and pd ATM).
The reason for that is to keep pd cross platform.
Guenter
Gerard
On Sunday 19 October 2003 05:49, Hans-Christoph Steiner wrote:
There really should be documentation for how to do this. Its on my todo list...
Basically, if your external can be compiled as a standalone object and its only dependencies are standard ones, then you can add them to the 'pd-externals' package. You do this by adding files to externals/build/src. Open up the files there to see how its done, its pretty simple. Then each platform has a directory with what it needs to build all those objects. There is currently externals/build/linux, externals/build/darwin, and externals/build/win.
-- electronic & acoustic musics-- http://www.xs4all.nl/~gml
PD-dev mailing list PD-dev@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-dev
hi list,
i encountered a strange phenomenon and do not know if it is a bug? is the dot "." a special character in symbols and i did not know?
following situation: i've got an ip adress aaa.bbb.ccc.ddd stored in a symbol. when i connect 2 chords at the outlet i get the full adress on the first outlet and only aaa on the second. also, if i use 2 netsend with connect messages in one patch the ip adress seems to get lost (except the first 3 digits) sometimes.
i've encountered this in 0.36, 0.37 and a recent cvs version. iohannes zmoellnig has also seen it happen, so maybe he could find better words to describe the bug/behaviour.
platform is linux, tried it out on two computers.
any comments welcome. martin
Only a wild guess, but the . is special in that sense that it is the decimal separator for floats. An IP address does superficially look like a floating point number. Could there some conversion between symbols and numbers happen somewhere?
best greetings, Thomas
----- Original Message ----- From: "martin pi" pi@attacksyour.net To: PD-dev@iem.at Sent: Monday, October 20, 2003 1:23 PM Subject: [PD-dev] symbol bug?
hi list,
i encountered a strange phenomenon and do not know if it is a bug? is the dot "." a special character in symbols and i did not know?
following situation: i've got an ip adress aaa.bbb.ccc.ddd stored in a symbol. when i connect 2 chords at the outlet i get the full adress on the first outlet and only aaa on the second. also, if i use 2 netsend with connect messages in one patch the ip adress seems to get lost (except the first 3 digits) sometimes.
i've encountered this in 0.36, 0.37 and a recent cvs version. iohannes zmoellnig has also seen it happen, so maybe he could find better words to describe the bug/behaviour.
platform is linux, tried it out on two computers.
any comments welcome. martin
http://attacksyour.net/pi http://www.machfeld.net
PD-dev mailing list PD-dev@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-dev