As far as I can tell, zexy is unbuildable on Windows unless you have the complete Pd source and you have built that source. This is because you need to use the autotools system, and it only knows about that kind of setup. The Pd-extended binary package includes everything needed to build zexy (headers, pd.dll).
export PATH="/usr/local/bin:/bin:/usr/bin:$PATH" autoreconf --install --force --verbose ./configure --disable-library --prefix= --libdir="$WORKSPACE/DESTDIR" --with-pd="$PROGRAMFILES/pd" CPPFLAGS="-I$PROGRAMFILES/pd/include/pd" EXTRA_LTFLAGS="-L$PROGRAMFILES/pd/bin" LDFLAGS="-L$PROGRAMFILES/pd/bin" make
And it always dies on linking:
make[2]: Entering directory `/c/pd-jenkins-build/workspace/zexy/label/windowsxp-i386/src' /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -IC:\Programme/pd -IC:\Programme/pd/include/pd -g -O2 -mms-bitfields -MT 0x260x260x7e.lo -MD -MP -MF .deps/0x260x260x7e.Tpo -c -o 0x260x260x7e.lo 0x260x260x7e.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -IC:\Programme/pd -IC:\Programme/pd/include/pd -g -O2 -mms-bitfields -MT 0x260x260x7e.lo -MD -MP -MF .deps/0x260x260x7e.Tpo -c 0x260x260x7e.c -DDLL_EXPORT -DPIC -o .libs/0x260x260x7e.o mv -f .deps/0x260x260x7e.Tpo .deps/0x260x260x7e.Plo /bin/sh ../libtool --tag=CC --mode=link gcc -g -O2 -mms-bitfields -module -avoid-version -shared -shrext .dll -no-undefined -LC:\Programme/pd/bin -Xlinker -l:pd.dll -LC:\Programme/pd/bin -LC:\Programme/pd/bin -o 0x260x260x7e.la -rpath c:\pd-jenkins-build\workspace\zexy\label\windowsxp-i386/DESTDIR/zexy 0x260x260x7e.lo -lregex -lm -lgdi32 -luser32 -lkernel32 -lcoldname -lcrtdll libtool: link: gcc -shared .libs/0x260x260x7e.o -LC:\Programme/pd/bin -lregex -lgdi32 -luser32 -lkernel32 -lcoldname -lcrtdll -O2 -mms-bitfields -Wl,-l:pd.dll -o .libs/0x260x260x7e.dll -Wl,--enable-auto-image-base -Xlinker --out-implib -Xlinker .libs/0x260x260x7e.dll.a c:/mingw/bin/../lib/gcc/mingw32/4.7.0/../../../../mingw32/bin/ld.exe: cannot find pd.dll collect2.exe: error: ld returned 1 exit status make[2]: *** [0x260x260x7e.la] Error 1 make[2]: Leaving directory `/c/pd-jenkins-build/workspace/zexy/label/windowsxp-i386/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/c/pd-jenkins-build/workspace/zexy/label/windowsxp-i386' make: *** [all] Error 2 Build step 'Execute shell' marked build as failure
.hc
On 02/18/2013 21:07, Hans-Christoph Steiner wrote:
As far as I can tell, zexy is unbuildable on Windows unless you have the complete Pd source and you have built that source.
zexy has been built on windows since 1999, without having the need to build Pd yourself. that was long before i started to use autotools, and there are still a number of build systems included in zexy that are exclusively useable on w32.
c:/mingw/bin/../lib/gcc/mingw32/4.7.0/../../../../mingw32/bin/ld.exe: cannot find pd.dll collect2.exe: error: ld returned 1 exit status
but i'll have a look at this.
fgamdsr IOhannes
On 02/18/2013 04:03 PM, IOhannes m zmölnig wrote:
On 02/18/2013 21:07, Hans-Christoph Steiner wrote:
As far as I can tell, zexy is unbuildable on Windows unless you have the complete Pd source and you have built that source.
zexy has been built on windows since 1999, without having the need to build Pd yourself. that was long before i started to use autotools, and there are still a number of build systems included in zexy that are exclusively useable on w32.
c:/mingw/bin/../lib/gcc/mingw32/4.7.0/../../../../mingw32/bin/ld.exe: cannot find pd.dll collect2.exe: error: ld returned 1 exit status
but i'll have a look at this.
Its obviously possible since its built as part of Pd-extended every night. It seems I committed some stuff in externals/Makefile that works some magic that I cannot reproduce on the MinGW terminal. You can see a history of my attempts here:
https://macosx105-i386.pdlab.puredata.info/job/zexy/
.hc
-
Hans-Christoph Steiner -
IOhannes m zmölnig