Closed gesellix closed 5 years ago
This one might even be related to #45
Yes, I've improved the loading mechanism in 2.2.0.
Moreover, most native libraries are now cross-compiled on macOS using clang (exceptions: macOS, which uses native clang, and Windows 10, which uses mingw-w64)
Please don't see this one as an issue, but more of a question.
In https://github.com/gesellix/gradle-testkit-junixsocket-issue I tried to find a minimal way of demonstrating an issue when using junixsocket 2.1.2. I suspected something along the way how Gradle Testkit performs functional tests. Using your recently published junixsocket 2.2.0 the issue had been fixed.
I would now like to find out what exactly changed in junixsocket to make the issue disappear, because I would like to understand whether there is still a risk of something being broken but unnoticed.
If you'd like to reproduce the issue, you can clone the linked repository and perform
./gradlew check --info --stacktrace
. The build should fail with the following stacktrace:If you checkout the
junixsocket-2.2.0
branch and repeat./gradlew check --info --stacktrace
, the build should succeed. The only difference is the dependency version changing from 2.1.2 to 2.2.0.Do you have an idea whether something regarding the library loading mechanism has been changed? I've had a look into the recent commits, but don't really understand what exactly the issue was with 2.1.2.