UE5 support? - Githubissues

caseymcc / UE4CMake

Provides a simple way to add a cmake lib to any Unreal Engine 4 (UE4) or 5 (UE5) project.

MIT License

78 stars 14 forks source link

UE5 support? #2

Closed connorjak closed 1 year ago

connorjak commented 2 years ago

I use vcpkg / CMake for my separate server application, and upgrading to UE5 broke UnrealGDAL (https://github.com/TensorWorks/UnrealGDAL), so I'm considering transitioning to UE_CMake instead to be able to share a gdal installation between the codebases. I have some questions:

How would upgrading to UE5 go? I'll be trying this myself but any guidance would be appreciated.
Is there anything in the way of me specifying a CMake toolchain to use (-DCMAKE_TOOLCHAIN_FILE...)?

caseymcc commented 2 years ago

I haven't tried it with UE5 yet but unless something major changed with the build tools I would I imagine that it will work.

You should be able to add the toolchain on the end of the CMakeTarget call, using {cmake args}.

CMakeTarget.add(Target, this, "{lib's cmake target name}", "{location to cmake lib source}", "-DCMAKE_TOOLCHAIN_FILE=...");

If I get a chance I will see if I can test UE5, however on the toolchain it might be better to build the toolchain file based on information from the build tools (if it is possible) that way the ue build and the cmake build agree on the build info.

connorjak commented 2 years ago

My particular use case for this is sharing a vcpkg installation of a few libraries including GDAL, which is accomplished by vcpkg supplying the toolchain that fulfills find_package calls in CMake.

caseymcc commented 2 years ago

ah, never used vcpkg. seems a little invasive to use the toolchain option like that but would have to spend some time with it to get an idea for sure. Likely a plug-in that used vcpkg directly would be better than ue->cmake->vcpkg. Also if hunter has the packages you need it might work better in this case, it's what I use with my ue projects

connorjak commented 2 years ago

vcpkg has its own package download / update tooling but the build configuration stuff is all CMake-based. The way I use it with my team actually removes most of the "vcpkg" parts by generating a vcpkg-export set of binaries. The toolchain file populates the package .cmake files so the application can find the installed libraries.

caseymcc commented 1 year ago

Closing till a UE5 issue shows up

caseymcc commented 1 year ago

Looks like there were a few issues with UE5 (mainly removal of target platforms). Those should be fixed with https://github.com/caseymcc/UE4CMake/pull/4