Re: lua 5.2 : modifying the way lua lib is built with mingw

[Vincent Torri <vincent.torri@...>]

On Tue, Mar 23, 2010 at 12:42 AM, Tom N Harris <telliamed@whoopdedo.org> wrote:

On 3/21/2010 11:12 PM, Vincent Torri wrote:

See http://sourceware.org/binutils/docs/ld/WIN32.html , section "direct
linking to a dll". It gives pro and cons of linking against a DLL and
against an import lib

Lua doesn't use aliases nor static objects, so the justifications for import libraries don't apply. And you can't (easily) use external modules when Lua is linked into the application.

Be glad Lua doesn't use autoconf+automake+libtool. The way it is now, Lua is simple to integrate into any project.

no, it is not simple to integrate it.

1) I have to write myself the .pc file to integrate it to a  project (not the case for lua 5.1.* though). By not providing that .pc file in lua 5.2, you are breaking *all* the projects that are currently using it.

2) on Windows, as there is no import or static lib, i have to copy files or write another Makefile; or modify the build system of that project (which is actually not an option).

Vincent Torri