flext-iiwu MacOSX (was: Re: [PD] several patches on one machine?)
atl at comp.lancs.ac.uk
Tue Jan 7 16:47:12 CET 2003
Compiling was pretty annoying, partially because of what you cite.
The specific step you need might be to remove the config.cache file...
configure caches the fact that it didn't find MidiShare.h on the first
go. I think once I got that step, it configured okay.
The iiwusynth-0.2.2 compile presents its own problems, cos the MacOSX
headers it needs are a mix between the MACINTOSH and (default) linux
builds. I just commented stuff out as I went along, (make, edit, repeat)
and then moved the src/.libs/libiiwusynth.a file to /usr/local/lib/, and
Anyway, it was much easier to provide a binary than describe the ad-hoc
hackery that went on last night.
Hope that helps you rolling your own,
david casal said this at Tue, 7 Jan 2003 12:34:08 +0000:
>On Tue, 7 Jan 2003, Adam Lindsay wrote:
>> However, getting iiwu to compile and tracking down MidiShare was much
>> more difficult.
>Well, turns out I spoke too soon. If I'm correct here, flext-iiwu wants
>iiwusynth compiled, which wants midishare? I downloaded the OSX packages
>from GRAME's website and installed, but I can't see a libmidishare.so
>anywwhere, and the only midishare.h (which 'configure' in iiwusynth-0.2.2
>seems to look for) is in the MidiShare Development tools package, in
>C/C++/include folder. Even when I put that in system paths like
>/usr/include or /usr/local, it iiwusynth won't configure with midishare
>Hints? Which version of iiwusynth did you compile? (or am I missing
>something here, and I don't really need to do any of this)
>(now missing debian-world)
>david casal --0+
>d.casal at uea.ac.uk --9+
Adam T. Lindsay atl at comp.lancs.ac.uk
Computing Dept, Lancaster University +44(0)1524/594.537
Lancaster, LA1 4YR, UK Fax:+44(0)1524/593.608
More information about the Pd-list