We can work through it. I don’t have a windows machine so I haven’t tested it
directly yet. I could get one from school but I have too much going on right
After running make, can you check if there is a “pd.lib” in either the /src or
Judging from the makefiles and Miller’s comment, it seems that the externs are
trying to link to a static pd lib which, I assume, is needed to provide the
symbol table for the dynamic modules. There are a couple of things I’m not sure
* if the auto tools build system creates this static lib
* if this static lib is still required or something we can dispense with
I’m hoping that, with the right settings, we can remove the requirement. If
not, then we need to make sure it’s at least building correctly. Maybe I can
look into how pd-lib-builder handles this.
In any case, I did some checking and I’m not sure that the proper flags set in
the ./configure step for the externals are making it down to their makefiles. I
did a small commit to test that.
Can you pull the latest commit and rerun make. It will probably fail again but
I’d like to see the output form when it compiles bob~.
Thanks! I’m sure this is something that we could solve with a couple of heads
and a windows machine at pd con.
> On Sep 21, 2016, at 4:07 PM, Christof Ressi <christof.re...@gmx.at> wrote:
> Hi Dan,
> Miller just wrote:
>> At the moment I'm compiling Pd using mingw but having to rely on
>> Microsoft Visual C for "pd.lib" (apparently linker information) and
>> all the eterns in "extra" - I never could get that part to work in
> Apparently I'm not the only one who can't manage to get beyond the extra
> folder with MinGW ;-)
Pdfirstname.lastname@example.org mailing list
UNSUBSCRIBE and account-management ->