Pavel Liavonau

Fixed your last fail with 0117a159d6342f9c2d398a36bb8161d7eba95f62. Now that project could be parsed fine. It is hard to add warnings/suggestion because there are too many cases for failing at custom xml...

Try cmake-converter -w4 -s xxx.sln For getting missing unprocessed xml nodes. Check -h for available options.

Pathing like this works. But there might be exceptions of this rule. With my cases it looks fine. What case exactly do you have?

@smaudet , is it from build step/event?

It's hard to support VS Qt solutions because of many Qt specific things there. You should investigate by yourself why does it fail and fix input files. I can add...

I would not like to implement partial solution. It's not so easy to support Qt and all versions of it at VS solutions. Also I have no setup of Qt...

Cmake-converter works properly only with sln file. What are you proposing for example? C# is not so crossplatform. What kind of C# projects do you want to build with cmake?

@whschultz ,CMake creates target binary for current platform. I don't agree with you about cross-plarform of C# but.. Since this https://blogs.windows.com/buildingapps/2018/12/04/announcing-open-source-of-wpf-windows-forms-and-winui-at-microsoft-connect-2018/ I'll consider to implement support of *.csproj.

Better rename your symbols to latin words that cmake supports

I don't like Idea of generating names. Considered this from the very beginning. I shall not implement a thing that CMake does not support. You may help CMake to implement...