On Thursday, 27 February 2025 at 13:33:55 UTC, John C. wrote:
>all code I have tested worked perfectly.
Of course, I had to rewrite all "RAYWHITE" to "raywhite", etc., but I'm happy to have working GUI library now!
February 27 Re: Noob ImportC questions | ||||
---|---|---|---|---|
| ||||
Posted in reply to John C. | On Thursday, 27 February 2025 at 13:33:55 UTC, John C. wrote: >all code I have tested worked perfectly. Of course, I had to rewrite all "RAYWHITE" to "raywhite", etc., but I'm happy to have working GUI library now! |
February 28 Re: Noob ImportC questions | ||||
---|---|---|---|---|
| ||||
Posted in reply to John C. | On Thursday, 27 February 2025 at 08:16:33 UTC, John C. wrote: >On Thursday, 27 February 2025 at 08:10:04 UTC, John C. wrote: >would removing some "hard to parse" constructs in header file help this situation? I tried to change
To more simpler definition which does not contain other previously defined macros (such as CLITERAL above)
But this change was not helpful, same error occured. Does this mean that ImportC cannot parse object literals? #define constants translated to enums are very limited in importC. Numbers and strings work. These color defines do not work. In raylib-d the color defines are all translated by hand. https://dlang.org/spec/importc.html#defines -Steve |