Closed spartanPAGE closed 8 years ago
I don't completely understand the issue here. What visual studio macro's are you refering to? I did build YSE with visual studio and had no problems there.
If you are using the YSE binary release they can be changed indeed, because they're just enums. It is the value that is passed around in the library, not the name.
@yvanvds Sorry, i had winapi on my mind, not visual studio.
Ok, i see now. Those files (especially wingdi.h) contain a lot of defines. And that's problem with defines: they're not in a namespace. Whatever name I pick, there will always be some header file out there that uses the same name.
Perhaps you could try including wingdi.h first, followed by:
After that, include yse.hpp
https://github.com/yvanvds/yse-soundengine/blob/master/yse/sound/sound.hpp#L36 -> SOUND::MESSAGE:: RELATIVE (wingdi.h) https://github.com/yvanvds/yse-soundengine/blob/master/yse/synth/synth.hpp#L37 -> SYNTH::MESSAGE:: CALLBACK (minwindef.h)
Works fine when renamed (looks like nothing depend on these names);