Files
imgui-java/bin
RobotandClaude Sonnet 4.6 34c40304f6
CI / Build Java (push) Has been cancelled
CI / Build Native (macos-latest - macos) (push) Has been cancelled
CI / Build Native (ubuntu-latest - linux) (push) Has been cancelled
CI / Build Native (ubuntu-latest - windows) (push) Has been cancelled
CI / Archive Natives (push) Has been cancelled
CI / Update Binaries (push) Has been cancelled
CI / Release (push) Has been cancelled
feat: add IMGUI_USE_WCHAR32 support, cross-compile natives, publish to mvn.mrlokop.dev
- Enable IMGUI_USE_WCHAR32 in imconfig.h (ImWchar = uint32_t)
- Extend ImFontGlyphRangesBuilder, ImFontConfig, ImFontAtlas for 32-bit codepoints
- Cross-compile natives for macOS universal, Linux x86_64 (glibc), Windows x86_64
- Publish as org.nnstd.imgui:...:1.90.0-wchar32+mrlokop2 to mvn.mrlokop.dev
- Add BUILDING.md with full rebuild and publish instructions

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-04-20 10:29:43 +03:00
..
2025-08-26 10:43:37 +00:00

Overview

The folder contains libraries used by the binding and the binding.sha1 checksum for the imgui-binding/src/main directory that the libraries are built upon. These libraries are utilized during the release process.

Specifying the Library Path

To specify the folder containing these files, provide the imgui.library.path (or java.library.path) VM option. For example:

-Dimgui.library.path=./folder/path

You can also use the java.library.path option in the same manner.

Changing the Library Name

By default, the binding expects the file name imgui-java64. You can change this by using the imgui.library.name VM option. For example:

-Dimgui.library.name=custom-lib-name.dll

Expected Library File Names

The expected library file names for different operating systems are:

OS Library
Windows imgui-java64.dll
Linux libimgui-java64.so
macOS libimgui-java64.dylib

Additional Information

  • All libraries include statically compiled FreeType.
  • The macOS version is a universal library and support x86_64 and arm64 architectures.

Continuous Integration

The hash sum in the binding.sha1 file is used in continuous integration (CI) to determine if there is a need to update the native binaries.