Messages

1

General discussions / Re: Android SDK 34 Font/Text issue

« on: June 09, 2025, 08:15:50 am »

Hi again!
I successfully got OpenAL working (at least) on a virtual x86_64 device by building this branch of OpenAL-Soft:
https://github.com/AerialX/openal-soft-android.

Since this branch is quite old, is there anything I should be concerned about?

2

General discussions / Re: Android SDK 34 Font/Text issue

« on: June 08, 2025, 09:55:50 am »

Or maybe if you can provide me the instructions how you have built the actual prebuilt libopenal.so?

Thanks!

3

General discussions / Re: Android SDK 34 Font/Text issue

« on: June 08, 2025, 09:33:26 am »

I build with Ninja like this, can you say am I doing something wrong?

cmake .. -G Ninja ^
  -DCMAKE_TOOLCHAIN_FILE="../26.3.11579264/build/cmake/android.toolchain.cmake" ^
  -DANDROID_ABI=x86_64 ^
  -DANDROID_PLATFORM=android-21 ^
  -DCMAKE_BUILD_TYPE=Release ^
  -DBUILD_SHARED_LIBS=ON ^
  -DALSOFT_BACKEND_OPENSL=ON ^
  -DALSOFT_BACKEND_DUMMY=ON ^
  -DALSOFT_BACKEND_WASAPI=OFF ^
  -DALSOFT_BACKEND_PULSEAUDIO=OFF ^
  -DALSOFT_BACKEND_OSS=OFF ^
  -DALSOFT_BACKEND_SOLARIS=OFF ^
  -DALSOFT_BACKEND_SNDIO=OFF ^
  -DALSOFT_BACKEND_PORTAUDIO=OFF ^
  -DALSOFT_BACKEND_WAVE=OFF ^
  -DALSOFT_BACKEND_ALSA=OFF ^
  -DALSOFT_EXAMPLES=OFF ^
  -DALSOFT_UTILS=OFF ^
  -DALSOFT_NO_CONFIG_UTIL=ON ^
  -DALSOFT_TESTS=OFF ^
  -DALSOFT_CONFIG=OFF ^
  -DALSOFT_HRTF_DEFS=OFF ^
  -DALSOFT_EMBED_HRTF_DATA=OFF ^
  -DALSOFT_REQUIRE_OPENSL=ON ^
  -DALSOFT_ENABLE_ALSOFT_LOGGING=OFF ^
  -DCMAKE_SHARED_LINKER_FLAGS="-Wl,--strip-all -Wl,--gc-sections -Wl,-z,max-page-size=16384" ^
  -DCMAKE_C_FLAGS_RELEASE="-ffunction-sections -fdata-sections -Os" ^
  -DCMAKE_CXX_FLAGS_RELEASE="-ffunction-sections -fdata-sections -Os"

I'm using the latest openal-soft source.
Thanks in advance.

4

General discussions / Re: Android SDK 34 Font/Text issue

« on: June 07, 2025, 10:48:55 pm »

Hi,

I have one more issue: libopenal.so also had to be built with the flag -DCMAKE_EXE_LINKER_FLAGS="-Wl,-z,max-page-size=16384" - However, after applying this, my app no longer plays any sound, and Logcat is flooded with errors like this (with varying source IDs):

[ALSOFT] (WW) Error generated on context 0xb400007246bbbe00, code 0xa001, "Invalid source ID 4289313793".

My question is: What is the correct way to build OpenAL-Soft to ensure compatibility with SFML?

5

General discussions / Re: Android SDK 34 Font/Text issue

« on: June 07, 2025, 07:07:11 pm »

Thank you, Texus!

I managed to get this working by copying libc++_shared.so from NDK 28.
I know that upgrading to SFML 3 is important, but since my app is already quite complex and built on SFML 2.6, I’ll need some time to properly plan and implement the migration. I appreciate any advice or insights on making the transition as smooth as possible! The app has already reached the testing phase and is actively being evaluated.  😊

6

General discussions / Re: Android SDK 34 Font/Text issue

« on: June 07, 2025, 06:04:21 pm »

Hi texus.

