brian/Cardinal
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

FreeBSD related fixes

Browse source 
Signed-off-by: falkTX <falktx@falktx.com>
This commit is contained in:
falkTX 2022-02-07 19:49:47 +00:00
parent 567a264f7f
commit a6e8bef774
No known key found for this signature in database
GPG key ID: CDBAA37ABC74FBA0
4 changed files with 33 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

2
.gitmodules vendored
View file

@ -129,7 +129,7 @@
url = https://github.com/CardinalModules/ihtsyn.git url = https://github.com/CardinalModules/ihtsyn.git
[submodule "deps/QuickJS"] [submodule "deps/QuickJS"]
path = deps/QuickJS path = deps/QuickJS
url = https://github.com/JerrySievert/QuickJS.git url = https://github.com/CardinalModules/QuickJS.git
[submodule "plugins/Autinn"] [submodule "plugins/Autinn"]
path = plugins/Autinn path = plugins/Autinn
url = https://github.com/NikolaiVChr/Autinn.git url = https://github.com/NikolaiVChr/Autinn.git

2
carla

@ -1 +1 @@
Subproject commit afc25ae3137be9cb7addedd16ff45fbe0ab4ea97 Subproject commit b8d38e395c215eed189a4849972f90af810ef971

2
deps/QuickJS vendored

@ -1 +1 @@
Subproject commit b70d5344013836544631c361ae20569b978176c9 Subproject commit 9ed118744671f1e257ebb0d731300ba115f6cfce

33
doc/BUILDING.md
View file

@ -38,7 +38,23 @@ Advanced options:
## FreeBSD ## FreeBSD
TODO Dependencies for using system libraries, that is, with `SYSDEPS=true`:
```
# common
sudo pkg install -A dbus libglvnd liblo libsndfile libX11 libXcursor libXext libXrandr
# system libraries
sudo pkg install -A libarchive libsamplerate jansson speexdsp
```
Dependencies for vendored libraries:
```
# common
sudo pkg install -A dbus libglvnd liblo libsndfile libX11 libXcursor libXext libXrandr
# nedeed by vendored libraries
sudo pkg install -A cmake
```
## Linux ## Linux
@ -121,6 +137,9 @@ After a successful build you will find the plugin binaries in the `bin/` directo
You can either install them to your system using e.g. `make install PREFIX=/some/prefix` (not recommended for local source builds) You can either install them to your system using e.g. `make install PREFIX=/some/prefix` (not recommended for local source builds)
or preferably just create a symbolic link on the respective plugin format folders. or preferably just create a symbolic link on the respective plugin format folders.
Cardinal plugin binaries expect to remain *within* their parent bundle/folder.
If you move them around make sure to keep their folder structure intact.
If you are a packager you pretty much already know what to do at this point, otherwise regular users might want to do something like: If you are a packager you pretty much already know what to do at this point, otherwise regular users might want to do something like:
``` ```
@ -130,6 +149,8 @@ ln -s $(pwd)/bin/*.vst ~/.vst/
ln -s $(pwd)/bin/*.vst3 ~/.vst3/ ln -s $(pwd)/bin/*.vst3 ~/.vst3/
``` ```
## macOS
If running macOS, use this instead: If running macOS, use this instead:
``` ```
@ -139,10 +160,14 @@ ln -s $(pwd)/bin/*.vst ~/Library/Audio/Plug-Ins/VST/
ln -s $(pwd)/bin/*.vst3 ~/Library/Audio/Plug-Ins/VST3/ ln -s $(pwd)/bin/*.vst3 ~/Library/Audio/Plug-Ins/VST3/
``` ```
Symbolic links are not supported on Windows, so this approach doesn't work there. Note: Official macOS Cardinal builds install in the system-wide `/Library/Audio/Plug-Ins` location.
Watch out for conflicts if switching between the two builds.
Note that the plugins expect to remain *within* their parent folder. ## Windows
If you move them around make sure to keep their folder structure intact.
Symbolic links are not supported on Windows, so this approach doesn't work there.
On Windows you will have to copy or move the plugin bundles.
If you are building from source, it is expected you know where they should go.
# Keeping up to date # Keeping up to date