Conflicting "define" values

Code
1

Hello,

The project I am working on uses a lot of scripts (.bat) to define some stuff finally used by CMake, which is called at the end.
When CMake is called, a value is defined and passed as argument :
cmake -D PLATFORM=%PLATFORM% (the value may be x86 or x64)

I am now trying to use a library through the FetchContent feature.
The problem is that library has a CMake script which uses/defines also PLATFORM, but with an other meaning :

Both meanings are legitimate, but how avoiding this conflict ? I guess I could simply rename PLATFORM in my scripts/CMakeLists.txt (although it annoys me), but I think this kind of situation may happen frequently.
Is there a good way to resolve that ?

Thanks.

2

I recommend that you namespace your own options. It keeps them nicely grouped and if vendoring happens (your project being vendored or vendoring another), it keeps projects from stepping on each other’s toes.

So I would name things I see here like RAYLIB_PLATFORM, RAYLIB_OPENGL_VERSION, RAYLIB_BUILD_EXAMPLES, etc.

3

OK, thanks.

I opened an issue on the library’s Github.