summaryrefslogtreecommitdiffstats
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
* MappedByteBufferInputStream: Reduce dependency to PlatformSven Gothel2023-01-231-5/+5
|
* NativeLibrary.enumerateLibraryPaths(): Reduce relative/absolute path mapping ↵Sven Gothel2023-01-231-9/+12
| | | | to 'java.library.path', others are absolute
* JNILibLoaderBase.loadLibraryInternal(): Produce own detailed exception if ↵Sven Gothel2023-01-231-3/+6
| | | | | | lib couldn't be loaded (avoid showing misleading orig exception) .. and detail some debug output. Both, own exception and debug output expose NativeLibrary.getSystemEnvLibraryPaths()
* NativeLibrary.enumerateLibraryPaths(): Using addPaths() ensures given 'path' ↵Sven Gothel2023-01-231-14/+51
| | | | | | is being resolved as absolute-canonical as required for System.load*() Further, detailed DEBUG messages are added on -Djogamp.debug.NativeLibrary
* NativeLibrary: Add getSystemEnvLibraryPaths(), i.e. LD_LIBRARY_PATH, PATH, ↵Sven Gothel2023-01-231-0/+35
| | | | .. content
* Formatting: BindingJNILibLoader, AWTEDTExecutorSven Gothel2023-01-232-29/+29
|
* src/junit/com/jogamp/gluegen/test/junit/generation/test1.h: Fix warnings re ↵Sven Gothel2023-01-151-3/+3
| | | | 'const' qualifier
* TestRecursiveLock01, TestRecursiveThreadGroupLock01: 'yield()' -> ↵Sven Gothel2023-01-152-6/+6
| | | | 'yield_thread()' to avoid potential Java>17 collision (JEP 361)
* TestIteratorIndexCORE: Fix template usageSven Gothel2023-01-151-11/+11
|
* SecurityUtil: Skip System's SecurityManager action for getSecurityManager() ↵Sven Gothel2023-01-151-7/+31
| | | | and doPrivileged() for Java17+
* Default build is JDK-17, prepare up to Java-21 (next LTS); ↵Sven Gothel2023-01-152-35/+64
| | | | | | | | PlatformPropsImpl: Remove static OSXVersion and Version* vars, add JAVA_17 and JAVA_21 flag. PlatformPropsImpl's static OSXVersion is JOGL specific and will be moved into its GLContextImpl. PlatformPropsImpl's static Version are not required and eats up memory where it can be used transitionary.
* Replace AccessController.doPrivileged() w/ SecurityUtil.doPrivileged()Sven Gothel2023-01-1414-38/+58
|
* Fix unit test1.hSven Gothel2023-01-141-2/+2
|
* MacOS: Add fat universal build w/ x86_64 + aarch64; Bump min SDK version >= 11.0Sven Gothel2023-01-141-0/+4
|
* WeakIdentityHashMap: Always null check on weakRef.get(); ↵Sven Gothel2019-12-311-18/+23
| | | | IdentityWeakReference: hash is final.
* WeakIdentityHashMap: Refine capacity computation; Bitfield.Util add ↵Sven Gothel2019-12-312-2/+105
| | | | 'PowerOf2' functions
* WeakIdentityHashMap: Cleanup; Implement putAll(..); Make ↵Sven Gothel2019-12-311-30/+61
| | | | IdentityWeakReference static
* Add WeakIdentityHashMap implementation (from Apache Avro)Sven Gothel2019-12-301-0/+229
| | | | | | | | | | Origin <https://github.com/apache/avro/blob/master/lang/java/avro/src/main/java/org/apache/avro/util/WeakIdentityHashMap.java> from their commit 70260919426f89825ca148f5ee815f3b2cf4764d. Apache License Version 2.0 until. Using our JogAmp 'New BSD 2-Clause License' for changes after this initial commit. Related to Bug 1312, where we like to utilize a WeakIdentityHashMap, allowing to have cached shared GLContext to disappear .. a compromise.
* Bug 1417 - Android: Context.MODE_WORLD_READABLE causes SecurityException on ↵Sven Gothel2019-12-262-2/+2
| | | | API >= 24, use Context.MODE_PRIVATE for temp cache
* Bug 1417 - Android: Add new x86 MachineDataInfo, differs due to smaller ↵Sven Gothel2019-12-101-0/+3
| | | | 'long double' than regular x86_32_unix
* Bug 1417 - Android: Complete 1st round: ↵Sven Gothel2019-12-101-1/+2
| | | | | | | | | make/lib/gluegen-cpptask-android-<abi>.xml and scripts All aligned now - gluegen-cpptasks-android-aarch64.xml - gluegen-cpptasks-android-armv6.xml (this has ld flag --no-undefined disabled, due to internal missing symbols) - gluegen-cpptasks-android-x86.xml
* Bug 1412 - JNI: GlueGen JavaEmitter: Check & Handle Exception after calling ↵Sven Gothel2019-12-061-0/+7
| | | | | | | back into Java The generated JNI code JVMUtil_NewDirectByteBufferCopy(..) calls Buffers.newDirectByteBuffer(..) and potential exceptions should be checked.
* minor autocleanup (final removed from static)Sven Gothel2019-11-281-1/+1
|
* Bug 1363: Java 11: Extract and extend sun.misc.Unsafe functionality to ↵java11iosSven Gothel2019-09-042-28/+234
| | | | | | | | | | | | | | | UnsafeUtil UnsafeUtil centralizes the workarounds (hack) of certain Java>=9 modularization encapsulation pitfalls, where no exports have been defined. The last resort. 1) Buffers utilizes UnsafeUtil for Java>=9 invokeCleaner. 2) To gain access for certain methods + fields w/o 'illegal access warnings', we have to temporarily disable the IllegalAccessLogger. Hence we provide a method 'T doWithoutIllegalAccessLogger(..<T> action)' for our essential module access under Java >= 9.
* Bug 1363: Java 11: Revert CStructAnnotationProcessor's ↵Sven Gothel2019-08-191-1/+1
| | | | | | | | | | | | | | | | | @SupportedSourceVersion back to 11 Behold, the issue as documented at commit 2d89df89453c099d4e357aa17eae88efcf1d1b70, one build machine failing to compile SourceVersion.RELEASE_11 was due to an incomplete installation of openjdk-11-jdk on Debian GNU/Linux. Wow. I have re-installed the openjdk-11-jre and openjdk-11-jdk packages on said machine, ensured they are being used .. and it works. Another note here regarding usage of OpenJDK11 compile time environment and Java8 target. If using Eclipse, I had to set the system runtime JDK to JDK 8. Otherwise the 'editor clean-up' jobs would run against the JDK 11 classes and wrongly so change certain type castings etc, incompatible with Java 8. If anybody knows a solution here .. shoot.
* Bug 1363: Java 11: Document Java8 target constraints; Fix one odd compile issueSven Gothel2019-08-191-1/+1
| | | | | | | | | | | | | | Document Java8 target constraints, i.e. where we need to set source, target and bootclasspath to ensure target runtime Java8 compliance. Fix one odd compile issue! Using two theorethical identical GNU/Linux Debian 10 machines with same set of installed software, one passes (like MacOS, Windows) and one fails. The failure was due to the CStructAnnotationProcessor's @SupportedSourceVersion tag. This downgrades the SourceVersion's previous bump from 6->11 (commit 610493b1724b5d91327f478338ff5d029bdcc032) down to 8. Interesting times ..
* Windows Regression: Mingw64 8.1.0 using statical linked tool lib ↵Sven Gothel2019-08-191-0/+271
| | | | | | | | | | | | | | | | | | | Test1p1Test1p1JavaEmitter 'com.jogamp.gluegen.test.junit.generation.Test1p1JavaEmitter' exposes a regression using MingW64 8.1.0: System.loadLibrary() gives a "Can't find dependent libraries". Here, 'Bindingtest1p1' is linked against 'test1' and fails to load due to its wrong dependent library name within 'Bindingtest1p1'. MingW64 8.1.0 dropped 'libtest1.so' into 'Bindingtest1p1.dll', which is surely wrong. Even passing '-Wl,-soname=test1.dll' didn't help. Note: Such constellation would only work with adding the lib-path to PATH on Windows. Since we don't utilize the method in any of our projects, but use the dynamic library lookup method - this is not a blocker, but wasted some good time.
* Bug 1363: Java 11: Resolve Buffers.Cleaner implementationSven Gothel2019-08-194-13/+68
| | | | | | | | | | | As of Java9, sun.misc.Cleaner has moved to jdk.internal.ref.Cleaner. However, access has been made (under the table) via sun.misc.Unsafe, which we are using for now as we cannot set the jdk.internal.ref.Cleaner method accessible. In this regard, we had to change our Cleaner.clean(..) method using a ByteBuffer instead of a Buffer object paramter. All tests have passed, no more illegal access case running on Java11 has been exposed.
* Bug 1363: Java 11: Complete renaming JEP 178 compatible native lib basename ↵Sven Gothel2019-08-187-9/+9
| | | | | | | | | | gluegen-rt -> gluegen_rt - Fix finding native library for Elf parsing - Fix one unit test - Fix comments Completes commit 330dad069dee5a0cc0480cf5cd9052000004223a
* MacOS shall only scan for .dylib, dropping .jnilib search in NativeLibrarySven Gothel2019-08-181-5/+0
|
* Fixed CStruct annotation processor to not use dummy Java variable typesWade Walker2019-08-162-2/+2
| | | | | | | | | When annotations were placed on dummy Java variables, the annotation processor was emitting a RenameJavaType directive into the gluegen config file that caused the emitted file to be named boolean.java instead of RenderingConfig.java or Pixel.java. Turned off this behavior when jname is given in the @CStruct annotation. I'm uncertain how much this processor is even used, since I can't find any occurrences of @CStruct outside the test code for it in gluegen.
* Fixed null pointer exception in logging printWade Walker2019-08-161-1/+4
|
* Fix warning in annotation processorWade Walker2019-08-161-1/+1
|
* Ported NativeTaglet to jdk.javadoc.doclet.TagletWade Walker2019-08-161-79/+66
| | | | The old com.sun.tools.doclets.Taglet was removed, so had to move to new API.
* iOS: NativeLibrary: Refine iOS, use proper alt system path for iOS+OSX, ↵Sven Gothel2019-06-214-36/+48
| | | | relax closeLibrary(..)
* Bug 1363: Java 11: Recognize Java9+ ..; Support JEP 178 static linkage ↵Sven Gothel2019-06-175-6/+67
| | | | | | | | | | | | | | | | | | | | | libgluegen-rt[.so] -> libgluegen_rt[.so|.a] Recognize Java9+ .. - Recognize new Java9+ version string as of JEP 223 - Avoid Classpath's private findLibrary call +++ Support JEP 178 static linkage (OpenJDK 1.8) - Need to change native library basename: libgluegen-rt[.so] -> libgluegen_rt[.so|.a] since the dash '-' is not supported in a ANSI-c function name. - Added 'JNI_OnLoad_gluegen_rt' to recognize statical linked JNI code - Added JNI_VERSION_1_8 to jni/jni.h
* iOS: Initial iOS support commit: build.xml targets, java code-path etcSven Gothel2019-06-178-11/+48
| | | | | | | | | | | | Current build system for JogAmp iOS Build is: - Build Machine: OSX Mojave 10.14 - Using own (still proprietary) OpenJDK 9 iOS Build - OpenJDK 1.8 (This will be replaced by OpenJDK 11 soon) - Xcode 10.2
* Bug 1369: SCC: Hide SHA Algorithm bit size in literals of SpecificationSven Gothel2019-04-033-43/+42
| | | | | Implementation currently uses 256 bit Secure Hash (SHA) algorithm, but this may change in the future. Hence only use 'SHA' in the names, not 'SHA256'.
* Bug 1367: TempJarCache: Fix Unit Test using ReflectionsSven Gothel2019-04-031-4/+4
|
* Bug 1369: Source Certification Contract (SCC): Initial SHA256 fingerprint & ↵Sven Gothel2019-04-036-1/+523
| | | | | | | | | | | | | | | | | | | | | runtime validation This change implements a strong SHA256 signature over: 1) source tree inclusive make recipe (SHA256-Source) 2) all class files (SHA256-Classes) 3) all native libraries (SHA256-Natives) 4) the class files as deployed in the jar (SHA256-Classes-this) 5) the native libraries as deployed in the jar (SHA256-Natives-this) and drops all of these in the deployed Jar file. This allows SHA256 validation of (4) + (5) at runtime and further complete validation (1), (2) and (3) offline. Full SCC would now required (1) - (3) to be placed on a server for further validation. Optionally we may use GPG <https://gnupg.org/> or PGP to validate the build entity to implement the chain of trust <https://en.wikipedia.org/wiki/Chain_of_trust> The SHA256 runtime validation is tested via: com.jogamp.common.util.TestVersionInfo
* Bug 1367: Make TempFileCache & TempJarCache even if temp folder can't handle ↵Sven Gothel2019-04-038-52/+142
| | | | executables
* Bug 1366 - Use String.format((Locale)null, "..." ..) avoiding Locale output ↵Sven Gothel2019-03-305-9/+14
| | | | for System related Operations
* Merge branch 'master' of git://github.com/pini-gh/gluegen into pini-gh-masterSven Gothel2019-03-261-1/+2
|\
| * Support architecture ppc64le (Debian ppc64el).Gilles Filippini2015-10-281-1/+2
| |
* | Merge pull request #33 from diegopl/bug_1300Sven Gothel2019-03-261-9/+14
|\ \ | | | | | | Use system property to detect Android
| * | Use system property to detect AndroidDiego Perez2016-04-061-9/+14
| | |
* | | Merge pull request #25 from ghost/masterSven Gothel2019-03-261-2/+3
|\ \ \ | | | | | | | | adding support for android x86 targets - revised
| * | | added android x86 support.Xavier Hallade2015-02-161-2/+3
| | | |
* | | | Bug 1219, Bug 1231: Re-add executable test by executionSven Gothel2019-03-251-10/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Re-adding executable test by execution is required for 'blocker technology' like Windows's 'Software Restriction Policies (SRP)', which only gets activated by the actual execution attempt. Merely testing the file's (ACL) execution flags via NIO's isExecutable is not sufficient. Implementation first tests the file's (ACL) execution flags via NIO's isExecutable. If the NIO test was successful or not available, the actual execution test is performed. To mitigate the virus scanner's false positive, we use an executable shell script per default now, which may be overriden by the new environment 'jogamp.gluegen.UseNativeExeFile=true' Tested on GNU/Linux with one temp folder having mount options 'noexec' and on Windows using Software Restriction Policies (SRP) disallowing one temp folder. Both temp folder were first in line via environment 'java.io.tmpdir'.
* | | | Bug 1219, Bug 1231: Avoid deflating test-exe on Windows using ↵Sven Gothel2019-03-241-51/+107
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | java.nio.file.Files.isExecutable(Path) Attempt to resolved virus scanner false positive detection on Windows while deflating the native code test-exe file in the temporary folder. As Julien Gouesse suggested, using Java 1.7's java.nio.file.Files.isExecutable(Path) _may_ resolve the issue, this has to be thorougly tested. This patch favors the nio's isExecutable file's ACL test over the more intrusive execution itself using a simple shell script file w/ set executable flag. Mind that previous tests allowed the shell script's execution, even if the temp folder did not allow execution of native code. We have to see how our testing results will be on this attempt.
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-28 23:35:17 +0000