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
Some parameters (like “${CMAKE_CURRENT_BINARY_DIR}/configure.h”) are passed to CMake commands in your build scripts without enclosing them by quotation marks. I see that these places will result in build difficulties if the contents of the used variables will contain special characters like semicolons.
You opened this exact issue five years ago on the magnum repository, don't you remember? ;) Because I do: mosra/magnum#24
If you look at your issue from 2013, there I proved that quoting is not necessary — CMake is not Unix shell, it will correctly preserve the space in variable substitutions. And to answer your second question from there — no, I don't plan bothering with paths containing semicolons. Unlike spaces, that's too hard to fix and not worth spending time with.
Some parameters (like “${CMAKE_CURRENT_BINARY_DIR}/configure.h”) are passed to CMake commands in your build scripts without enclosing them by quotation marks. I see that these places will result in build difficulties if the contents of the used variables will contain special characters like semicolons.
I would recommend to apply advices from a wiki article.
The text was updated successfully, but these errors were encountered: