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 <[email protected]> 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 > > _______________________________________________ > [email protected] mailing list > UNSUBSCRIBE and account-management -> > https://lists.puredata.info/listinfo/pd-list >
_______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
