• gyokimae

    Hi, sorry to pull up this old topic.

    This somewhat overlaps with my recent post to [pd-dev] list.
    After the posting, I had made some progress and came up with a new question while discovering this thread which seemed very relevant.

    Struggling to get my externs built on Windows, I've been working both in VC++ Express 2008 and MSYS.

    Under both environments, the "hello world" code on the "EXTERNALS HOWTO" page build fine. Well, with minimal knowledge of C and zero experience in mangling with existing OSS, I did spend a good amount of time with VC++ before reaching configurations identical to ones mentioned earlier in this thread.

    However, with the next "counter" example, I would face problems related to the fact that "s_float" cannot resolved.

    Under VC++, the link would simply fail due to the unresolved _s_float symbol... until this morning.. I've tried linking to the pd.lib file contained in a version of Pd later than I tried earlier in order to gather error messages for this post. For some reason it seems to work now.

    The situation remains the same with MSYS.
    I get the following message during linking. Although the .dll file is created, Pd does not load the external properly.

    $ ld -E -shared -o gcounter.dll gcounter.o pd.dll
    Info: resolving _s_float by linking to __imp__s_float (auto-import)

    (gcounter is just a name a gave to the simple counter example to avoid conflict with existing objects in pd-extended)

    After working on this for a few nights, I've finally got files built in VC++ working so I am somewhat relaxed now.
    I would, however, appreciate advise on what may be going on with the MSYS builds. Again, "helloworld" builds and runs great. Only after s_float symbols are introduced do I see behaviors I cannot understand.

    Thanks.

    --
    David Shimamoto

    posted in extra~ read more
Internal error.

Oops! Looks like something went wrong!