FreeBSD support is missing #421
Comments
|
You can find an attempt to port LWJGL (at least the parts Minecraft needs) to FreeBSD here. Official support won't be possible without a CI service (like Travis, AppVeyor, etc.) that supports FreeBSD. Afaik, such a service does not exist and cross-compilation from Linux is painful. If someone would like to host a solution (Jenkins or whatever) for us, please let me know. |
|
@Spasi we could be willing to provide that, what would you need there? |
|
Hey @nkfilis, A FreeBSD environment with the tools (GCC, git, CMake, etc.) and development headers necessary to build the projects listed here. You can check the
Ideally, the FreeBSD solution would work as simply as that. |
|
Just to let you know, I followed those instructions and managed to compile LWJGL3 and what was needed for Minecraft 1.13.2. It worked perfectly fine on my FreeBSD 11.2 64-bit system. |
|
If @nkfilis can't manage the CI setup for FreeBSD, I'll happily give it a go too. My FreeBSD server already runs 24/7 for other open source projects. |
|
I think this page could help a little bit about FreeBSD CI: https://wiki.freebsd.org/HostedCI |
FYI, Sourcehut supports FreeBSD and OpenBSD CI: https://man.sr.ht/builds.sr.ht/compatibility.md I haven't used it, but I know other OpenBSD developers who said it works quite well. |
|
would anyone be willing to layout what it would take to configure a CI system to support FreeBSD? I would be willing to learn and help with it, but my knowledge at the moment is rather low. |
|
Please check https://wiki.freebsd.org/HostedCI , there is some examples, and TravisCI also has experimental FreeBSD support now. |
|
LWJGL-CI has migrated to GitHub Actions. Anyone still interested in FreeBSD support, you may want to try https://github.com/marketplace/actions/freebsd-vm. Let me know if it works out please. |
|
I'm looking forward to seeing freebsd support added |
|
@Spasi Added a PR for FreeBSD Github Actions to LWJGL-CI |
|
CI aside, does Gephi's master branch build/work under FreeBSD? |
|
Started attempt at making a lwjgl3 port : freebsd (2021-05-14) Working port of lwjgl3 to FreeBSD (2021-07-09) |
|
@grahamperrin great work! If everything is ok, post a pull request to the upstream |
|
Not my work, I'm just linking |
|
@ivan-volnov that's the github of them who worked on LWJGL3 support for FreeBSD https://github.com/CRKatri/lwjgl3 |
|
Hello, what is the status of FreeBSD support? Has there been any progress? I have tried to compile using forks that claim they work but no luck. I assume either my environment is not setup correctly or the previous methods no longer work. |
|
Hey @VVD, You could probably avoid the libc copy. Drop the jemalloc native artifact/module and use I'll see if I can also make the |
|
@Spasi, thanks! |
|
Review with port: https://reviews.freebsd.org/D44263 |
|
|
|
But I need to create port LWJGL - "rules" for build it. For build automatically in clean and "closed" environment too (tool |
|
I would personally just leave jemalloc as is. There's no serious drawback to using an non-libc allocator, even if it's basically the same implementation. However, if you have no control of the application that's going to use your port AND you really want to use libc, then try adding |
why dependencies are in EXTRACT_DEPENDS? |
I can use software from ports or from base system only - we don't have jemalloc in ports, but have it in base embedded in libc.
lwjgl-jemalloc.jar build without errors, lwjgl-jemalloc-natives-freebsd.jar not build (as expected - use external lib instead packed in this jar).
Need files for |
I don't have other jamalloc - only in base system.
I need to build lwjgl correctly before using it.
Check plz patches: --- modules/lwjgl/jemalloc/src/generated/java/org/lwjgl/system/jemalloc/JEmalloc.java.orig 2023-12-18 14:22:59 UTC
+++ modules/lwjgl/jemalloc/src/generated/java/org/lwjgl/system/jemalloc/JEmalloc.java
@@ -40,27 +40,27 @@ public class JEmalloc {
/** Function address. */
public static final long
- malloc_message = apiGetFunctionAddress(JEMALLOC, "je_malloc_message"),
- malloc = apiGetFunctionAddress(JEMALLOC, "je_malloc"),
- calloc = apiGetFunctionAddress(JEMALLOC, "je_calloc"),
- posix_memalign = apiGetFunctionAddress(JEMALLOC, "je_posix_memalign"),
- aligned_alloc = apiGetFunctionAddress(JEMALLOC, "je_aligned_alloc"),
- realloc = apiGetFunctionAddress(JEMALLOC, "je_realloc"),
- free = apiGetFunctionAddress(JEMALLOC, "je_free"),
- free_sized = apiGetFunctionAddress(JEMALLOC, "je_free_sized"),
- free_aligned_sized = apiGetFunctionAddress(JEMALLOC, "je_free_aligned_sized"),
- mallocx = apiGetFunctionAddress(JEMALLOC, "je_mallocx"),
- rallocx = apiGetFunctionAddress(JEMALLOC, "je_rallocx"),
- xallocx = apiGetFunctionAddress(JEMALLOC, "je_xallocx"),
- sallocx = apiGetFunctionAddress(JEMALLOC, "je_sallocx"),
- dallocx = apiGetFunctionAddress(JEMALLOC, "je_dallocx"),
- sdallocx = apiGetFunctionAddress(JEMALLOC, "je_sdallocx"),
- nallocx = apiGetFunctionAddress(JEMALLOC, "je_nallocx"),
- mallctl = apiGetFunctionAddress(JEMALLOC, "je_mallctl"),
- mallctlnametomib = apiGetFunctionAddress(JEMALLOC, "je_mallctlnametomib"),
- mallctlbymib = apiGetFunctionAddress(JEMALLOC, "je_mallctlbymib"),
- malloc_stats_print = apiGetFunctionAddress(JEMALLOC, "je_malloc_stats_print"),
- malloc_usable_size = apiGetFunctionAddress(JEMALLOC, "je_malloc_usable_size");
+ malloc_message = apiGetFunctionAddress(JEMALLOC, functionNamePrefix + "malloc_message"),
+ malloc = apiGetFunctionAddress(JEMALLOC, functionNamePrefix + "malloc"),
+ calloc = apiGetFunctionAddress(JEMALLOC, functionNamePrefix + "calloc"),
+ posix_memalign = apiGetFunctionAddress(JEMALLOC, functionNamePrefix + "posix_memalign"),
+ aligned_alloc = apiGetFunctionAddress(JEMALLOC, functionNamePrefix + "aligned_alloc"),
+ realloc = apiGetFunctionAddress(JEMALLOC, functionNamePrefix + "realloc"),
+ free = apiGetFunctionAddress(JEMALLOC, functionNamePrefix + "free"),
+ free_sized = apiGetFunctionAddress(JEMALLOC, functionNamePrefix + "free_sized"),
+ free_aligned_sized = apiGetFunctionAddress(JEMALLOC, functionNamePrefix + "free_aligned_sized"),
+ mallocx = apiGetFunctionAddress(JEMALLOC, functionNamePrefix + "mallocx"),
+ rallocx = apiGetFunctionAddress(JEMALLOC, functionNamePrefix + "rallocx"),
+ xallocx = apiGetFunctionAddress(JEMALLOC, functionNamePrefix + "xallocx"),
+ sallocx = apiGetFunctionAddress(JEMALLOC, functionNamePrefix + "sallocx"),
+ dallocx = apiGetFunctionAddress(JEMALLOC, functionNamePrefix + "dallocx"),
+ sdallocx = apiGetFunctionAddress(JEMALLOC, functionNamePrefix + "sdallocx"),
+ nallocx = apiGetFunctionAddress(JEMALLOC, functionNamePrefix + "nallocx"),
+ mallctl = apiGetFunctionAddress(JEMALLOC, functionNamePrefix + "mallctl"),
+ mallctlnametomib = apiGetFunctionAddress(JEMALLOC, functionNamePrefix + "mallctlnametomib"),
+ mallctlbymib = apiGetFunctionAddress(JEMALLOC, functionNamePrefix + "mallctlbymib"),
+ malloc_stats_print = apiGetFunctionAddress(JEMALLOC, functionNamePrefix + "malloc_stats_print"),
+ malloc_usable_size = apiGetFunctionAddress(JEMALLOC, functionNamePrefix + "malloc_usable_size");
}
@@ -105,11 +105,16 @@ public class JEmalloc {
/** Use as arena index in "stats.arenas.<i>.*" mallctl interfaces to select destroyed arenas. */
public static final int MALLCTL_ARENAS_DESTROYED = 0x1001;
+ private static String functionNamePrefix = "je_";
+
static {
+ if (Platform.get() == Platform.FREEBSD) {
+ functionNamePrefix = "";
+ }
// Force jemalloc to initialize before anyone else uses it.
// This avoids a dangerous race when the first jemalloc functions are called concurrently.
if (Platform.get() == Platform.WINDOWS) {
- invokePV(invokePP(8L, apiGetFunctionAddress(JEMALLOC, "je_malloc")), apiGetFunctionAddress(JEMALLOC, "je_free"));
+ invokePV(invokePP(8L, apiGetFunctionAddress(JEMALLOC, functionNamePrefix + "malloc")), apiGetFunctionAddress(JEMALLOC, functionNamePrefix + "free"));
}
}--- modules/lwjgl/core/src/main/java/org/lwjgl/system/MemoryManage.java.orig 2023-12-18 14:22:59 UTC
+++ modules/lwjgl/core/src/main/java/org/lwjgl/system/MemoryManage.java
@@ -34,6 +34,9 @@ final class MemoryManage {
String className;
if (allocator == null || "jemalloc".equals(allocator)) {
className = "org.lwjgl.system.jemalloc.JEmallocAllocator";
+ if (Platform.get() == Platform.FREEBSD) {
+ Configuration.JEMALLOC_LIBRARY_NAME.set("libc.so.7");
+ }
} else if ("rpmalloc".equals(allocator)) {
className = "org.lwjgl.system.rpmalloc.RPmallocAllocator";
} else {
Also why do you link statically with libffi? Why not dynamically as with other libraries? Thanks! |
|
Need patches for libraries with other names only: --- modules/lwjgl/shaderc/src/generated/java/org/lwjgl/util/shaderc/Shaderc.java.orig 2023-12-18 14:22:59 UTC
+++ modules/lwjgl/shaderc/src/generated/java/org/lwjgl/util/shaderc/Shaderc.java
@@ -20,7 +20,7 @@ import static org.lwjgl.system.MemoryUtil.*;
/** Native bindings to the libshaderc C API of the <a href="https://github.com/google/shaderc/">shaderc</a> library. */
public class Shaderc {
- private static final SharedLibrary SHADERC = Library.loadNative(Shaderc.class, "org.lwjgl.shaderc", Configuration.SHADERC_LIBRARY_NAME.get(Platform.mapLibraryNameBundled("shaderc")), true);
+ private static final SharedLibrary SHADERC = Library.loadNative(Shaderc.class, "org.lwjgl.shaderc", Configuration.SHADERC_LIBRARY_NAME.get(Platform.mapLibraryNameBundled(Platform.get() == Platform.FREEBSD ? "shaderc_shared" : "shaderc")), true);
/** Contains the function pointers loaded from the shaderc {@link SharedLibrary}. */
public static final class Functions {--- modules/lwjgl/spvc/src/generated/java/org/lwjgl/util/spvc/Spvc.java.orig 2023-12-18 14:22:59 UTC
+++ modules/lwjgl/spvc/src/generated/java/org/lwjgl/util/spvc/Spvc.java
@@ -40,7 +40,7 @@ import static org.lwjgl.system.MemoryUtil.*;
*/
public class Spvc {
- private static final SharedLibrary SPVC = Library.loadNative(Spvc.class, "org.lwjgl.spvc", Configuration.SPVC_LIBRARY_NAME.get(Platform.mapLibraryNameBundled("spirv-cross")), true);
+ private static final SharedLibrary SPVC = Library.loadNative(Spvc.class, "org.lwjgl.spvc", Configuration.SPVC_LIBRARY_NAME.get(Platform.mapLibraryNameBundled(Platform.get() == Platform.FREEBSD ? "spirv-cross-c-shared" : "spirv-cross")), true);
/** Contains the function pointers loaded from the spvc {@link SharedLibrary}. */
public static final class Functions { |
|
Hey @VVD, I don't understand what you're trying to do. The whole point of this issue was to add official support for FreeBSD to LWJGL, which is what happened. Afaict, FreeBSD ports are useful for a) building software from source and b) patching software that does not support or has issues on FreeBSD, so that it works on FreeBSD. There should be no need to patch anything in LWJGL, it already supports FreeBSD. However, if your goal is to build LWJGL from source, then that's no simple undertaking at all. The LWJGL core is simple enough, but LWJGL is nothing without the bindings. Each binding is a whole project by itself, written in C and/or C++, with a variety of build systems and dependencies of its own. This is what we have LWJGL-CI for and keeping it healthy is a major part of my work as LWJGL maintainer. It's difficult and time-consuming. So, you can't really claim that your LWJGL port is building from source, without also building all these dependencies. Which is something that I would find pointless and wouldn't wish for anyone to have to do. LWJGL already provides prebuilt binaries for all its dependencies, in sync with every release/build of the LWJGL core. If on the other hand, your goal is to make an LWJGL port that does not use its own dependencies, but uses natives from other FreeBSD ports instead... I don't know, maybe I see some value there, but I also find it weird too. You're opening yourself to a world of pain with versioning issues. LWJGL bindings are developed in sync with the corresponding native libraries, i.e. updated always together, which is a guarantee that leaves little room for backward compatibility. Native libraries often break API and LWJGL breaks it at the same time. Or maybe I'm busy irl for a while and can't update LWJGL, so other ports are more up-to-date and LWJGL is behind. In any case, LWJGL has been designed to work with its own binaries. I mean, that's the whole point of LWJGL, saving Java developers from having to build native code. Anyway, statements like:
Make little sense to me, exactly because LWJGL comes with its own jemalloc build. I don't see how you can claim you don't have other jemalloc, a FreeBSD build comes out-of-the-box with LWJGL.
Because libffi is a critical part of LWJGL core (used to implement native-to-Java callbacks) and wanted the core to be a single native binary. It's also an implementation detail. At some point LWJGL switched to dyncall, now it's back to libffi. Note that any API/binding under the |
A port is a build recipe that produces a package. For user to be able to do
Yes, it is a common problem for all the open source software and meta-build systems like FreeBSD Ports, Gentoo Portage, etc.
Now, this is arguable. From my experience as downstream packager I'd say that most of the software tries to use dependencies from the system. Build systems like Autotools, Meson and CMake are built around this idea - they all provide a way to look for some other library or package and link your project to it. A bit less common scenario is when the project gives user a choice where to look for dependencies - either system or bundled ones. This is achieved with Finally, on the rarest occasions, the project just declares that it is not intended to be built with external dependencies and just bundle everything. From what I gather, lwjgl follows the "bundle-everything" path. In this case there is indeed no sense in fighting it on the ports side.
Yes, versioning issues is a thing, but so far the world keeps up with it. We have more than 30k ports in our tree and only a miniscule of them are bundling their stuff. This approach also has its own benefits:
Of course I don't request lwjgl to change the way it handles deps, just sharing my experience from the other side of borderline. |
|
Hey @arrowd, Thanks for the interesting input, it honestly makes a lot of sense for native software. However, doing
is not something a Java developer would want to do. Java dependencies are managed via Maven/Gradle, there's no point in installing a Java library outside the local Maven repo. However, a software product that uses LWJGL may want to be installable that way. Which includes NOT using some of LWJGL's prebuilt binaries and overriding them with other ports. I.e. this is something that the product developer should decide and control, it should not be enforced by an LWJGL port. Also, note that incompatibilities may also arise in the opposite direction. There are some LWJGL dependencies with patches that are Java/LWJGL-specific and will never be included in the upstream project. For example, GLFW's async implementation for macOS. |
Regular users want to use |
|
Added --- config/freebsd/build.xml.orig 2023-12-18 14:22:59 UTC
+++ config/freebsd/build.xml
@@ -159,16 +159,18 @@
<include name="${module.lwjgl}/jawt/src/generated/c/*.c" if:true="${binding.jawt}"/>
</fileset>
</source>
- <beforeLink>
+ <beforeLink unless:true="${use.libffi.so}">
<parallel threadsPerProcessor="2" failonany="true" unless:set="lib-dependencies-uptodate">
<update-dependency module="core" artifact="core/libffi.a"/>
</parallel>
</beforeLink>
<link>
- <fileset dir="${lib.native}/org/lwjgl">
+ <fileset dir="${lib.native}/org/lwjgl" unless:true="${use.libffi.so}">
<include name="libffi.a"/>
</fileset>
<arg value="-ldl"/>
+ <arg value="-lffi" if:true="${use.libffi.so}"/>
+ <arg value="-L${libffi.path}" if:set="libffi.path"/>
</link>
</build>
Look like it's last patch for now. :-D |
|
Time to test run! I got error during run:
Sources of the File With this Do you use this set of patches: glfw/glfw#2130? More logs: |
|
Build |
|
It use llvmpipe (software rendering) if file
@Spasi, did you added this option? Patch didn't help:
didn't help too. Only |
|
IIRC, this problem is specific to NVIDIA proprietary driver, although it arranges a |
Don't think |
|
Found other bug (maybe offtopic here): can't set multiple paths in |
|
Hey all, What's the ABI compatibility story on FreeBSD? Current binaries are built on FreeBSD 13.2 with Clang 14. 13.3 comes with Clang 17 and there's also 14.0 (released earlier than 13.3?) with Clang 16. I'm guessing that a build on 13.3 will work on 14.0, but will it also be compatible with 13.0-13.2? |
Yes, with
It can work, but no warranty.
14.1 release in 3 weeks: https://www.freebsd.org/releases/14.1R/schedule/ |
Yes, just like Linux kernel. About binary compatibility, current FreeBSD config is compatible with binaries from FreeBSD 4 (I think it needs to rebuild or pack libraries into package to make old binaries workable) |
All necessary system libraries are in ports: |
Environment
3.2unknownopenjdk 8FreeBSD 11.1coreDescription
The Minecraft 1.12.x game worked just fine under FreeBSD with lwjgl 2.9.x but then when Minecraft 1.13.x came out, they moved up to lwjgl 3.x. Currently the lwjgl 3.x doesn't have support for FreeBSD.
Seeing as v2.9.x did, is there any changes somebody here could try and add v3.x support for FreeBSD, so we can get the wonderful Minecraft game working again. :-)
Somebody in the FreeBSD web forums have tried to get lwjgl 3.2 to build under FreeBSD 11.1, and here is how far they can. Hopefully this is a good start for anybody with more knowledge, to add the missing piece, or understand the compilation errors. I don't.
https://forums.freebsd.org/threads/minecraft-11-2-failed-to-locate-library-liblwjgl-so.66923/#post-402189
Here is a copy of that forum message:
With some help on #freebsd freenode, I am attempting to compile lwjgl 3.2 on FreeBSD 11.1-STABLE. I have modified lwjgl's build.xml file to compile using gcc8.
https://github.com/LWJGL/lwjgl3/blob/2359eb7b5a9e7e629beae95d3cdab8e997c59039/config/linux/build.xml
And here is my modified build.xml, to work with gcc8:
https://paste.pound-python.org/show/Akuv2tbz32OTgSyqZKfJ/
Using the build instruction found here:
https://www.lwjgl.org/guide#build-instructions
I am getting the following output:
https://paste.pound-python.org/show/8GO6dhwjNrQFu1ddtx2a/
The text was updated successfully, but these errors were encountered: