Bug: c2wwise forces plugin version to correspond to Wwise version

[eu-ch]

bundle_template.json sets targetWwiseVersion to be the same as plugin version, but it should be set based on parsing AkWwiseSDKVersion.h or $WWISEROOT/install-entry.json

    "id": "Heavy.{{name}}.${year}_${major}_${minor}_${build}",
    "name": "{{name}}",
    "tag": "{{name}}",
    "description": "",
    "vendor": "Heavy",
    "image": "data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAQAAAC1HAwCAAAAC0lEQVR42mNkYAAAAAYAAjCB0C8AAAAASUVORK5CYII=",
    "type": "plugin",
    "productDependentData": {
        "targetWwiseVersion": {
            "year": ${year},
            "major": ${major}
        }
    },

[dromer]

Hmm, not sure how we can decouple this. Perhaps we need a separate step for creating the bundle?

Because after your refactor the rest of the code no longer depends on a specific SDK right?

I'm not even sure what is even using bundle_template.json. c2wwise copies it over, but none of these fields have variables that can be used.

[eu-ch]

Copying my answer from discord. I can get version from certain files in the Wwise SDK folder (I've mentioned two possible options in the ticket). Bundle template us used for making installable bundles and it requires an image, so here you go 🙂 I can possibly include a hvcc logo there instead

bundle_template itself is turned into a bundle.json when making a package

[dromer]

Ok, so this bundle template is used by the wwise SDK scripts, not by c2wwise?

[eu-ch]

Ok, so this bundle template is used by the wwise SDK scripts, not by c2wwise?

Correct. I just want making plugin bundles as frictionless as possible. It's a really useful feature of new build system and I liked using it in past projects.

I can just check do of files under $WWISEROOT of what's installed and fall back to using current setup. See install-entry.json under Wwise installation, it contains all metadata about installed SDK packages.