The makefiles for [dssi~] and [pluginhost~] both seem a little messy for Linux compilation. For now I'm returning to ghostess for dssi hosting. As I have time I'll tinker with creating a new makefile for [dssi~]. This is admittedly of little interest to most users, but internal dssi hosting is a worthy option so I'll update here if I sort it out. Thanks everyone who's taken the time to view this.

I am having issues compiling the [dssi~] external on an up-to-date Arch Linux (i386) box, also on Arch Linux Arm. Dependencies listed in Readme are all satisfied.

Code:
cc: error: suppress: No such file or directory
cc: error: unrecognized command line option ‘-bundle’
cc: error: unrecognized command line option ‘-flat_namespace’
makefile:48: recipe for target 'src/dssi~.pd_darwin' failed

The Makefile for dssi~ is unlike the Makefiles for [hid] and [plugin~].

dssi~ seems perhaps deprecated. Did [pluginhost~] actually materialize? Is there a preferred object to host dssi plugins?
`]

Hi all! I've been switching from Ubuntu to Arch and haven't been able to get Puredata off the ground yet. Whether installing puredata (0.44) from repos or pd-extended from AUR or source, I get the error "sh: wish8.5: command not found". The problem of course(/perhaps) is that I have TK8.6 installed, not TK8.5. I found a four year old bug ticket regarding PD 0.42 issues with TK8.6, but that was a while ago. So:

1. Must I downgrade to TK8.5, or will PD work with TK8.6?

if it can work with 8.6,

2. Where does PD launch Wish from? Older info points to a pd.tk file, but it doesn't seem to be present on my system

Update: Downgraded to tcl85 from AUR, pd installation still wants to pull in "tcl" (8.6 which interconflicts with 8.5) as depend. Installed PD with -nodep, exact same error on launch. Hmm.

Thanks! I think I must have monked something up the line, but I wasn't sure which rabbit hole to jump down first. Cheers.

Hmm. If you have some patches in progress perhaps you could attach them to make things clearer. If you're still in the design stages and haven't done much like this in puredata then I would suggest that you start by looking at the [send] [receive] and [select] objects to switch the controller functions and send them where you need. The idea here is to use the launchpad's control output to trigger internal signals which can be changed all at once at the flick of a radio button.

I'm not sure I understand what you're working on, but "pages" sounds like nested pd patches, like a "sequencerthing.pd" and a "stepeditorthing.pd" all accessed from a main patch Maybe that's not what you want. Are you trying to emulate parts of an existing software paradigm/layout (i.e. Ableton, Reason etc.)?