chromatic wrote: > On Sat, 2005-02-05 at 12:58 -0800, chromatic wrote: >> Why not generate the .def file instead of hoping that people add the >> correct symbols? Here's a patch that seems to do the trick for me >> (though not running Windows, I can't really test if the defines are all >> correct). > Actually it doesn't, because of a typo in the makefile source. Ignore > that one in favor of this one.
I haven't checked the details, but I think this will not work, as it seems to generates a list of all symbols beginning with nci_, but 'int_cb_D4' is used, too. Previously, I have proposed adding 'PARROT_API' to declarations, and grep for them, or expand them to '__declspec(dllexport)' on Windows. #31649: [TODO] Win32 - Automatically Export Symbols http://rt.perl.org/rt3/Ticket/Display.html?id=31649 Another idea would be to create a "symbol list file" for each library, which contains only the symbol names, from which the .def file would be derived (maybe another platform has similar needs?). Ron
