Open MeachamusPrime opened 5 years ago
Is the problem here not simply that normal escaping is applied, so '\Me' is treated as the escape character '\M' followed by 'e'? Does it work if you properly escape the backslashes as '\'? Single-quoted strings are not escaped, so does using single-quotes for Windows paths work?
I'm successfully building with clang-cl in Visual Studio compatibility mode on Windows using CMake for Windows and Google Ninja. My goal was to get around using any paywalled Microsoft software. Downloading the Windows 10 SDK was required for success. The build works with one quirk.
When the include paths on windows are passed manually (I didn't test any automated functionality), as in:
the '\' characters have been removed when processing the directories.
The workaround I propose to be added to the README is a warning that users on Windows should change all path related '\' characters for include paths to '/' characters.
Details: Apologies if this has been remedied already. My testing is on an older version as the latest version breaks some of my macros. It's not convenient for me to work a patch for the latest version at the moment or I would have simply made a pull request.
The reason appears to be that while iterating through the array, I think it is going through
ucl_object_tostring()
, but it eventually gets toucl_copy_value_trash()
andobj->type
is not set toUCL_STRING
so it goes down to callucl_object_emit_single_json()
and the JSON emitter is removing the '\' characters, believing them to be escape characters.