Re: Dynamic loading progress

[Aurélien Aptel]

On Thu, Feb 12, 2015 at 9:34 PM, Eli Zaretskii <address@hidden> wrote:
> Sorry, I don't understand: the Emacs configure script already adds
> that directory to the include path.  So what's wrong?

He's talking about the module Makefile, which is very basic and
standalone (no includes or preprocessing).


> The unresolved externals that are defined by Emacs are expected: you
> need to link against an import library produced as part of building
> emacs.exe.  Otherwise all this stuff will not work on Windows, because
> the Windows port of the linker must see the import library at link
> time.
>
> The flag to produce the import library should be something like this:
>
>    -Wl,--out-implib=libemacs.dll.a
>
> Then you need to link the shared library against -lemacs.

The configure script adds this to Emacs LD flags when modules are enabled:

    -lltdl -Wl,--export-dynamic

What does that do on Windows? I have very little experience in C
programming on Windows, especially using the GNU toolchain.

I want to make this work but this is unknown territory for me. Is
there an up-to-date guide to setup a simple build environment (libs
and all) for Emacs on Windows?