| Summary: | have java jni bindings, will join | ||
|---|---|---|---|
| Product: | dbus | Reporter: | Carlos Romero <kidcrash> |
| Component: | core | Assignee: | Havoc Pennington <hp> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | high | ||
| Version: | unspecified | ||
| Hardware: | x86 (IA32) | ||
| OS: | Linux (All) | ||
| URL: | http://freedesktop.org/~kidcrash/libdbus-java/ | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
Carlos Romero
2005-04-06 14:12:32 UTC
(In reply to comment #0) > already a member of freedesktop with the xlibs and xserver projects, i would > like dbus added to my list, to import and maintain the java jni binding i have > already started a functional replacement for the current gcj binding in dbus, currently still buggy as i have'nt touched it waiting for it to find a home. the code compiles without warnings. to compile native -- gcc -c org_freedesktop_dbus_*.c `pkg-config --cflags dbus-1` -DDBUS_API_SUBJECT_TO_CHANGE=1 -Wall gcc --shared -o libdbus.so org_freedesktop_dbus_*.o `pkg-config --libs dbus-1` the test is a hal device enumeration, and currently works. Is it even necessary to have a JNI interface? Can this not be done natively over a socket in Java? How is work going on the JNI bindings? There is a new java implementation in git - git://anongit.freedesktop.org/dbus/dbus-java |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.