search for: ac_libtool_win32_dll

...ten"). There > has to be some simpler solution. Anyone? > > Jean-Marc The autotools files can also be used to build Win32 libraries using mingw32 (preferably cross-compiling on GNU/Linux). It's currently possible to build static libs. To be able to build DLLs you need to add AC_LIBTOOL_WIN32_DLL to configure.ac. --- speex-1.2beta2/configure.ac 2007-05-17 16:14:35.000000000 +0200 +++ speex-1.2beta2.my/configure.ac 2007-11-29 23:33:37.000000000 +0100 @@ -30,6 +30,7 @@ AM_MAINTAINER_MODE AC_CANONICAL_HOST +AC_LIBTOOL_WIN32_DLL AM_PROG_LIBTOOL AC_C_BIGENDIAN Mikael

Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: speex_vs2008.diff Type: application/octet-stream Size: 165590 bytes Desc: speex_vs2008.diff Url : http://lists.xiph.org/pipermail/speex-dev/attachments/20071127/08917736/speex_vs2008-0001.obj

...s was. I'm just surprised you took so long to realise it :-). > The autotools files can also be used to build Win32 libraries using > mingw32 (preferably cross-compiling on GNU/Linux). It's currently > possible to build static libs. To be able to build DLLs you need to add > AC_LIBTOOL_WIN32_DLL to configure.ac. For libsndfile, my solution has been : - Use MinGW on windows. - Release pre-compiled binaries. I provide basic instructions for compling using MinGW: http://www.mega-nerd.com/libsndfile/win32.html And if anyone asks why I don't just ship project files, I point the...

...o-_initial_pcmoffset-as-vorbi.patch Type: text/x-patch Size: 1029 bytes Desc: not available URL: <http://lists.xiph.org/pipermail/vorbis-dev/attachments/20180320/998341f5/attachment-0016.bin> -------------- next part -------------- A non-text attachment was scrubbed... Name: 0004-configury-do-AC_LIBTOOL_WIN32_DLL-for-win32-dll-buil.patch Type: text/x-patch Size: 656 bytes Desc: not available URL: <http://lists.xiph.org/pipermail/vorbis-dev/attachments/20180320/998341f5/attachment-0017.bin> -------------- next part -------------- A non-text attachment was scrubbed... Name: 0005-configury-add-Version_sc...

...++ b/configure.ac @@ -22,6 +22,10 @@ AC_INIT(src/flac/main.c) AM_INIT_AUTOMAKE(flac, 1.2.1) m4_ifdef([AM_SILENT_RULES], [AM_SILENT_RULES([yes])]) + +#Prefer whatever the current ISO standard is. +AC_PROG_CC_STDC +AC_USE_SYSTEM_EXTENSIONS # Enable the generation of shared libraries under Win32 AC_LIBTOOL_WIN32_DLL @@ -60,6 +64,7 @@ AC_HEADER_STDC AM_PROG_CC_C_O AC_C_INLINE AC_C_VARARRAYS +AC_C_TYPEOF AC_CHECK_HEADERS(stdint.h) AC_SUBST(HAVE_STDINT_H) @@ -68,6 +73,8 @@ AC_SUBST(HAVE_INTTYPES_H) AC_CHECK_HEADERS(byteswap.h) AC_SUBST(HAVE_BYTESWAP_H) +AC_CHECK_HEADERS([sys/param.h]) + XIPH_C_BSWAP...

...CRO_DIR([m4]) +AM_INIT_AUTOMAKE([foreign -Wall tar-pax no-dist-gzip dist-xz subdir-objects]) m4_ifdef([AM_SILENT_RULES], [AM_SILENT_RULES([yes])]) #Prefer whatever the current ISO standard is. AC_PROG_CC_STDC AC_USE_SYSTEM_EXTENSIONS -# Enable the generation of shared libraries under Win32 -AC_LIBTOOL_WIN32_DLL - -# We need two libtools, one that builds both shared and static, and -# one that builds only static. This is because the resulting libtool -# does not allow us to choose which to build at runtime. -AM_PROG_LIBTOOL -sed -e 's/^build_old_libs=yes/build_old_libs=no/' libtool > libtool-di...