From: lane-brain <lane-brain@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: vinstall doesn't work with wildcards?
Date: Mon, 07 Dec 2020 01:05:20 +0100 [thread overview]
Message-ID: <20201207000520.uLCtu9VKJDlW9PuRGadLvQf4LHMUOkevAc-f8_exF38@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26881@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2375 bytes --]
New comment by lane-brain on void-packages repository
https://github.com/void-linux/void-packages/issues/26881#issuecomment-739589766
Comment:
@harrisonthorne I was able to build dexed vst and vst3 plugins with this installed. Can you confirm if it will work for your templates?
```
# Template file for 'steinberg-vst-devel'
pkgname=steinberg-vst-devel
version=3.6.14
revision=1
short_desc="Steinberg's VST SDK (version 3.6)"
homepage="https://www.steinberg.net/sdk_downloads/"
hostmakedepends="unzip"
maintainer="lane-brain <lane@mailbox.org>"
_sdkarchive="vst-sdk_3.6.14_build-24_2019-11-29.zip"
distfiles="https://download.steinberg.net/sdk_downloads/${_sdkarchive}
https://www.steinberg.net/sdk_downloads/vstsdk367_03_03_2017_build_352.zip"
wrksrc=${pkgname}-${version}
license="custom:Steinberg"
checksum="1f61d847d4fbd570a2b3d3cc14210b4e7f808f87b641a44b146a07f708cb1552
5e8f1058177472f6dd3b5c1e7f8e0e76f37c5f751fed65936e04ff2441ce831a"
repository=nonfree
do_extract() {
mkdir current vst-sdk-367
cd current
unzip ${XBPS_SRCDISTDIR}/${pkgname}-${version}/${_sdkarchive}
cd ../vst-sdk-367
unzip ${XBPS_SRCDISTDIR}/${pkgname}-${version}/vstsdk367_03_03_2017_build_352.zip
}
pre_install() {
cd ${wrksrc}/current/VST_SDK
cp -r VST2_SDK/* VST3_SDK
}
do_install() {
# Install headers
echo "do_install: $PWD"
vst_sdk_path="${wrksrc}/current/VST_SDK/VST3_SDK"
vst_legacy_path="${wrksrc}/vst-sdk-367/VST_SDK"
header_path="usr/include/vst36"
mkdir -p ${DESTDIR}/${header_path}
vcopy ${vst_sdk_path}/* ${header_path}
mkdir -p ${DESTDIR}/${header_path}/pluginterfaces/vst
vcopy ${vst_sdk_path}/pluginterfaces/vst ${header_path}/pluginterfaces/vst
# Install legacy headers from 3.6.7. According to the notes:
#
# "The VST2 SDK is not part anymore of the VST3 SDK, you have to use
# an older version of the SDK and copy the VST2_SDK folder into the VST_SDK folder."
vcopy ${vst_legacy_path}/VST2_SDK/pluginterfaces/vst2.x ${header_path}/pluginterfaces
# Clean up unneeded files/directories
cd ${DESTDIR}/${header_path}
rm -r tools bin
}
post_install() {
vlicense ${wrksrc}/current/VST_SDK/VST3_SDK/LICENSE.txt
vlicense ${wrksrc}/current/VST_SDK/VST3_SDK/VST3_License_Agreement.pdf
}
```
next prev parent reply other threads:[~2020-12-07 0:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 5:13 [ISSUE] " harrisonthorne
2020-12-02 5:24 ` CameronNemo
2020-12-06 21:54 ` lane-brain
2020-12-06 21:56 ` lane-brain
2020-12-06 21:58 ` harrisonthorne
2020-12-06 21:59 ` lane-brain
2020-12-06 22:19 ` lane-brain
2020-12-06 22:20 ` lane-brain
2020-12-06 22:23 ` harrisonthorne
2020-12-06 22:31 ` lane-brain
2020-12-06 22:31 ` lane-brain
2020-12-06 22:31 ` lane-brain
2020-12-06 22:32 ` lane-brain
2020-12-06 22:36 ` lane-brain
2020-12-07 0:05 ` lane-brain [this message]
2020-12-07 0:06 ` lane-brain
2021-01-21 17:25 ` ericonr
2021-01-21 17:25 ` [ISSUE] [CLOSED] " ericonr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201207000520.uLCtu9VKJDlW9PuRGadLvQf4LHMUOkevAc-f8_exF38@z \
--to=lane-brain@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).