Re: [PD-dev] integrating pdlua into Pd-extended

2011-03-27 Thread Hans-Christoph Steiner
Hmm, turns out it was already installed on the Windows build machine, but I just updated it. Something with the way pdlua is being linked makes it not able to find lua51.dll. My guess is because the Lua build system doesn't generate a liblua51.dll.a to put in /usr/local/ lib, like the

Re: [PD-dev] integrating pdlua into Pd-extended

2011-03-27 Thread Martin Peach
I just built that lua-5.1.4 package in MinGW. Just typing 'make mingw'produces liblua.a and lua51.dll in src. liblua.a is somewhat larger than the dll. 'Make install' copies liblua.a into /usr/local/lib and creates an empty directory /usr/local/lib/lua. The error in the latest autobuild log

Re: [PD-dev] integrating pdlua into Pd-extended

2011-03-27 Thread Hans-Christoph Steiner
I think the key is to generate the liblua51.dll.a file using the instructions that were just posted, and stick that into the pdlua folder, set -L., then -llua51 should just work. The .dll.a file seems to expose the DLL symbols in a way that ld understands. If that works, I'll include

Re: [PD-dev] integrating pdlua into Pd-extended

2011-03-27 Thread Hans-Christoph Steiner
Oh, I assumed that a libfoo.a was a complete library for static linking, like on GNU/Linux and Mac OS X, and that the libfoo.dll.a was a special MinGW dlltool format to trick ld into linking against a Windows DLL. That was my impression from reading about the dlltool trick. .hc On