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 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 |
Jau Support Library (C++, Java, ...)Git RepositoryThis project's canonical repositories is hosted on Gothel Software. GoalsThis project aims to provide general C++ and Java collections, algorithms and utilities - as well as basic concepts to support a Java JNI binding. This project was extracted from Direct-BT to enable general use and enforce better encapsulation. API DocumentationUp to date API documentation can be found:
ExamplesSee Direct-BT C++ API Doc. Supported PlatformsMinimum language requirements
See supported platforms for details. Building BinariesIt is advised to include this library into your main project, e.g. as a git-submodule. Then add jaulib/include/ to your C++ include-path and also add the C++ source files under jaulib/src/ into your build recipe. The produced Java libraries are fully functional. This library's build recipe are functional though, but currently only intended to support unit testing and to produce a Doxygen API doc. Build Dependencies
The project requires CMake 3.13+ for building and a Java JDK >= 11. Installing build dependencies for Debian >= 11 and Ubuntu >= 20.04:
To test
To use URL streaming functionality via the
Note: For a generic build use:
The install target of the last command will create the include/ and lib/ directories with a copy of the headers and library objects respectively in your build location. Note that doing an out-of-source build may cause issues when rebuilding later on. Our cmake configure has a number of options, cmake-gui or ccmake can show you all the options. The interesting ones are detailed below: Changing install path from /usr/local to /usr
Building debug build:
Add unit tests to build (default: disabled)
Add unit tests requiring
Disable stripping native lib even in non debug build:
Enable using
Enable using
Disable using
Override default javac debug arguments
Building debug and instrumentation (sanitizer) build:
Using clang instead of gcc:
Cross-compiling on a different system:
To build Java bindings:
To build documentation run:
Cross BuildAlso provided is a cross-build script using chroot into a target system using QEMU User space emulation and Linux kernel binfmt_misc to run on other architectures than the host. You may use our pi-gen branch to produce a Raspi-arm64, Raspi-armhf or PC-amd64 target image. ChangesSee Changes. |