-
Notifications
You must be signed in to change notification settings - Fork 278
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
can't make it use ImWchar32 #232
Comments
You must edit generator.sh to add -DIMGUI_USE_WCHAR32 |
hmm, I see. Maybe there is a way to include command-line arguments in this script by default? |
maybe a quick edit like this? diff --git a/generator/generator.sh b/generator/generator.sh
index 92d7ae4..e2840c5 100755
--- a/generator/generator.sh
+++ b/generator/generator.sh
@@ -22,4 +22,4 @@ then
suffix='.exe'
fi
-luajit$suffix ./generator.lua gcc "internal noimstrv" glfw opengl3 opengl2 sdl2
+luajit$suffix ./generator.lua gcc "internal noimstrv" glfw opengl3 opengl2 sdl2 "$@" EDIT I've created PR #233 |
I prefer not because it would only be useful for CFLAGS but not other options that must be edited in generator.sh |
hmm, I see what... maybe introduce some flags-parser logic in generator.sh? |
the best would be for you to have your own generator.bat (sh) outside cimgui repo edited as:
That way you are able to update cimgui but keeping your generator options |
I've considered it, however, note that the current generator.sh already contains more stuff than just luajit call... |
Yes, but upstream cimgui has some predefined options hardcoded in generator.bat. The only way to have your own options is having your own generator.sh outside cimgui changing this line:
|
I see, I'm just wondering why not add |
Perhaps update your PR so that I can understand how would it be? |
@sonoro1234 take a look now |
Hi
I generated binding with
./generate.sh -DIMGUI_USE_WHCAR32
(like readme says)but it still seems to use ImWchar16...
what am I doing wrong? Or probably I missunderstood how USE_IMGUI_WHCAR32 works?
The text was updated successfully, but these errors were encountered: