Closed YuzukiTsuru closed 3 years ago
Thanks for reporting this. The continuous integration build it on windows and there was no problem: https://travis-ci.com/github/ArthurSonzogni/FTXUI/jobs/406888815
Are you sure this isn't caused by your usage? Are you just compiling the FTXUI library, or are you compiling your project?
I will confirm it and build example
This is caused by a conflict with a macro defined in a Windows header: https://docs.microsoft.com/en-us/windows/win32/api/wingdi/nf-wingdi-rgb. I ran into the same issue by including an ASIO header before including FTXUI headers.
I would open a PR fixing it, but the options are
#undef RGB
which could break user code if adding FTXUI includes.Rgb
. Breaking change, but maybe the nicer option?If you let me know what you think, I can open a PR with a fix. :)
Thanks @robinlinden!
I think this window header you mentioned shouldn't have defined such a macro with this very common name. I believe option 1 might be worth it to be tried?
A windows header is breaking us, we break it in return? ;-)
Sounds good, will open a PR in a bit! :) If users really want the macro, they can always move the Windows header to after the line where ftxui's headers are included and everything will work.