I’m currently encountering an issue on Android version 15, which appears to require support for 16 KB page sizes (https://developer.android.com/guide/practices/page-sizes). I have compiled the SFML libraries using the flag -DCMAKE_EXE_LINKER_FLAGS="-Wl,-z,max-page-size=16384", but I am still seeing errors in Android Studio as follows:

D  Load /data/app/~~<random>/com.example.app.debug-<random>/lib/x86_64/libsfml-activity-d.so using ns clns-7 from class loader (caller=<unknown>): ok
2025-06-07 17:18:46.087 24715-24715 libc                    com.example.app.debug               A  Fatal signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0x7422de9a0cc0 in tid 24715 (com.example.app.debug), pid 24715 (com.example.app.debug)
2025-06-07 17:18:46.390 24736-24736 DEBUG                   crash_dump64                         A  Cmdline: com.example.app.debug
2025-06-07 17:18:46.391 24736-24736 DEBUG                   crash_dump64                         A  pid: 24715, tid: 24715, name: com.example.app.debug  >>> com.example.app.debug <<<
2025-06-07 17:18:46.397 24736-24736 DEBUG                   crash_dump64                         A        #07 pc 0000000000005cf5  /data/app/~~<random>/com.example.app.debug-<random>/lib/x86_64/libsfml-activity-d.so (loadLibrary(char const*, _JNIEnv*, _jobject*&)+453)
2025-06-07 17:18:46.397 24736-24736 DEBUG                   crash_dump64                         A        #08 pc 00000000000061ce  /data/app/~~<random>/com.example.app.debug-<random>/lib/x86_64/libsfml-activity-d.so (ANativeActivity_onCreate+558)

Would you happen to know if there is something specific I should consider or adjust to resolve this issue? I'm still on SFML 2.6.2

7

General discussions / Re: Android SDK 34 Font/Text issue

« on: June 04, 2025, 04:36:19 pm »

Thanks texus!

I'm going to migrate to SFML3 soon.

8

General discussions / Re: Android SDK 34 Font/Text issue

« on: June 02, 2025, 01:00:12 pm »

It can be reproduced with a minimal code, so the code below isn't working. But if you comment out window.draw(text), it works.

#include <SFML/Graphics.hpp>

int main()
{
    sf::RenderWindow window(sf::VideoMode(800, 600), "Minimal SFML Example");
   
    sf::Font font;
    if (!font.loadFromFile("UbuntuMono-R.ttf")) 
        return -1;

    sf::Text text("Hello, SFML!", font, 30);     
    text.setFillColor(sf::Color::White);
    text.setPosition(50.f, 50.f);
   
    sf::RectangleShape rect(sf::Vector2f(200.f, 100.f));
    rect.setFillColor(sf::Color::Blue);
    rect.setOutlineColor(sf::Color::Red);
    rect.setOutlineThickness(3.f);
    rect.setPosition(50.f, 120.f);
   
    while (window.isOpen())
    {
        sf::Event event;
        while (window.pollEvent(event))
            if (event.type == sf::Event::Closed)
                window.close();

        window.clear(sf::Color::Black);
        window.draw(text);
        window.draw(rect);
        window.display();
    }
}

9

General discussions / Re: Android SDK 34 Font/Text issue

« on: June 02, 2025, 10:53:15 am »

Hi, not much information but this (with the rest I posted earlier).


_{libc                    com.TEST.App.debug                   A  Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0 in tid 27697 (.TEST.App.debug), pid 27674 (.TEST.App.debug)}


AI:
"Your crash log indicates a segmentation fault (SIGSEGV) with SEGV_MAPERR, meaning your app tried to access an invalid memory location—likely a null pointer dereference. The issue seems to originate from sf::Texture::copyToImage() and sf::Texture::update(), which suggests a problem with texture handling in SFML."

10

General discussions / Re: Android SDK 34 Font/Text issue

« on: June 02, 2025, 09:55:25 am »

Hi,

The issue appears to be related to OpenGL ES 1.1. To resolve it, I compiled Zombiechannel's branch of SFML (https://github.com/Zombieschannel/SFML/tree/SFML-2.6.x-GLES2) using OpenGL ES 2.0, and that successfully fixed the problem.

Since this may affect other users as well, I would kindly suggest considering updates to the master branch to ensure broader compatibility with future Android versions.

Thank you for your continued work on SFML!

11

General discussions / Re: SFML 3, iOS toolchain?

« on: May 31, 2025, 07:11:11 pm »

Hi, sorry for the delayed response — I’ve postponed building the iOS app for now. I’ll revisit this later and get back to you then.

12

General discussions / Android SDK 34 Font/Text issue

« on: May 31, 2025, 06:53:19 pm »

Hi, I have a fully working app built with SFML 2.6 for Android (SDK 33 and below).

I'm preparing for release, but I noticed that on Android SDK 34, SFML doesn't behave as expected — specifically, the app crashes when trying to render (draw) text using sf::Text.

Before I start migrating to SFML 3.x, I'd like to ask:

Has this issue been fixed in SFML 3.x already?

Or is there any known workaround for SFML 2.6 that would allow me to keep using it for now?

Thanks in advance!

^{/lib/x86_64/libsfml-graphics-d.so (sf::Texture::copyToImage() const+626) (BuildId: 143156b11f1e7688c99cca42702019eea822d896)
/lib/x86_64/libsfml-graphics-d.so (sf::Texture::update(sf::Texture const&, unsigned int, unsigned int)+248) (BuildId: 143156b11f1e7688c99cca42702019eea822d896)
/lib/x86_64/libsfml-graphics-d.so (sf::Texture::update(sf::Texture const&)+32) (BuildId: 143156b11f1e7688c99cca42702019eea822d896)
/lib/x86_64/libsfml-graphics-d.so (sf::Texture::Texture(sf::Texture const&)+287) (BuildId: 143156b11f1e7688c99cca42702019eea822d896)
/lib/x86_64/libsfml-graphics-d.so (sf::Font::Page::Page(sf::Font::Page&&)+60) (BuildId: 143156b11f1e7688c99cca42702019eea822d896)
/lib/x86_64/libsfml-graphics-d.so (sf::Font::loadPage(unsigned int) const+180) (BuildId: 143156b11f1e7688c99cca42702019eea822d896)
/lib/x86_64/libsfml-graphics-d.so (sf::Font::getTexture(unsigned int) const+26) (BuildId: 143156b11f1e7688c99cca42702019eea822d896)
/lib/x86_64/libsfml-graphics-d.so (sf::Text::ensureGeometryUpdate() const+156) (BuildId: 143156b11f1e7688c99cca42702019eea822d896)
/lib/x86_64/libsfml-graphics-d.so (sf::Text::draw(sf::RenderTarget&, sf::RenderStates) const+54) (BuildId: 143156b11f1e7688c99cca42702019eea822d896)
/lib/x86_64/libsfml-graphics-d.so (sf::RenderTarget::draw(sf::Drawable const&, sf::RenderStates const&)+175) (BuildId: 143156b11f1e7688c99cca42702019eea822d896)
/lib/x86_64/libsfml-system-d.so (sf::Thread::run()+25) (BuildId: 3528b2aa2c2bb0e8cec9e9b4d11fcae90e2d20f6)} 

13

General discussions / Re: SFML 3, iOS toolchain?

« on: May 02, 2025, 10:20:56 pm »

Thanks, this helped a lot to move on!

When finally trying to build a test app in Xcode 18.4 I got an error: Implicit instantiation of undefined template 'std::char_traits<unsigned int>'

ChatGPT gives an answer, but I don't know if this is the real case here:

That error —
“Implicit instantiation of undefined template ‘std::char_traits<unsigned int>’” —
means some code is trying to use std::basic_string<unsigned int>, which is not allowed because std::char_traits<unsigned int> is not defined by the standard library (libc++ doesn't support it).

This issue has come up in SFML, especially when trying to build for iOS using libc++, which is more strict than libstdc++.

14

General discussions / SFML 3, iOS toolchain?

« on: May 02, 2025, 04:56:54 pm »

Hi,

there is no iOS.toolchain.cmake file anymore available with source code.

Is there one available somewhere?



 

15

General discussions / Build sfeMovie against new version of ffmpeg?

« on: September 19, 2023, 10:06:26 am »

Hi,

is it possible to build sfeMovie against new version (or newer version) of ffmpeg than 2.8?
If so what it takes to get job done? I have succeed to build the sfeMovie with Visual Studio so far (with ffmpeg 2.8 ), but there is an issue to use sfeMovie on Windows Server 2019 (crash). On Win 10 works fine. Maybe the old version of the ffmpeg is the issue?