* Matěj Týč wrote on Sun, Oct 25, 2009 at 03:05:26PM CET: > There is one big issue with AC_SEARCH_LIBS: If you use a different > calling convention than cdecl (like stdcall, but I don't know, they've > just told me), you will get unresolved symbols if you try to link > without a proper include file (or something like that). Which means you > can't rely on that macro, especially when it concerns Windows libraries. > This is quite catastrophic, isn't it? What else than pkg-config would be > the proper solution of this? Is there a generic way to check for a library function with such a different calling convention without knowing the function declaration, nor the header(s) needed to declare it? IOW, does Autoconf have a chance to implement such a check with the information it is given now, or is another API needed? Thanks, Ralf _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
