https://github.com/lvm/build-supercollider

A dead simple script that builds and installs Supercollider
https://github.com/lvm/build-supercollider

installer-script supercollider

Last synced: 3 months ago
JSON representation

A dead simple script that builds and installs Supercollider

• Host: GitHub
• URL: https://github.com/lvm/build-supercollider
• Owner: lvm
• License: unlicense
• Created: 2017-03-24T18:17:42.000Z (over 7 years ago)
• Default Branch: master
• Last Pushed: 2021-12-18T20:22:43.000Z (over 2 years ago)
• Last Synced: 2024-01-17T19:19:40.784Z (6 months ago)
• Topics: installer-script, supercollider
• Language: Shell
• Size: 35.2 KB
• Stars: 67
• Watchers: 5
• Forks: 14
• Open Issues: 1
• Metadata Files:
  • Readme: README-deb.md
  • License: LICENSE

Lists

• awesome-supercollider - Build script for Linux - Easily build SuperCollider with plugins from source on Linux (Ubuntu/Debian) (Build scripts and templates / Other tools)

README

        
# Debian way

Dan Stowell posted an article about [how to package SC for debian/ubuntu](http://mcld.co.uk/blog/2017/how-to-package-supercollider-for-debian-and-ubuntu-linux.html), which seems to be the most sane way to build SC if you're using one of these distros.  

To make things simpler (and avoid breaking your OS), I've created Docker recipes to create a clean Debian and Ubuntu building environments with the necessary dependencies to properly build deb packages.

### Using Docker

In order to build the Docker image, enter to your prefered distro and:

```

$ docker build -t scdeb .

```

To run it after:

```

$ docker run --rm -it scdeb

```

### Dan's post

Once you have a clean Debian installation working, just follow his advice.  

The only thing that changes are:

`gbp import-orig --pristine-tar --sign-tags ${path-to-fetched-tarball}`  

He describes `../tarballs` as the directory where the repacked tar is placed, in my case this directory was simply `..` (the directory above).

`gbp buildpackage -S --git-export-dir=../buildarea`  

Same thing here: He describes `../buildarea` as the directory where the repacked tar is placed, in my case this directory was simply `..` (the directory above).

  

Also, since I'm not Felipe Sateler nor Dan Stowell, I wasn't able to sign the `.changes` or the `source`, so I used the flags `-uc -us` which doesn't sign the `.changes` / `source` respectively.  

ie: `gbp buildpackage -S -uc -us --git-export-dir=../`

### That's it.

If everything went well, you'll see a bunch of `.deb` files placed in the directory above of the cloned repository.