Building EdoController on Mac

[dejf_mk]

Hello,
First I would like to say that the ctrlrs I have tested so far seem quite promising! Good work ” title=”Smile” />

But now I am trying to design a ctrlr and I am running in to lots of problems. I am running a MacPro, Snow Leopard 10.6.5 and using XCode 3.2.4.

I have been following the screencast from the how to guide thread and the document on the Googlecode wiki. I’ve tried this with the sourceforge ctrlrv4/Stable and older googlecode ctrlr and the same problem.

So far I compiled Jucer, created a simple GUI layout, imported this in to an XCode project. That all seems ok. But when I follow the instructions at googlecode and I come to compile EdoController I get loads of Juce related errors. I guess this is because my path is different to yours, but how can I configure the XCode project so that it sees my path? I added my juce path to the EdoController XCode project’s "header search path" but still it can’t find the juce amalgamation path!

Apologies in advance if that’s obvious but I just can’t past this point!

Thanks in advance

David

[atom]

the amalgamation path is the juce main directory, look for file juce_amalgamated.h and .cpp

[dejf_mk]

Hi Atom,
Thanks for the reply. Sorry in advance if this is newbie stuff, I’m new to XCode and Juce!!

"atom":1zg3wu7l wrote:

the amalgamation path is the juce main directory, look for file juce_amalgamated.h and .cpp[/quote:1zg3wu7l]

Sure, I can see the amalgamated path no problem, what I’m having problems with is pointing the XCode project at that directory. Should I be editing the JuceLibraryCodeX.mm files to have the correct path?

My most recent attempt I have actually hardcoded all of the paths that were giving me errors (I know this is not a recommended solution!). Once I did that, I get errors like:

[code:1zg3wu7l]
/Users/dejf/Documents/Programming/ctrlrv4/Stable/EdoController/Build/Mac/../../EdoModulatorManager/Lua/EdoModulatorManagerLuaWrapper.cpp:155:0 /Users/dejf/Documents/Programming/ctrlrv4/Stable/EdoController/Build/Mac/../../EdoModulatorManager/Lua/EdoModulatorManagerLuaWrapper.cpp:155: error: no matching function for call to ‘MidiMessageEx::MidiMessageEx(juce::MemoryBlock)’

../../Primitives/MidiMessageEx.h:39:0 ../../Primitives/MidiMessageEx.h:39: note: candidates are: MidiMessageEx::MidiMessageEx()
[/code:1zg3wu7l]

I guess my question is how to make sure that the juce amalgamated gets pulled properly into the XCode project. For example, in the JuceLibraryCode1.mm file in the XCode project there is:
[quote:1zg3wu7l]
If you want to change the method by which Juce is linked into your app, use the
Jucer to change it, rather than trying to edit this file directly.
[/quote:1zg3wu7l]

Is this relevant?

Thanks in advance

David

[atom]

well it looks like i missed a constructor for MidiMessageEx, but i’m sure it was there
try changing line 32 of MidiMessageEx from
[code:2la7xo08]
MidiMessageEx(MemoryBlock &dataToScan);
[/code:2la7xo08]
to
[code:2la7xo08]
MidiMessageEx(const MemoryBlock dataToScan);
[/code:2la7xo08]

it should take a copy of the data anyway, not reference it. i don’t know why didn’t that pop out for me.

Also i don’t recommend playing with that code anymore, i’m doing Ctrlr v5 and to do new Ctrlrs you won’t need any C++ code anymore, it’s just a recommendation since you might want to play with that code anyway just for fun.

[dejf_mk]

"atom":33p6zjyx wrote:

well it looks like i missed a constructor for MidiMessageEx, but i’m sure it was there
try changing line 32 of MidiMessageEx from
[code:33p6zjyx]
MidiMessageEx(MemoryBlock &dataToScan);
[/code:33p6zjyx]
to
[code:33p6zjyx]
MidiMessageEx(const MemoryBlock dataToScan);
[/code:33p6zjyx]

it should take a copy of the data anyway, not reference it. i don’t know why didn’t that pop out for me.
[/quote:33p6zjyx]
Aha, ok that makes sense. Thanks.

"atom":33p6zjyx wrote:

Also i don’t recommend playing with that code anymore, i’m doing Ctrlr v5 and to do new Ctrlrs you won’t need any C++ code anymore, it’s just a recommendation since you might want to play with that code anyway just for fun.[/quote:33p6zjyx]
Yes I noticed this in the News area of the forum. Will we continue to use the Jucer and the Ctrlr template editor to design a GUI for a Ctrlr? If yes, then I will work on that in preparation of v5. I am not a big fan of XCode ” title=”Smile” />

Is Ctrlr v5 in svn yet? I know it is early, just wondering….

David

[atom]

yes v5 is in the svn under Beta, and no no need for Jucer or any other external app to create UIs, a JUCER like interface is in Ctrlr v5 already.

[Author]

Posts