[joltphysics] Add new port

[RT2Code]

I know this is not what's advocated for vcpkg, but for this port, I'm using the latest commit instead of the latest release version. The reason for that is that since the previous release, the CMakelist.txt file have been improved a lot, supports many more platforms and it was far easier to make a working and clean port from it.

• What does your PR fix?

Add new port joltphysics : https://github.com/jrouwe/JoltPhysics

• Which triplets are supported/not supported? Have you updated the [CI baseline]

All. No.

• Does your PR follow the [maintainer guide]

Yes

• If you have added/updated a port: Have you run ./vcpkg x-add-version --all and committed the result?

Yes

[JavierMatosD]

Hi @RT222, thank you for the PR!

You mentioned using the latest upstream commit instead of their latest release. However, we can't do this without upstreams approval. I went ahead and reached out to see if they approved or if they were willing to make an early release.

Additionally, I noticed that this port doesn't provide any usage instructions. Under some conditions,
vcpkg will generate the usage instructions, but this port does not. Would you mind adding them?

To do so,

1. Create a file named usage in the port directory with the content you want to display.
   Here is an example using zlib:

The package zlib is compatible with built-in CMake targets:

    find_package(ZLIB REQUIRED)
    target_link_libraries(main PRIVATE ZLIB::ZLIB)

2. To the portfile.cmake, add

file(INSTALL "${CMAKE_CURRENT_LIST_DIR}/usage" DESTINATION "${CURRENT_PACKAGES_DIR}/share/${PORT}")

3. Rerun vcpkg x-add-version

I will keep the info:reviewed label while I wait for upstream's response to make sure we don't drop this.

[jrouwe]

The library should support ARM and UWP now.

[jrouwe]

I've created a new release of the library: v2.0.0.

[JavierMatosD]

@RT222 It looks like @jrouwe was kind enough to do a release for us, so please update the port and version to the latest release. Additionally, the library now supports arm and uwp. We can delete them from the support clause. Finally, the usage text file is not technically required, so that wouldn't block this PR. That said, it would be very helpful. :)

[RT2Code]

Thanks @JavierMatosD for the assistance, and thanks @jrouwe for your reactivity and for sharing with us this awesome library.

There's still some issues to tackle before the port is ready :

• Thank you for adding support for ARM and UWP. Unfortunately, I still can't build your library on this platform with vcpkg, it fails with the following compilation error :
  Jolt\Core\Core.h(109): fatal error C1189: #error: Unsupported CPU architecture
• By default, vcpkg use the Debug and Release build type modes. In the JoltPhysics documentation, it is mentioned that the Release mode include support for profiling and debug rendering. Do you think it would be more appropriate to use the Distribution instead of the Release build type mode?

[jrouwe]

Jolt\Core\Core.h(109): fatal error C1189: #error: Unsupported CPU architecture

By default it detects the ARM platform by: #if defined(__aarch64__) || defined(_M_ARM64). This works on my machine, but maybe _M_ARM64 is not set when building as a package for some reason (maybe it's compiling in emulation mode and also _M_ARM64EC needs to be checked)? What do I need to do to repro this?

Do you think it would be more appropriate to use the Distribution instead of the Release build type mode?

Yes, Distribution is better if there are only 2 choices to make.

[jrouwe]

Ok, I know what is going on. It's trying to compile the 32-bit ARM version instead of the 64-bit version.

vcpkg install joltphysics:arm64-uwp

works,

vcpkg install joltphysics:arm-uwp

doesn't.

Let me see if a 32-bit version can work.

[jrouwe]

The latest version on 'master' should work now. Please let me know if it works for you too and then I'll create a release with it.

[RT2Code]

I can confirm that it's working fine now, well done. :)

[jrouwe]

Ok, I created release 2.0.1

[RT2Code]

I think it's ready to go.

[BillyONeal]

@RT222 Thanks again for the new port!
@jrouwe Thanks for being a great upstream maintainer and tagging meaningful releases!
@JavierMatosD Thanks for bringing these folks together!
@JonLiu1993 Thanks for the initial review!