RobLoach / RobLoach/raylib-cpp

Can't find standard headers while working for Android

Open
#359 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
960
Forks
120
Avg merge
10m
Merged PRs (30d)
1

Description

Hi, I'm currently trying to develop a Raylib game using the raylib-cpp wrapper; following this guide and modifying a bit the launch script (that I will attach), I was able to make Raylib run on Android.
The problem is that when I start to use raylib-cpp (after following the Getting Started section obviously), I get this error message:

In file included from src/main.cpp:2:
In file included from src/engine/engine.hpp:4:
In file included fro

[build_android.txt](https://github.com/user-attachments/files/20458700/build_android.txt)

[build_android.txt](https://github.com/user-attachments/files/20458710/build_android.txt)

m raylib-cpp/include/raylib-cpp.hpp:34:
In file included from raylib-cpp/include/./AudioDevice.hpp:4:
raylib-cpp/include/././RaylibException.hpp:4:10: fatal error: 'stdexcept' file not found
    4 | #include <stdexcept>
      |          ^~~~~~~~~~~
1 error generated.

I think every there's a linking problem regarding raylib-cpp and Android projects, because when I try using a cmake to make the project run on desktop everything works perfectly. How can I fix this?

Steps to replicate:

  1. Follow the guide linked to setup Android developing Raylib project
  2. Clone raylib-cpp into the project directory
  3. Run the building script

build_android.txt

EDIT: I tried commenting the #include <stdexcept> line in the RaylibException.hpp file, and I got the same error with the #include <string>. I also commented this last include and, again, got the same error with cmath on a different file. It seems raylib-cpp can't find the standard libraries at all.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the attached build_android.txt script alongside the linked Android setup guide, then reproduce the build and inspect the include chain through raylib-cpp/include/./RaylibException.hpp. Trace why standard headers such as stdexcept, cstring, and cmath are unavailable; done means the Android build completes with raylib-cpp without those header errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, cpp
Domain
build-system, mobile-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.