Re: [softwerk-dev] Troubles with Softwerk

[Paul Barton-D. <pb...@op...>]

>My problems started with your custom libraries (gtkmmext, guileconfig,
>midi++, pbd). It appears that when doing a make install each package
>(pbd in particular) installs a m4 macro file into
>/usr/local/share/aclocal/.

Shouldn't happen that way. The tarball is setup to do a 100% local
install into <softwerk-dir>/libs/... Nothing gets installed outside of
that unless you install softwerk itself, which isn't the plan right now.

Did you follow the precise instructions for the tarball compile that
are in README ?

>The configure script for the other libs still reported that my libpbd
>install wasn't sane. Though I noticed it listed the version (1.1.1)
>which satisfied the check (1.1.0). This problem is not occuring now,
>though I was messing with these macros. Not sure why it works now.

This seems to be related to LD_LIBRARY_PATH. I am not sure of the
connection at this point.

>So I WAS getting a seg fault on startup. It appears that was due to an
>invalid path in the softwerkrc.scm to softwerk_ui.rc.

Quite possible. Error checking for user error is very thin at this time.

>How do you configure Softwerk to use an ALSA sequencer client:port? I

You can't. If you want to write the code, feel free. I have little or
no use for the sequencer, and I've never written any code to deal with it.

>Happy to report that it now works (starts up), while I'm writing this
>email. Can't try it though until I can get the sequencer interface
>working.

I take it you have no "true" MIDI devices then ? Just those silly
wavetable synths that require their device driver to translate MIDI
into register fiddling ?

--p