If so, how is that normally bundled up? I need people to have external, the help patcher and also a set of scm files on their pd search path for it all to work.
Externals are mainly distributed in binary form (sometimes also with the sources) via Pd's own package manager Deken.
As others have already noted, you should use the pd-lib-builder build system if possible.
Christof
On 10.06.2021 22:19, Iain Duncan wrote:
Hi folks, I'm only a few days away (I think!) from a first beta release for Scheme-for-Pd, and am wondering what I'm supposed to do for releasing to the early testers given I don't want to put it on Deken until it's had the tires well kicked...
Things I need to sort - answers or pointers to where to read both appreciated:
Is it pretty common that people know how to build or should I prepare a binary for OSX and Windows?
If so, how is that normally bundled up? I need people to have external, the help patcher and also a set of scm files on their pd search path for it all to work.
Is there anyone who would be interested in testing out building and running, both from zipped up packages and cloning and building? There's a pretty extensive help file, and everything in it should "just work". (haha, we'll see about that!)
thanks iain
Pd-dev mailing list Pd-dev@lists.iem.at https://lists.puredata.info/listinfo/pd-dev
Thanks everyone. I've got it so that it should be buildable and you ought to be able to run all the examples in the help file. I've put info about status and so on in the readme file. I'd love to hear how people make out building it and what should be different, either by email here or in the github issues tracker.
https://github.com/iainctduncan/scheme-for-pd
thanks! iain
On Thu, Jun 10, 2021 at 5:25 PM Christof Ressi info@christofressi.com wrote:
If so, how is that normally bundled up? I need people to have external, the help patcher and also a set of scm files on their pd search path for it all to work.
Externals are mainly distributed in binary form (sometimes also with the sources) via Pd's own package manager Deken.
As others have already noted, you should use the pd-lib-builder build system if possible.
Christof On 10.06.2021 22:19, Iain Duncan wrote:
Hi folks, I'm only a few days away (I think!) from a first beta release for Scheme-for-Pd, and am wondering what I'm supposed to do for releasing to the early testers given I don't want to put it on Deken until it's had the tires well kicked...
Things I need to sort - answers or pointers to where to read both appreciated:
Is it pretty common that people know how to build or should I prepare a binary for OSX and Windows?
If so, how is that normally bundled up? I need people to have external, the help patcher and also a set of scm files on their pd search path for it all to work.
Is there anyone who would be interested in testing out building and running, both from zipped up packages and cloning and building? There's a pretty extensive help file, and everything in it should "just work". (haha, we'll see about that!)
thanks iain
Pd-dev mailing listPd-dev@lists.iem.athttps://lists.puredata.info/listinfo/pd-dev
Hi Iain,
thank you for this port-amazing!
I need to add the scm directory to Pd's path to avoid the error messages s4pd.scm: can't open test.scm: can't open when opening s4pd-help.pd. You could try adding a [declare -path ../scm] object to the help patch perhaps (untested)?
Furthermore when trying the hello world example from s4pd-help.pd the brackets seem to be posted in a separate line in the Pd window, like this s4pd: "hello world!" s4pd> () Is this intentional?
thanks again! P
- Iain Duncan iainduncanlists@gmail.com [2021-06-11 06:09]:
Thanks everyone. I've got it so that it should be buildable and you ought to be able to run all the examples in the help file. I've put info about status and so on in the readme file. I'd love to hear how people make out building it and what should be different, either by email here or in the github issues tracker.
https://github.com/iainctduncan/scheme-for-pd
thanks! iain
On Thu, Jun 10, 2021 at 5:25 PM Christof Ressi info@christofressi.com wrote:
If so, how is that normally bundled up? I need people to have external, the help patcher and also a set of scm files on their pd search path for it all to work.
Externals are mainly distributed in binary form (sometimes also with the sources) via Pd's own package manager Deken.
As others have already noted, you should use the pd-lib-builder build system if possible.
Christof On 10.06.2021 22:19, Iain Duncan wrote:
Hi folks, I'm only a few days away (I think!) from a first beta release for Scheme-for-Pd, and am wondering what I'm supposed to do for releasing to the early testers given I don't want to put it on Deken until it's had the tires well kicked...
Things I need to sort - answers or pointers to where to read both appreciated:
Is it pretty common that people know how to build or should I prepare a binary for OSX and Windows?
If so, how is that normally bundled up? I need people to have external, the help patcher and also a set of scm files on their pd search path for it all to work.
Is there anyone who would be interested in testing out building and running, both from zipped up packages and cloning and building? There's a pretty extensive help file, and everything in it should "just work". (haha, we'll see about that!)
thanks iain
Pd-dev mailing listPd-dev@lists.iem.athttps://lists.puredata.info/listinfo/pd-dev
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
On 6/11/21 9:04 AM, Peter P. wrote:
I need to add the scm directory to Pd's path to avoid the error messages s4pd.scm: can't open test.scm: can't open when opening s4pd-help.pd. You could try adding a [declare -path ../scm] object to the help patch perhaps (untested)?
https://github.com/iainctduncan/scheme-for-pd/issues/4
and [declare -path ../scm] would be a bad choice for a (properly)
installed version of s4pd, where the scm-scripts would even be in the
same folder as the help-patch ("./"), or in "./scm/").
gfmasdr IOhannes
thanks for the help! So looking at feedback so far it seems to me that I should:
- remove the patchers dir and just put the help patcher in the same level
as s4pd.c
- do something with the pd builder about the scm directory
For the second, there will be multiple scm files the user needs (some optional, but should be in a release). A few questions if people can clarify:
- is it reasonable for these to still be in a scm directory? I could live
with them at top level if need be, there aren't too many. But it could grwo
- can anyone explain what should happen when someone installs a package re
that dir? does the declare -path stuff set up a directory to be automatically added to the Pd file path?
thanks. I'll be able to look at this again later on today, but not for a while. All the tips are much appreciated! iain
On Fri, Jun 11, 2021 at 12:27 AM IOhannes m zmoelnig zmoelnig@iem.at wrote:
On 6/11/21 9:04 AM, Peter P. wrote:
I need to add the scm directory to Pd's path to avoid the error messages s4pd.scm: can't open test.scm: can't open when opening s4pd-help.pd. You could try adding a [declare -path ../scm] object to the help patch perhaps (untested)?
https://github.com/iainctduncan/scheme-for-pd/issues/4
and
[declare -path ../scm]would be a bad choice for a (properly) installed version of s4pd, where the scm-scripts would even be in the same folder as the help-patch ("./"), or in "./scm/").gfmasdr IOhannes
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Hi Peter, I will try to get it so that the scm files do the right thing with declare path.
Regarding the below, what you're seeing there is a null return value being printed to the console. I need to fix the logging controls, but what will happen is that the log-nulls flag will allow one to mute '(), <unspecified> and {gensym} return values, which clutter up the console when you might still want return values of evaluated expressions showing. That will all be the help tab for that bit when I get it done, likely this weekend.
iain
Furthermore when trying the hello world example from s4pd-help.pd the brackets seem to be posted in a separate line in the Pd window, like this s4pd: "hello world!" s4pd> () Is this intentional?
thanks again! P
- Iain Duncan iainduncanlists@gmail.com [2021-06-11 06:09]:
Thanks everyone. I've got it so that it should be buildable and you ought to be able to run all the examples in the help file. I've put info about status and so on in the readme file. I'd love to hear how people make out building it and what should be different, either by email here or in the github issues tracker.
https://github.com/iainctduncan/scheme-for-pd
thanks! iain
On Thu, Jun 10, 2021 at 5:25 PM Christof Ressi info@christofressi.com wrote:
If so, how is that normally bundled up? I need people to have external, the help patcher and also a set of scm files on their pd search path
for it
all to work.
Externals are mainly distributed in binary form (sometimes also with
the
sources) via Pd's own package manager Deken.
As others have already noted, you should use the pd-lib-builder build system if possible.
Christof On 10.06.2021 22:19, Iain Duncan wrote:
Hi folks, I'm only a few days away (I think!) from a first beta release for Scheme-for-Pd, and am wondering what I'm supposed to do for
releasing
to the early testers given I don't want to put it on Deken until it's
had
the tires well kicked...
Things I need to sort - answers or pointers to where to read both appreciated:
Is it pretty common that people know how to build or should I prepare a binary for OSX and Windows?
If so, how is that normally bundled up? I need people to have external, the help patcher and also a set of scm files on their pd search path
for it
all to work.
Is there anyone who would be interested in testing out building and running, both from zipped up packages and cloning and building?
There's a
pretty extensive help file, and everything in it should "just work".
(haha,
we'll see about that!)
thanks iain
Pd-dev mailing listPd-dev@lists.iem.athttps://
lists.puredata.info/listinfo/pd-dev
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management ->
https://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
ok looking over comments I'm realizing I don't actually know what to do with declare path yet and the scm files, so awaiting further clarification!
iain
On Fri, Jun 11, 2021 at 8:25 AM Iain Duncan iainduncanlists@gmail.com wrote:
Hi Peter, I will try to get it so that the scm files do the right thing with declare path.
Regarding the below, what you're seeing there is a null return value being printed to the console. I need to fix the logging controls, but what will happen is that the log-nulls flag will allow one to mute '(), <unspecified> and {gensym} return values, which clutter up the console when you might still want return values of evaluated expressions showing. That will all be the help tab for that bit when I get it done, likely this weekend.
iain
Furthermore when trying the hello world example from s4pd-help.pd the brackets seem to be posted in a separate line in the Pd window, like this s4pd: "hello world!" s4pd> () Is this intentional?
thanks again! P
- Iain Duncan iainduncanlists@gmail.com [2021-06-11 06:09]:
Thanks everyone. I've got it so that it should be buildable and you
ought
to be able to run all the examples in the help file. I've put info about status and so on in the readme file. I'd love to hear how people make
out
building it and what should be different, either by email here or in the github issues tracker.
https://github.com/iainctduncan/scheme-for-pd
thanks! iain
On Thu, Jun 10, 2021 at 5:25 PM Christof Ressi info@christofressi.com wrote:
If so, how is that normally bundled up? I need people to have
external,
the help patcher and also a set of scm files on their pd search path
for it
all to work.
Externals are mainly distributed in binary form (sometimes also with
the
sources) via Pd's own package manager Deken.
As others have already noted, you should use the pd-lib-builder build system if possible.
Christof On 10.06.2021 22:19, Iain Duncan wrote:
Hi folks, I'm only a few days away (I think!) from a first beta
release
for Scheme-for-Pd, and am wondering what I'm supposed to do for
releasing
to the early testers given I don't want to put it on Deken until it's
had
the tires well kicked...
Things I need to sort - answers or pointers to where to read both appreciated:
Is it pretty common that people know how to build or should I prepare
a
binary for OSX and Windows?
If so, how is that normally bundled up? I need people to have
external,
the help patcher and also a set of scm files on their pd search path
for it
all to work.
Is there anyone who would be interested in testing out building and running, both from zipped up packages and cloning and building?
There's a
pretty extensive help file, and everything in it should "just work".
(haha,
we'll see about that!)
thanks iain
Pd-dev mailing listPd-dev@lists.iem.athttps://
lists.puredata.info/listinfo/pd-dev
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management ->
https://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
-
Christof Ressi -
Iain Duncan -
IOhannes m zmoelnig -
Peter P.