Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to build bgfx for iOS Simulator x86_64 arch #3239

Closed
npamidisf opened this issue Jan 6, 2024 · 4 comments
Closed

Unable to build bgfx for iOS Simulator x86_64 arch #3239

npamidisf opened this issue Jan 6, 2024 · 4 comments

Comments

@npamidisf
Copy link

npamidisf commented Jan 6, 2024

Describe the bug
A clear and concise description of what the bug is.

I've been trying to build bgfx, bimg and bx for iOS and followed the steps recommended in the build-instructions page. While, it does build make ios-arm and make ios-simulator-arm64, but I'm seeing the below error when i run make ios-simulator.

In file included from ../../../../bimg/src/image_decode.cpp:71: ../../../../bimg/3rdparty/stb/stb_image.h:967:1: fatal error: thread-local storage is not supported for the current target STBI_THREAD_LOCAL ^ ../../../../bimg/3rdparty/stb/stb_image.h:624:39: note: expanded from macro 'STBI_THREAD_LOCAL' #define STBI_THREAD_LOCAL thread_local

To Reproduce
Steps to reproduce the behavior:

  1. Download bgfx, bimg, bx
  2. cd into bgfx
  3. Run make ios-simulator
  4. See error

Expected behavior
It should generate static libraries of bgfx, bimg and bx for x86_64 arch

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
I have XCode 15 running on my machine..

@npamidisf
Copy link
Author

Seems others are having the same issue as well #2399

@bkaradzic
Copy link
Owner

I removed support for iOS simulator:
8cb7445

@npamidisf
Copy link
Author

@bkaradzic Don't we need the x86_64(intel macs) and arm64(m1 macs) simulator arch builds to be able to build and develop using the library?

@bkaradzic
Copy link
Owner

You submitted issue it doesn't work. I didn't check that recently, nor I have time to deal with it. So this wouldn't be fixed anytime soon by me, and I just removed it to not cause confusion. Once I have time to deal with simulator I might reintroduce it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants