Try removing all old javax.usb class files, jar files, and .so libs
from your system. Make sure you remove them all.
Then rebuild all 3 packages and set your LD_LIBRARY_PATH to the
javax-usb-ri-linux lib directory and it should work.
On Tue, Apr 28, 2009 at 11:39 AM, Woo, Ed wrote:
> Dan,
>
>
>
Dan,
I compiled it myself using ant 1.7.x as ant jars. This is 32bit system on
ubuntu 8.10 linux.
--
Register Now & Save for Velocity, the Web Performance & Operations
Conference from O'Reilly Media. Velocity features a
Tuesday, April 28, 2009 9:41 AM
> To: Woo, Ed
> Cc: [email protected]
> Subject: Re: [javax-usb-devel] UsbException
>
> I believe that means it can't find your native library (libJavaxUsb.so).
>
> On Mon, Apr 27, 2009 at 2:29 PM, Woo, Ed wrote:
>> H
I believe that means it can't find your native library (libJavaxUsb.so).
On Mon, Apr 27, 2009 at 2:29 PM, Woo, Ed wrote:
> Hello,
>
>
>
> I get the following error when I try to call the
> UsbHostManager.getUsbServices()….
>
>
>
> [stderr] java.lang.UnsatisfiedLinkError:
> com.ibm.jusb.os.linux.J
Hello,
I get the following error when I try to call the
UsbHostManager.getUsbServices()
[stderr] java.lang.UnsatisfiedLinkError:
com.ibm.jusb.os.linux.JavaxUsb.nativeSetTraceOutput(ILjava/lang/String;)V
[stderr] at com.ibm.jusb.os.linux.JavaxUsb.nativeSetTraceOutput(Native
Method)
On Tue, 14 Jan 2003 20:56:49 -0500 (EST), [EMAIL PROTECTED] wrote:
Hey Dan:
>technically, javac will complain about an 'ambiguous class' and won't
>compile (which makes sense), but you're right that still we should keep
>the namespace in mind...
True, but that wasn't exactly what I was
On Tue, 14 Jan 2003, Brad BARCLAY wrote:
>On Tue, 14 Jan 2003 19:13:44 -0500 (EST), [EMAIL PROTECTED] wrote:
>
>Hey Dan:
>
>>perhaps all exceptions in javax.usb should be prefixed with 'Usb'...
>
> That's not such a bad idea. If a developer is working with
>another developers code, it can
On Tue, 14 Jan 2003 19:13:44 -0500 (EST), [EMAIL PROTECTED] wrote:
Hey Dan:
>perhaps all exceptions in javax.usb should be prefixed with 'Usb'...
That's not such a bad idea. If a developer is working with
another developers code, it can help them to better understand where
the exception
On Tue, 14 Jan 2003, Brad BARCLAY wrote:
>On Tue, 14 Jan 2003 13:31:03 -0500 (EST), [EMAIL PROTECTED] wrote:
>
> It would be best to have something in javax.usb., but with a
>different name (perhaps USBNotActiveException). This is for two
>reasons:
>
> 1) As some users will want to u
On Tue, 14 Jan 2003 13:31:03 -0500 (EST), [EMAIL PROTECTED] wrote:
>One final issue: I was using javax.usb.NotActiveException for certain
>methods. However, there is also a java.io.NotActiveException. I had
>changed to use that Exception, but it may be better to use a
>javax.usb.NotActiveExcept
One of the known todos is to create more meaningful USB-specific
UsbExceptions. While talking to a coworker, we discussed what to do about
platform-specific errors, i.e. those that aren't USB-specific. We came up
with
PlatformException extends UsbException
{
public Exception getException();
11 matches
Mail list logo
