Cannot built application against installed engine becaues of incorrect Utility/DirectXMath header files location

[ibbles]

I'm trying to build my first application using Wicked Engine. I started following the instructions at https://github.com/turanszkij/WickedEngine/blob/master/Content/Documentation/WickedEngine-Documentation.md#building-and-linking but they were somewhat lacking. After using target_include_directories to point to the header files and target_link_libraries to point to libWickedEngine.a during building I got errors such as SDL_GetWindowSize not being declared, invalid conversions from void* to SDL_Window*, and error: inlining failed in call to ‘always_inline’ ‘__m128i _mm_cvtps_ph(__m128, int)’: target specific option mismatch which I have no idea what it means. And probably more I don't remember and didn't write down.

As Wicked Engine is a CMake project I instead tried the regular CMake procedure of setting CMAKE_INSTALL_PREFIX for Wicked Engine and building with cmake --build . --target install, then adding list(APPEND CMAKE_PREFIX_PATH "/path/to/WickedEngineInstall") and target_link_libraries(wicked_engine_app PRIVATE WickedEngine::WickedEngine) to my application's CMakeLists.txt. That adds a bunch of compiler and linker flags that I hope will resolved the errors described above, but I also got WickedEngine/wiMath.h:29:10: fatal error: Utility/DirectXMath/DirectXMath.h: No such file or directory which sounds more like a packaging problem than a compiler command line flags problem.

I think the source of the problem is in WickedEngine/Utility/CMakeLists.txt:8 and line 29 in the same file. These do a GLOB_RECURSE to gather up all the Utility header files and then dumps them in "${CMAKE_INSTALL_INCLUDEDIR}/WickedEngine/Utility/. This means that DirectXMath.h, which is in Utility/DirectXMath/ in the repository, ends up in Utility/ (no DirectXMath/) in the installed package. This causes all other Utility files that include Utility/DirectXMath/DirectXMath.h to fail to compile.

I don't see how I can resolve this from the consumer / application side, I think this needs a fix in Wicked Engine.

[turanszkij]

Please check out this sample on how to set up a basic application with Wicked Engine with Cmake (on Linux):
https://github.com/turanszkij/WickedEngine/tree/master/Samples/Template_Linux

You can also just copy this directory with a new name and build your application logic in it.
Let me know if you still have problems.

[brakhane]

Installing WickedEngine is currently broken, building in-tree by copying Template_Linux works, though.

I'll try to make a PR soon that removes the install stuff.

[ibbles]

I would prefer to use Wicked Engine as an external library in my existing project / CMake setup, which I cannot easily shoe-horn into the Wicked Engine source tree.

Skipping the install step and pointing my CMakeLists.txt to the engine's build directory seems to work. I can build and run my main.cpp which is a copy/paste from the Linux template, and a get a black window with some text in the upper-left corner, the same as when running the Template_Linux executable from the engine samples.

So I'm happy and we can close this thread, but I would like to see proper install support working at some point.

[brakhane]

Sure, installing WickedEngine is definitely useful, but currently there are some problems with compiling it as an .so (can't remember which exactly).

As it currently stands, the install target is unmaintained and doesn't work; that's why I think removing it for now is the better solution. Making Wicked installable is definitely something we should make possible (again) in the future.