Configuration of a mere generated Hello app is failing on Windows about cutelyst

[dantti]

The Wiki ATM if free to everyone to edit, so be welcome :)

[texpert]

Here I made it - #54, @dantti

Though, the Wiki needs some additions in regards to building and running on Windows. Could do it later, if you're accepting the PR.

[dantti]

Closing this as mentioned on the PR

[ccassan]

Hello,
I see that this issue is closed but I still have issues with the training as of 01/10/2018 on windows.
It complained about not finding CuteLystQt5Config.cmake, on my install it is called CuteLyst2Qt5Config.cmake. I went further by renaming the file, and generated the Hello code. Now it fails at the cmake .. command, not finding Cutelyst2Qt5Targets.cmake.

D:\CuteLyst\MyTests\Hello\build>cmake ..
CMake Error at D:/CuteLyst/cutelyst/build/CutelystQt5Config.cmake:13 (include):
include could not find load file:

D:/CuteLyst/cutelyst/build/Cutelyst2Qt5Targets.cmake

Call Stack (most recent call first):
CMakeLists.txt:16 (find_package)

This file exists on my machine but under D:\CuteLyst\cutelyst\build\CMakeFiles\Export_usr\lib\cmake\Cutelyst2Qt5
I'm not familiar with cmake, should this file have been moved when I compiled cutelyst? The compilation seemed ok.

Thanks for your help

[dantti]

Cutelyst master branch is v2.0 you should use v1.x.x branch ATM

[ccassan]

Thank you, it worked better with the branch. The training info on the wiki is targeting Linux, with references to .so and such, so it doesn’t work out of the box but I should be able to find my way through it. Thanks

[Plaristote]

Seems like the v2 is stable now, yet this issue still is valid. I've got the same issue with that missing Cutelyst2Qt5Targets.cmake file, referenced by Cutelyst2Qt5Config.cmake... is that file supposed to exist, and what's supposed to generate it ?

I've been using Qt 5.12 and msvc2017. Clearly not an entirely supported setup, considering Cutelyst doesn't compile out of the box with Qt 5.12 (minor issue due to the lack of Qt::endl in earlier versions of Qt). Still, it would be pretty damn handy to me if I could properly link my projects to Cutelyst in that environment.