File: control

package info (click to toggle)
libjna-java 4.5.2-1
  • links: PTS, VCS
  • area: main
  • in suites: bullseye, buster, sid
  • size: 9,844 kB
  • sloc: java: 75,159; ansic: 4,781; xml: 4,585; makefile: 434; sh: 235
file content (81 lines) | stat: -rw-r--r-- 3,388 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
Source: libjna-java
Section: java
Priority: optional
Maintainer: Debian Java maintainers <pkg-java-maintainers@lists.alioth.debian.org>
Uploaders:
 Jan Dittberner <jandd@debian.org>,
 Ludovic Claude <ludovic.claude@laposte.net>,
 Andrew Ross <ubuntu@rossfamily.co.uk>
Build-Depends:
 ant,
 ant-optional,
 debhelper (>= 11),
 default-jdk,
 default-jdk-doc,
 javahelper (>=0.32~),
 libffi-dev,
 libx11-dev,
 libxt-dev,
 maven-repo-helper (>= 1.5~),
 pkg-config
Standards-Version: 4.2.0
Vcs-Git: https://salsa.debian.org/java-team/libjna-java.git
Vcs-Browser: https://salsa.debian.org/java-team/libjna-java
Homepage: https://github.com/twall/jna

Package: libjna-java
Architecture: all
Depends: libjna-jni, ${misc:Depends}
Suggests: libjna-java-doc
Description: Dynamic access of native libraries from Java without JNI
 JNA provides Java programs easy access to native shared libraries without
 writing anything but Java code - no JNI or native code is required. This
 functionality is comparable to Windows' Platform/Invoke and Python's ctypes.
 Access is dynamic at runtime without code generation.
 .
 JNA's design aims to provide native access in a natural way with a minimum of
 effort. No boilerplate or generated code is required. While some attention is
 paid to performance, correctness and ease of use take priority.
 .
 The JNA library uses a small native library stub to dynamically invoke native
 code. The developer uses a Java interface to describe functions and structures
 in the target native library. This makes it quite easy to take advantage of
 native platform features without incurring the high overhead of configuring and
 building JNI code for multiple platforms.

Package: libjna-jni
Architecture: any
Depends: ${misc:Depends}, ${shlibs:Depends}
Description: Dynamic access of native libraries from Java without JNI (native libs)
 JNA provides Java programs easy access to native shared libraries without
 writing anything but Java code - no JNI or native code is required. This
 functionality is comparable to Windows' Platform/Invoke and Python's ctypes.
 Access is dynamic at runtime without code generation.
 .
 This package contains the native libraries for libjna-java

Package: libjna-platform-java
Architecture: all
Depends: libjna-java, ${misc:Depends}
Replaces: libjna-java (<< 3.4.2)
Breaks: libjna-java (<< 3.4.2)
Description: Dynamic access of native libraries from Java without JNI (platform extension)
 JNA provides Java programs easy access to native shared libraries without
 writing anything but Java code - no JNI or native code is required. This
 functionality is comparable to Windows' Platform/Invoke and Python's ctypes.
 Access is dynamic at runtime without code generation.
 .
 This package contains the platform library with many native functions already
 mapped as well as a set of utility interfaces that simplify native access.

Package: libjna-java-doc
Section: doc
Architecture: all
Depends: ${misc:Depends}
Description: Dynamic access of native libraries from Java without JNI (documentation)
 JNA provides Java programs easy access to native shared libraries without
 writing anything but Java code - no JNI or native code is required. This
 functionality is comparable to Windows' Platform/Invoke and Python's ctypes.
 Access is dynamic at runtime without code generation.
 .
 This package contains the Javadoc API documentation.