On Tue, 2013-01-22 at 09:27 -0600, Jeremiah Benham wrote: > I wrote autotools files for portmidi and created a tarball of it. At the > moment it only compiles for linux. I then created a gub file. You can > see that in gub/specs/portmidi.py after doing a git pull. Once I have > this working for windows also we can remove > portmidi from denemo. I think it is a mess anyway. Is there any reason > to keep it with out code if we get this working reliably? No, no reason at all - but I am puzzled how the libraries libsmf etc are being found (presumably!) while libportmidi is not - the files from configure.ac downwards appear to be in order. What mystifies me is the autogen.sh step - you said IIRC that gub does not do it - how does it get the makefiles if not?
> I am currentan ly uploading denemo-1.0.0.~rc.7-3.linux-x86 that I just > created linking against this libportmidi.la that was created from this. > I tested and confirm that portmidi is working this way in the linux > build. I just downloaded denemo-1.0.0.~rc.7-3.linux-x8 and installed it on my debian stable box. It errors at startup like this: denemo /home/rshann/bin/denemo: 41: cannot create : Directory nonexistent /home/rshann/denemo/usr/bin/denemo: error while loading shared libraries: libportmidi.so.0: cannot open shared object file: No such file or directory and indeed there is no libportmidi in ~/denemo/usr/lib where the others are. Richard _______________________________________________ Denemo-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/denemo-devel
