Move binary files to neoAssets

[AdamTadeusz]

Description

Move all asssets to neoAssets.

Toolchain

• Windows MSVC VS2022
• Linux GCC Distro Native [Specify distro + GCC version]
• Linux GCC 10 Sniper 3.0

Linked Issues

[Rainyan]

Do we want to pin this to a static GIT_TAG? That'd require PRs for both repos whenever there's an asset update on the binary side.

[AdamTadeusz]

Do we want to pin this to a static GIT_TAG? That'd require PRs for both repos whenever there's an asset update on the binary side.

As this works right now you would have to do that anyway since the commit hash in the cmake file this repository has to be updated to use new assets in the asset repository. I probably am misunderstanding what you said though.

[AdamTadeusz]

Do we want to pin this to a static GIT_TAG? That'd require PRs for both repos whenever there's an asset update on the binary side.

So you're just suggesting we use git tags instead of git commit hashes to reference versions of the assets repository? These and even branch names can be used if I understand correctly, unless we use use the git_shallow parameter in which case only branch names can be used I think

[AdamTadeusz]

Never mind im retarded, you're suggesting we don't select the version of assets used. So yeah we could point to the master branch for example and add the git shallow tag and that would mean we don't need an extra pr here and it would be even quicker to fetch the git asset repository. The only question is would older versions of this repo break with newer assets. The only things that might break in the future are probably like materials, but also the stuff we are planning with navmeshes might for some reason not be compatible with older version of the repo I don't know

[Edit] Since the binary assets that are currently in this repository are version controller it seems like a safe bet to continue that practice by grabbing a specific version of those assets once they're in a different repository, but again I think it's unlikely anything will break with newer assets

[Rainyan]

Yeah, I meant we most likely want to use a tag that points to the most recent change (like master), to avoid having to create somewhat superfluous PRs in the code repo to manually keep the two in sync whenever the binary repo receives an update.

Pinning dependencies by hash is nice for reproducability, but for convenience we probably don't need super strict control over the asset versioning for the assets in particular. At least not for dev builds.

[AdamTadeusz]

Ill mark this as ready for review once Masterkatze has time to mess around with copy_directory versus the install command

[Masterkatze]

LGTM.

The use of copy_directory is fine since we copy it inside the same repo.

If someone wants to use manually cloned neoAssets:

1. Set FETCHCONTENT_FULLY_DISCONNECTED to ON
2. Set FETCHCONTENT_SOURCE_DIR_NEO_ASSETS to the path of cloned neoAssets repo