1
0
Fork 0

Create plugin bundles in target/bundled

It's going to get a bit crowded otherwise once we add more formats.
This commit is contained in:
Robbert van der Helm 2022-02-26 20:04:41 +01:00
parent d39ebb5b51
commit 72c3e00510
2 changed files with 7 additions and 4 deletions

View file

@ -118,7 +118,7 @@ jobs:
- name: Move all packaged plugin into a directory
run: |
mkdir "$ARCHIVE_NAME"
mv target/*.vst3 "$ARCHIVE_NAME"
mv target/bundled/* "$ARCHIVE_NAME"
- uses: actions/upload-artifact@v2
with:
name: ${{ env.ARCHIVE_NAME }}

View file

@ -10,6 +10,9 @@ mod symbols;
const USAGE_STRING: &str =
"Usage: cargo xtask bundle <package> [--release] [--target <triple>] [--bundle-vst3]";
/// The base birectory for the bundler's output.
const BUNDLE_HOME: &str = "target/bundled";
/// Any additional configuration that might be useful for creating plugin bundles, stored as
/// `bundler.toml` alongside the workspace's main `Cargo.toml` file.
type BundlerConfig = HashMap<String, PackageConfig>;
@ -103,7 +106,7 @@ fn bundle(package: &str, mut args: Vec<String>) -> Result<()> {
eprintln!();
if bundle_vst3 {
let vst3_lib_path = Path::new("target").join(vst3_bundle_library_name(
let vst3_lib_path = Path::new(BUNDLE_HOME).join(vst3_bundle_library_name(
&bundle_name,
cross_compile_target.as_deref(),
)?);
@ -250,9 +253,9 @@ fn maybe_create_macos_vst3_bundle(package: &str, cross_compile_target: Option<&s
}
// TODO: May want to add bundler.toml fields for the identifier, version and signature at some
// point.
// point.
fs::write(
format!("target/{}.vst3/Contents/PkgInfo", package),
format!("{}/{}.vst3/Contents/PkgInfo", BUNDLE_HOME, package),
"BNDL????",
)
.context("Could not create PkgInfo file")?;