Robert Huber

Hi Stephen, i am on 10.11.6 El Capitan. That OS definitely activates the unix module in the pom.xml in my hands. i dont think there is much need for a cross-compile, so restricting the linux build in the <family>unix</family> to <name>Linux</name> will do no harm but solves the problem I ran into. P.S. Yes, the Xcode CLI is used in a lot of the installs like Macports and others. Be well,

mvn compile issue on mac with fix

it even seems to use the correct driver (1.4.8) but device is still claimed from previous ones despite unload of modules. FTDI Device: 0 Type : FT_DEVICE_UNKNOWN Descr : SerNum : Open : true Speed : false Class : class net.sf.yad2xx.Device Driver : 1.4.8 java.lang.IllegalStateException: Device in use at net.sf.yad2xx.Device.open(Device.java:211) at Tests_Control.Test_FTDIDeviceManager.main(Test_FTDIDeviceManager.java:27) and if we prevent the built in driver from loading in the first place then none...

ok, no prob with unloading the driver ... when i plug in the click $ lsmod ftdi_sio 53248 2 usbserial 45056 5 ftdi_sio $ ls /dev/tty* /dev/ttyUSB0 /dev/ttyUSB1 after the unload all of these entries are gone ... good so far. i then run $ sudo java -jar ~/yad2xx-master/yad2xxJava/target/yad2xxJava-1.0-jar-with-dependencies.jar net.sf.yad2xx.samples.ListDevices but i get ... no main manifest attribute, in /home/admin_lab/yad2xx-master/yad2xxJava/target/yad2xxJava-1.0-jar-with-dependencies.jar running...

hi stephen, confirming a clean compile, the FTDIclick is recognized, but, as you suspected, the built in usbserial driver grabs a hold of it as soon as I plug the click in. $ ls /dev/tty* lists ttyUSB0 and ttyUSB1 for the two devices of the FT2232H i consulted the ftdi readme https://www.ftdichip.com/Drivers/D2XX/Linux/README.dat which tells me to unload the ftdi_sio and usbserial drivers you must unload this driver (and usbserial) if it is attached to your device ("rmmod ftdi_sio" and "rmmod usbserial"...

dang it. yes you are so very right. that is exactly what i had missed. i added the lines and i get a spanking clean new compile of the lib for linux. cant wait to put it through its paces today. will report. i am using the openjdk 8 for compile and 11 for run time. thanks for updating the github readme. confirming that it works as writen in my hands.

it then fails to find -lftd2xx during gcc compile ... any suggestions? thanks [INFO] /bin/sh -c cd /home/admin_lab/Downloads/yad2xx-master/yad2xxSo && gcc -shared -o /home/admin_lab/Downloads/yad2xx-master/yad2xxSo/target/soFTDIInterface.so target/objs/FTDIInterface.o -lftd2xx -L/usr/local/lib /usr/bin/ld: cannot find -lftd2xx collect2: error: ld returned 1 exit status [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] Yet Another...

one step further. the missing jni.h was due to the missing JAVA_HOME path after restart. 3 ways to solve it ... set it (temproarily for you only) in your terminal $ export JAVA_HOME="/usr/lib/jvm/java-1.8.0-openjdk-amd64" or (for you and it remains after restart) add this line to your .bashrc file, save it, and force it to rerun from the terminal export JAVA_HOME="/usr/lib/jvm/java-1.8.0-openjdk-amd64" $ source ~/.bashrc or (permanently for all users) add the line to /etc/profile and restart export...