Linux build

[atom]

I updated the linux build and at r286 it works with Renoise (it does not crash it at least, i checked), 32bit build is up.

But for those of you with a bit more hacking capabilities you can build your own Ctrlr, here is a quick howto.

You need some packages (depending on your distro they might be called differently, i’m basing this list on Ubuntu names)
– build-essential (gcc libc6-dev g++)
– freetype-dev (freetype6 devel files)
– xorg-dev (Xorg devel files)
– mesa (you might need it but it’s not necessary)
– libasound2-dev (ALSA development files)
– make
– libreadline-dev (for LUA)
– subversion
– git-core

create some directory (i use /home/atom/devel) and put all the below stuff in it

once you got those, get the latest JUCE source from git

git clone --depth 1 git://juce.git.sourceforge.net/gitroot/juce/juce

get the latest Ctrlr source from SVN

svn checkout http://svn.code.sf.net/p/ctrlrv4/code/nihtly ctrlr

you need to get the VSTSDK 2.4 from someplace (need to google it and find it yourselves it’s a license nightmare)

once all files are in your directory go to juce/extras/Introjucer/Builds/Linux and type make, it should build a binary "Introjucer" in the build directory

atom@ubuntu-x32:~/devel/juce/extras/Introjucer/Builds/Linux$ make -j4
Compiling jucer_DocumentEditorComponent.cpp
Compiling jucer_FilePreviewComponent.cpp
Compiling jucer_JuceUpdater.cpp
Compiling jucer_Main.cpp
Compiling jucer_MainWindow.cpp
Compiling jucer_OpenDocumentManager.cpp
Compiling jucer_SourceCodeEditor.cpp
Compiling jucer_GroupInformationComponent.cpp
Compiling jucer_NewFileWizard.cpp
Compiling jucer_NewProjectWizard.cpp
Compiling jucer_Project.cpp
Compiling jucer_ProjectContentComponent.cpp
Compiling jucer_ProjectExporter.cpp
Compiling jucer_ProjectInformationComponent.cpp
Compiling jucer_ProjectTreeViewBase.cpp
Compiling jucer_ResourceFile.cpp
Compiling jucer_TreeViewTypes.cpp
Compiling jucer_CodeHelpers.cpp
Compiling jucer_FileHelpers.cpp
Compiling jucer_JucerTreeViewBase.cpp
Compiling jucer_MiscUtilities.cpp
Compiling jucer_StoredSettings.cpp
Compiling BinaryData.cpp
Compiling JuceLibraryCode1.cpp
Compiling JuceLibraryCode2.cpp
Compiling JuceLibraryCode3.cpp
Compiling JuceLibraryCode4.cpp
Linking The Introjucer
atom@ubuntu-x32:~/devel/juce/extras/Introjucer/Builds/Linux$ ls build/Introjucer
build/Introjucer

this is not necessary but is very helpful, you can now launch this binary and open one of the Ctrlr jucer projects in the main ctrlr directory, there are two files: Ctrlr_Standalone.jucer and Ctrlr_Plugin.jucer. Once you open the you will be presented with some parameters for the build, in the "Linux Makefile" tab set your paths to the JUCE source and VSTSDK (if you are building the Plugin version). Once you have those paths set, save the project and exit Introjucer.

Enter the ctrlr root directory.

Go to ctrlr/Builds/Generated/Linux/Standalone and type make, this should build Ctrlr binary in the ctrlr/Bin path, if it works you can build the Release binary (without the debug symbols) by typing, make CONFIG=Release. If you have more then one cpu make -j4 will spawn more jobs and will build the binary faster.

That’s it you got your own Ctrlr build. In case some path issues fix them in Introjucer, remember witch config you are editing (there are two Debug and Release) and build this configuration only.

have phun

• This topic was modified 10 years, 11 months ago by atom.

[ungleichklang]

Where did the Linuxbuild go?? Can’t see it in the downloads for a while.

[atom]

well since noone said anything for quite some time i didn’t update the linux build, and the one that was there way too old.

[ungleichklang]

o.k. I say something ” title=”Wink” />
First I love it …
Standalone version ran quite stable most of the time. I tried to use it as a plugin and it crashed, but on my system most DSSI do that …. somewhere some misconfig

I now have a Blofeld and a Mopho to test the tool more intense

[mouzika]

Hi, wish you all best !

[nightmorph]

anyone been able to build the latest SVN on linux? rev 803.

i can’t get ctrlr to compile, even though i’ve compiled and run many other JUCE/VST-based projects before. the build seems to be failing because the #includes in [b:163mbrva]JuceLibraryCode/modules/[/b:163mbrva] are hardcoded to [b:163mbrva]/home/atom/devel[/b:163mbrva], and those [b:163mbrva].h[/b:163mbrva] files seem to be recursively linked to themselves.

a sample header file, [b:163mbrva]juce_audio_basics.h[/b:163mbrva], in JuceLibraryCode/modules/foo/bar/ looks like this:
[code:163mbrva]#if defined (JUCER_LINUX_MAKE_62C631A2)
#include "/home/atom/devel/juce/modules/juce_audio_basics/juce_audio_basics.h"[/code:163mbrva]
this is what i mean by recursive. it’s trying to include itself, yet there’s no other content in it. and there’s certainly no directory named [b:163mbrva]juce[/b:163mbrva] that’s distributed with the ctrlr SVN.

a full build log is available here[/url:163mbrva].

i really want to try out ctrlr; i’d like to get something working for fellow microkorg xl users. what i’m ultimately after is a working way to assign outboard controllers, such as a nanokontrol, to all the parameters normally hidden several menus deep on the keyboard. ctrlr looks like a much more friendly way to get at the guts of the synthesis engine. if only i could build it, that is. once it’s built, i can come up with a package for gentoo linux.

so, what needs to happen to make this build?

[evanjones246]

I am looking for the Linux build and am having trouble finding it. Were you able to find the Linuxbuild? Thanks.

"ungleichklang":3cofyzs6 wrote:

Where did the Linuxbuild go?? Can’t see it in the downloads for a whileMyhosting[/url:3cofyzs6][/size:3cofyzs6][/quote:3cofyzs6]

[atom]

Well the downloads page has the linux builds: the latest nightly is here always: https://sourceforge.net/projects/ctrlrv … n/download

[Author]

Posts