Can't find standard headers while working for Android
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 45/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Tranquilo
- Stack tecnológico
- android, cpp
- Área
- build-system, mobile-dev
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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:
- Follow the guide linked to setup Android developing Raylib project
- Clone raylib-cpp into the project directory
- Run the building script
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.
- Lenguaje dominante
- C++
- Estrellas
- 960
- Forks
- 120
- Merge medio
- 10 min
- PR fusionados (30 d)
- 1
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de RobLoach/raylib-cpp
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
RobLoach/raylib-cpp#425 ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
RobLoach/raylib-cpp#427 ·
-
Code gen Abierto
Dificultad 5/5 Más de una semana Aptitud para principiantes 30/100
RobLoach/raylib-cpp#415 · 1 comentario ·
-
Dificultad 3/5 1-2 días Aptitud para principiantes 45/100
RobLoach/raylib-cpp#370 · 1 comentario ·
-
SDF Font Support Abierto
Dificultad 3/5 1-2 días Aptitud para principiantes 55/100
RobLoach/raylib-cpp#366 · 3 comentarios ·
Todos los issues de RobLoach/raylib-cpp
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
duckdb/duckdb-wasm#2258 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
objectionary/eo-graphs#75 ·
-
Coarray integration tests carry no LABELS, so run_tests.py silently skips them under every backend Abiertocoarray
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
FISCO-BCOS/FISCO-BCOS#5642 ·