You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So, if you define NVG_NO_STB, you get no image functionality. You can't have your own version or get the symbols from a different library that also uses "stb_image.h".
It would be better, if the inclusion code would look like this:
This way you could avoid creating possibly duplicate symbols when building nanovg (by setting NVG_NO_STB_IMAGE_IMPLEMENTATION) and you can still avoid "stb_image.h" altogether with NVG_NO_STB as before.
The # include <stb_image.h> will look for an installed "stb_image.h" before considering the local one.
The text was updated successfully, but these errors were encountered:
LOL, I always wanted to create a bug report with tech debt in the title. Now here's why.
The "stb_image.h" version in nanovg is nine years old, and a couple of revisions older than the current version.
nanovg.c
uses it like this:So, if you define
NVG_NO_STB
, you get no image functionality. You can't have your own version or get the symbols from a different library that also uses "stb_image.h".It would be better, if the inclusion code would look like this:
This way you could avoid creating possibly duplicate symbols when building nanovg (by setting
NVG_NO_STB_IMAGE_IMPLEMENTATION
) and you can still avoid "stb_image.h" altogether withNVG_NO_STB
as before.The
# include <stb_image.h>
will look for an installed "stb_image.h" before considering the local one.The text was updated successfully, but these errors were encountered: