.dll gurus,
Latest response from Jan Dubois of ActiveState: > On Fri, 24 Aug 2007, Suresh Govindachar wrote: > >> Sisyphus suggested linking with C:/opt/perl/lib/CORE/perl58.lib >> (which does have the symbols in it) in the command that creates >> if_perl.o and/or in the command that builds gvim.exe (which is >> also the command that reports the missing references). >> >> But the build is supposed to use the library dynamically, rather >> than be statically linked. So perl58.dll must tell the linker >> that it will resolve the missing references at run time. >> >> Perhaps although ActiveState added code for the references, they >> are not exposing them to the linker for dynamic use via >> perl58.dll? Or is everything in a dll automatically visible? > > Perl_sv_2iv_flags is exported from perl58.dll. This symbols is > being used by virtually every Perl module containing XS code > because the SvIV() macro will expand into a call to it: > > [in sv.h] > #define SvIV(sv) (SvIOK(sv) ? SvIVX(sv) : sv_2iv(sv)) > ... > #define sv_2iv(sv) sv_2iv_flags(sv, SV_GMAGIC) --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
