search

atsushieno / aap-juce

AAP (Audio Plugins For Android) JUCE integration.
GNU General Public License v3.0
15 stars 1 forks source link

strip out "aap-metadata-generator" part from ordinary build process. #21

Closed atsushieno closed 3 years ago

atsushieno commented 3 years ago

We run aap-metadata-generator to generate aap_metadata.xml from AudioProcessor implementation class. To achieve that, we first build Linux or Darwin version of the plugin, then link it to the extractor console tool.

That takes long time before starting the actual Android project build, while it is only to generate the metadata. And the metadata is actually unchanged unless code changes happen. It is good to run the metadata generator whenever code update occurs, but it actually rarely happens.

Thus, it is probably better to split out metadata generation task from the ordinary builds.

atsushieno commented 3 years ago

In aap-lv2 world I actually took that approach for aap-sfizz, and I actually triggered regression for inconsistent updates. So it is desirable to trigger some caution whenever we update the JUCE app submodule if we didn't regenerate metadata.

atsushieno commented 3 years ago

It is being worked on as isolate-metadata-gen branches in various repos.

atsushieno commented 3 years ago

It is merged into main (069844b).