And these are the changes in the configure script. I don't recall
exactly why I just removed the check for mingw ONLY but what I do
remember is gcc will not link any libraries unless they start with lib.
So the workaround was to remove the check and rename the library to
libftd2xx.a if i recall...
/Ake
urjtag/configure.ac | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/urjtag/configure.ac b/urjtag/configure.ac
index 3c0ce81..7758fb4 100644
--- a/urjtag/configure.ac
+++ b/urjtag/configure.ac
@@ -295,7 +295,7 @@ AS_IF([test "x$with_ftd2xx" = xyes -o
"x$with_ftd2xx" = xcheck], [
AS_IF([test "x$with_ftd2xx" != xno], [
HAVELIBFTD2XX=yes
case $host in
- *cygwin*|*mingw*)
+ *cygwin*|*xxxmingw*)
CFLAGS="$CFLAGS -I$with_ftd2xx"
AS_IF([test -d "$with_ftd2xx/i386"], [
FTD2XXLIB="$with_ftd2xx/i386/ftd2xx.lib"
@@ -328,7 +328,7 @@ AC_ARG_WITH([inpout32],
[], [with_inpout32=auto])
case $host in
- *cygwin*|*mingw*) ;;
+ *cygwin*|*xxxmingw*) ;;
*) with_inpout32=no ;;
esac
Post by Geert StappersPost by Ã
ke RehnmanPost by Geert StappersI am currently trying to compile UrJTAG using Cygwin
./configure --host=i586-mingw32msvc --with-ftd2xx=~/ftd2 --with-inpout32
After having added the ftd2xx.h file to the usbconn directories in
/tap and /include as an error message demanded of me, I seem to be
gcc  -g -O2 -I~/ftd2 -Wall  -o jtag.exe jtag.o -Lcmd -lcmd -Ltap -ltap -Lpart
-lpart -Llib -ljtaglib -Lflash -lflash -Ltap -ltap -Lflash -lflash -Lbus -lbus
-lm ~/ftd2/ftd2xx.lib -lintl -Lsvf -lsvf -Lbsdl -lbsdl  -lusb
/usr/lib/gcc/x86_64-pc-cygwin/5.4.0/../../../../x86_64-pc-cygwin/bin/ld: cannot find -lpart
/usr/lib/gcc/x86_64-pc-cygwin/5.4.0/../../../../x86_64-pc-cygwin/bin/ld: cannot find -lsvf
collect2: Fehler: ld gab 1 als Ende-Status zurück
As is apparent, the linker seems to be incompatible with libpart.a and libsvf.a.
I have added every single "devel" or library package the Cygwin setup offers me.
Does someone know what I am doing wrong?
libsvf and libpart are libraries generated from urjtag source.
I don't known how cygwin handles such libraries.
My advice is to compare the cygwin buildlog with a Linux buildlog such as
at https://buildd.debian.org/status/fetch.php?pkg=urjtag&arch=arm64&ver=0.10%2Br2052-1&stamp=1481752319&raw=0
the problem probably arised much earlier where libpart and libsvf
and was compiled.
Run make again without cleaning and those errors should be clearly
visible through all garbage on the console.
And rerunning configure wouldn't harm.
Post by Ã
ke RehnmanAs a side note, unless someone has fixed the configure script UrJtag
doesn't build under cygwin with ftdi-drivers.
These days we do accept patches.
Groeten
Geert Stappers