# Building on Raspberry Pi

**URL:** <https://forum.cabbageaudio.com/t/building-on-raspberry-pi/121>\
**Category:** Cabbage Farmers\
**Created:** [4 February 2016 12:59 UTC](https://forum.cabbageaudio.com/t/building-on-raspberry-pi/121 "2016-02-04T12:59:14Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![RedMagnet](https://forum.cabbageaudio.com/letter_avatar_proxy/v4/letter/r/d2c977/32.png) [@RedMagnet](https://forum.cabbageaudio.com/u/RedMagnet)\
**Post date:** [4 February 2016 12:59 UTC](https://forum.cabbageaudio.com/t/building-on-raspberry-pi/121/1 "2016-02-04T12:59:14Z")

</div>

Dear Cabbage farmers,

I’ve been trying to get Cabbage to work on my Raspberry Pi 2.  
I’ve installed all the dependecies but I get serious errors, and don’t know how to deal with them. Any advice would be much appreciated!  
This is the first error I get, many more like this one follow:

Compiling ComponentLayoutEditor.cpp  
cc1plus: error: bad value (native) for -march switch

I’m running Raspbian (not sure which version, not yet fully up to speed with Linux).  
Thanks,  
RM

PS. Rory, thank you for making CSound so much fun again!

---

<div class="post-metadata">

**Author:** ![gsenna](https://forum.cabbageaudio.com/letter_avatar_proxy/v4/letter/g/a88e4f/32.png) [@gsenna](https://forum.cabbageaudio.com/u/gsenna)\
**Post date:** [4 February 2016 18:29 UTC](https://forum.cabbageaudio.com/t/building-on-raspberry-pi/121/2 "2016-02-04T18:29:11Z")

</div>

Hi,

What version of g++ do you have? You’ll have to modify the Makefiles.

I’ve found this on the [raspberrypi.org](http://raspberrypi.org) forum:

For gcc 4.8 I use  
gcc-4.8 -mcpu=cortex-a7 -mfpu=neon-vfpv4 -mfloat-abi=hard

This gave me the best code and was the only option that enabled sdiv/udiv.  
To get gcc 4.8 just do  
sudo apt-get install gcc-4.8

For gcc 4.6 (the default compiler on rasbian)  
gcc -march=armv7-a -mfpu=neon-vfpv4 -mfloat-abi=hard

For a Pi 1 (B+)  
gcc -mcpu=arm1176jzf-s -mfpu=vfp -mfloat-abi=hard

---

<div class="post-metadata">

**Author:** ![rorywalsh](https://forum.cabbageaudio.com/user_avatar/forum.cabbageaudio.com/rorywalsh/32/165_2.png) [@rorywalsh](https://forum.cabbageaudio.com/u/rorywalsh)\
**Post date:** [4 February 2016 18:54 UTC](https://forum.cabbageaudio.com/t/building-on-raspberry-pi/121/3 "2016-02-04T18:54:44Z")

</div>

Best to change the arch flags in the makefiles. I haven’t used Cabbage on a PI myself, but I know someone who is using Cabbage and PI for live music, so it definitely works. Good luck with your Cabbage Pie!

---

<div class="post-metadata">

**Author:** ![RedMagnet](https://forum.cabbageaudio.com/letter_avatar_proxy/v4/letter/r/d2c977/32.png) [@RedMagnet](https://forum.cabbageaudio.com/u/RedMagnet)\
**Post date:** [6 February 2016 10:33 UTC](https://forum.cabbageaudio.com/t/building-on-raspberry-pi/121/5 "2016-02-06T10:33:01Z")

</div>

Thanks for the tips! They helped me a lot. I managed to build Cabbage! 😄  
The only problem now is that the UI doesn’t get updated properly. So menus pile up on top of each other. When I load an example the window size will change but it still show the start-up screen. Also I cannot get the source editor to open up.  
Any ideas?

I’ll leave a note of what worked to build on Raspbian for reference.  
I had to update gcc and g++ to version 4.8  
sudo apt-get install gcc-4.8  
sudo apt-get install g+±4.8

I then changed the symlinks to gcc and g++ to point to the 4.8 versions, so that the gcc and g++ commands pick the right version.  
rm /usr/bin/gcc  
rm /usr/bin/g++  
ln -s /usr/bin/gcc-4.8 /usr/bin/gcc  
ln -s /usr/bin/g+±4.8 /usr/bin/g++

Also make sure to have the correct version of CSound installed (the default was 5.x, and 6.0.3 is needed). Building CSound is easy, just follow these instructions:  
[http://ikenberrypi.tumblr.com/post/90967171834/compiling-csound-6-on-the-raspberry-pi](http://ikenberrypi.tumblr.com/post/90967171834/compiling-csound-6-on-the-raspberry-pi)

The last thing is to make sure the VST SDK is at ~/SDKs/vstsdk2.4  
I was not able to make it work with any other location, some Juce sources would fail.

---

<div class="post-metadata">

**Author:** ![rorywalsh](https://forum.cabbageaudio.com/user_avatar/forum.cabbageaudio.com/rorywalsh/32/165_2.png) [@rorywalsh](https://forum.cabbageaudio.com/u/rorywalsh)\
**Post date:** [6 February 2016 11:34 UTC](https://forum.cabbageaudio.com/t/building-on-raspberry-pi/121/6 "2016-02-06T11:34:37Z")

</div>

I’ve just emailed one of the guys who had it running as part of a live setup. I’ll let you know what he gets back to me with, or perhaps he’ll join the discussion directly.

---

<div class="post-metadata">

**Author:** ![shreeswifty](https://forum.cabbageaudio.com/user_avatar/forum.cabbageaudio.com/shreeswifty/32/1375_2.png) [@shreeswifty](https://forum.cabbageaudio.com/u/shreeswifty)\
**Post date:** [11 December 2017 20:05 UTC](https://forum.cabbageaudio.com/t/building-on-raspberry-pi/121/7 "2017-12-11T20:05:35Z")

</div>

Hi

I am about to TRY to compile Cabbage for Raspberry Pi 3 with Csound 6.08  
Can someone give me some caveats before i go down a painful rabbit hole with this?

I have SuperCollider + Pure Data working plus some python audio apps but i would like to bring my csound skills back up from the ancient days So Dr. B recommended cabbage.

Will it work?

---

<div class="post-metadata">

**Author:** ![rorywalsh](https://forum.cabbageaudio.com/user_avatar/forum.cabbageaudio.com/rorywalsh/32/165_2.png) [@rorywalsh](https://forum.cabbageaudio.com/u/rorywalsh)\
**Post date:** [11 December 2017 21:48 UTC](https://forum.cabbageaudio.com/t/building-on-raspberry-pi/121/8 "2017-12-11T21:48:02Z")

</div>

I believe people have got it running there before. I’ve built Csound before, that should be fine. Just follow the Linux guidelines and you might get lucky!

---

<div class="post-metadata">

**Author:** ![alcomposer](https://forum.cabbageaudio.com/letter_avatar_proxy/v4/letter/a/f4b2a3/32.png) [@alcomposer](https://forum.cabbageaudio.com/u/alcomposer)\
**Post date:** [18 December 2017 13:31 UTC](https://forum.cabbageaudio.com/t/building-on-raspberry-pi/121/9 "2017-12-18T13:31:25Z")

</div>

I’ve been able to build Csound quite easily on MacOS & Arch. Arch was a bit easier. I have yet to build Cabbage however.

Fun thing about DIY building is you can checkout branches and test new features.

---

<div class="post-metadata">

**Author:** ![rorywalsh](https://forum.cabbageaudio.com/user_avatar/forum.cabbageaudio.com/rorywalsh/32/165_2.png) [@rorywalsh](https://forum.cabbageaudio.com/u/rorywalsh)\
**Post date:** [18 December 2017 13:32 UTC](https://forum.cabbageaudio.com/t/building-on-raspberry-pi/121/10 "2017-12-18T13:32:57Z")

</div>

I think it should build relatively easily on RPi. Let us know how it goes. I’m pi-less for the next few weeks so I won’t be able to try it out myself.

---

<div class="post-metadata">

**Author:** ![alcomposer](https://forum.cabbageaudio.com/letter_avatar_proxy/v4/letter/a/f4b2a3/32.png) [@alcomposer](https://forum.cabbageaudio.com/u/alcomposer)\
**Post date:** [18 December 2017 13:39 UTC](https://forum.cabbageaudio.com/t/building-on-raspberry-pi/121/11 "2017-12-18T13:39:14Z")

</div>

Pi-less during Christmas? Sounds like a good present! 🙂

---

<div class="post-metadata">

**Author:** ![shreeswifty](https://forum.cabbageaudio.com/user_avatar/forum.cabbageaudio.com/shreeswifty/32/1375_2.png) [@shreeswifty](https://forum.cabbageaudio.com/u/shreeswifty)\
**Post date:** [9 January 2018 18:30 UTC](https://forum.cabbageaudio.com/t/building-on-raspberry-pi/121/12 "2018-01-09T18:30:26Z")

</div>

this guy is taxxing my linux64 with 32GB of RAM raspberry would just be masochism

---

<div class="post-metadata">

**Author:** ![rorywalsh](https://forum.cabbageaudio.com/user_avatar/forum.cabbageaudio.com/rorywalsh/32/165_2.png) [@rorywalsh](https://forum.cabbageaudio.com/u/rorywalsh)\
**Post date:** [9 January 2018 21:35 UTC](https://forum.cabbageaudio.com/t/building-on-raspberry-pi/121/13 "2018-01-09T21:35:00Z")

</div>

Really? I do most of my testing and development on a 4gb i3 laptop(Linux) and I’ve never been horrified by the performance. I also have access to more powerful machines, but I reckon a RPi might not be the worst 😉
