# xCode/Juce doesn't display anything when running basic Juce app

**URL:** <https://forum.juce.com/t/xcode-juce-doesnt-display-anything-when-running-basic-juce-app/31572>\
**Category:** The Projucer\
**Created:** [February 1, 2019, 5:39pm UTC](https://forum.juce.com/t/xcode-juce-doesnt-display-anything-when-running-basic-juce-app/31572 "2019-02-01T17:39:16Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![netien](https://avatars.discourse-cdn.com/v4/letter/n/53a042/32.png) [@netien](https://forum.juce.com/u/netien)\
**Post date:** [February 1, 2019, 5:39pm UTC](https://forum.juce.com/t/xcode-juce-doesnt-display-anything-when-running-basic-juce-app/31572/1 "2019-02-01T17:39:16Z")

</div>

Hello everyone

I’m new to juce but not to C++. I’m using the Prodjucer version 5.4.1 with XCode version 8.2.1.

I’m following the JUCE tutorial and all goes fine and well until I come by the part where you display the first GUI app (which is just a Volume slider that does nothing). like shown here : [https://docs.juce.com/master/tutorial\_code\_basic\_plugin.html](https://docs.juce.com/master/tutorial_code_basic_plugin.html)

I double-triple checked that my classes and methods are exactly like they are supposed to be. I didn’t forgot the addAndMakeVisible (&midiVolume).

I click on the Compile & run button, all goes well, it compiles all the files and then…  
Nothing.  
No window are displayed.

Anyone could explain what the \*\*\*\* (fill the blank with any 4-letter word of your choice) is happening ?

Thanks a lot !

---

<div class="post-metadata">

**Author:** ![cpr2323](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/cpr2323/32/18682_2.png) [@cpr2323](https://forum.juce.com/u/cpr2323)\
**Post date:** [February 1, 2019, 5:46pm UTC](https://forum.juce.com/t/xcode-juce-doesnt-display-anything-when-running-basic-juce-app/31572/2 "2019-02-01T17:46:02Z")

</div>

The tutorial you linked is for creating a plugin, not a stand alone app. You can’t ‘run’ a plugin, it has to be loaded into an application which loads plugins (Ableton, Logic, etc). You can see that implied here at the end `Run the plug-in in the host environment`

This is a tutorial in creating a stand alone app.  
[https://docs.juce.com/master/tutorial\_main\_component.html](https://docs.juce.com/master/tutorial_main_component.html)

---

<div class="post-metadata">

**Author:** ![netien](https://avatars.discourse-cdn.com/v4/letter/n/53a042/32.png) [@netien](https://forum.juce.com/u/netien)\
**Post date:** [February 1, 2019, 7:31pm UTC](https://forum.juce.com/t/xcode-juce-doesnt-display-anything-when-running-basic-juce-app/31572/3 "2019-02-01T19:31:17Z")

</div>

Ok, that makes sense. Thanks a lot.

Now if I want to make a plugin for DAWs that also works as a stand-alone app, like a lot of plug-ins are, it means that I have to code it as a stand-alone project and then re code it as a plug-in project ?

---

<div class="post-metadata">

**Author:** ![cpr2323](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/cpr2323/32/18682_2.png) [@cpr2323](https://forum.juce.com/u/cpr2323)\
**Post date:** [February 1, 2019, 8:04pm UTC](https://forum.juce.com/t/xcode-juce-doesnt-display-anything-when-running-basic-juce-app/31572/4 "2019-02-01T20:04:03Z")

</div>

You can easily share code between projects. I’ve not done plugin work for a bit, but as it turns out, there is a mode for the plugin project that allows you to generate a stand alone (executable) version. In Visual Studio I have three projects I can select to build from  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/juce/original/2X/1/1c76356bfbdd1c58769c963e52244adc5f4705aa.png)

---

<div class="post-metadata">

**Author:** ![matkatmusic](https://avatars.discourse-cdn.com/v4/letter/m/dfb087/32.png) [@matkatmusic](https://forum.juce.com/u/matkatmusic)\
**Post date:** [February 3, 2019, 4:34am UTC](https://forum.juce.com/t/xcode-juce-doesnt-display-anything-when-running-basic-juce-app/31572/5 "2019-02-03T04:34:49Z")

</div>

update your version of xcode while you’re at it. we’re up to xcode 10.1 now, which is pretty solid with the Legacy build system enabled.
