On 14 February 2014 08:23, Dmitry Timoshkov dmitry@baikal.ru wrote:
-WINE_CONFIG_DLL(xmllite) +WINE_CONFIG_DLL(xmllite,,[implib])
That's auto-generated by make_makefiles from Makefile.in.
Henri Verbeet hverbeet@gmail.com wrote:
On 14 February 2014 08:23, Dmitry Timoshkov dmitry@baikal.ru wrote:
-WINE_CONFIG_DLL(xmllite) +WINE_CONFIG_DLL(xmllite,,[implib])
That's auto-generated by make_makefiles from Makefile.in.
Just a bit of clarification: does that mean that an import library gets added once a Wine component (dll or an application) start to require it and somebody adds a dependency to Makefile.in? If that's the case what should 3rd party users of winelib do when they compile their code and it fails to link because of a missing import library? Shouldn't they be always available if PSDK provides one?
On 16 February 2014 15:17, Dmitry Timoshkov dmitry@baikal.ru wrote:
Henri Verbeet hverbeet@gmail.com wrote:
On 14 February 2014 08:23, Dmitry Timoshkov dmitry@baikal.ru wrote:
-WINE_CONFIG_DLL(xmllite) +WINE_CONFIG_DLL(xmllite,,[implib])
That's auto-generated by make_makefiles from Makefile.in.
Just a bit of clarification: does that mean that an import library gets added once a Wine component (dll or an application) start to require it and somebody adds a dependency to Makefile.in?
Just that you should add a line "IMPORTLIB = xmllite" to dlls/xmllite/Makefile.in, then run tools/make_makefiles, and it will take care of updating configure.ac.