# How to Comply with "free" version of JUCE and Putting Out Open Source Apps?

**URL:** <https://forum.juce.com/t/how-to-comply-with-free-version-of-juce-and-putting-out-open-source-apps/20447>\
**Category:** General JUCE discussion\
**Created:** [December 31, 2016, 4:44am UTC](https://forum.juce.com/t/how-to-comply-with-free-version-of-juce-and-putting-out-open-source-apps/20447 "2016-12-31T04:44:49Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![joe-04-04](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/joe-04-04/32/2566_2.png) [@joe-04-04](https://forum.juce.com/u/joe-04-04)\
**Post date:** [December 31, 2016, 4:44am UTC](https://forum.juce.com/t/how-to-comply-with-free-version-of-juce-and-putting-out-open-source-apps/20447/1 "2016-12-31T04:44:49Z")

</div>

I’ve posted a few times here, but as I’ve said in the past, I’m a brand new JUCE user. As of right now, I’m just running the free, non-paid for version of JUCE. I plan to, at some point, switch to a full license, when I’m comfortable enough with the library and the Projucer to justify it and want to put out non-free apps, but as of now, I’m just using this free version. How does one comply with the putting out Open Sourced projects in regards to keeping it legal with JUCE’s agreement? Are we just to upload the code to our Github and make sure all users of the software know that its open-sourced? Forgive me if this seems a little silly, but this is my first forray into GUI apps and potentially releasing free products.

Thank you

---

<div class="post-metadata">

**Author:** ![Dr\_Andrew](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/dr_andrew/32/590_2.png) [@Dr\_Andrew](https://forum.juce.com/u/Dr_Andrew)\
**Post date:** [December 31, 2016, 10:07am UTC](https://forum.juce.com/t/how-to-comply-with-free-version-of-juce-and-putting-out-open-source-apps/20447/2 "2016-12-31T10:07:26Z")

</div>

> [@joe\_04\_04](#):
>
> Are we just to upload the code to our Github and make sure all users of the software know that its open-sourced?

Answer: YES.

## A brief manual:

**Getting JUCE and preparing your workplace**

Clone the fresh JUCE version (git clone [GitHub - juce-framework/JUCE: JUCE is an open-source cross-platform C++ application framework for desktop and mobile applications, including VST, VST3, AU, AUv3, LV2 and AAX audio plug-ins.](https://github.com/julianstorer/JUCE.git)). In the JUCE folder create _projects_ directory:

 ![](https://us1.discourse-cdn.com/flex026/uploads/juce/original/2X/3/308389404769a335a85d73d09ccfe839e05aaadb.png)

**Compiling Projucer**

As any cross-platform development tool JUCE has two type of projects: platform independent (\*.jucer) and platform dependent. JUCE includes _Projucer_, project and resource manager and also code editor. Projucer can create and edit platform independent projects. With so called _exporters_ Projucer generates platform dependent projects (for Windows, Linux and so on).  
Go to the _extras/Projucer/Builds_ directory of your JUCE folder. There are several folders of _Projucer_’s platform dependent projects. Compile _Projucer_ for your OS (for Linux with command _make CONFIG=Release_):

 ![](https://us1.discourse-cdn.com/flex026/uploads/juce/original/2X/7/778ed7027735f0adcee7499e08fe2d89066eccac.png)

**Build the ready JUCE project**

Load a ready JUCE project or use any in the examples folder. Replace it into the _projects_ folder.  
Launch Projucer. Push the _Open Existing Project_ button to open project file:

 ![](https://us1.discourse-cdn.com/flex026/uploads/juce/original/2X/9/907c6b7bed50d634030601ddd0b7fcc726a292be.png)

In the left side of the Projucer window there are available exporters. You can create additional one for your target OS:

 ![](https://us1.discourse-cdn.com/flex026/uploads/juce/original/2X/7/7e347de1afa5e262f0ae7c11324fa954a15692a7.png)

To generate platform dependent projects select the menu item **File - Save Project** :

 ![](https://us1.discourse-cdn.com/flex026/uploads/juce/original/2X/7/73d93b4a19f2c42c6b6fa266e1b9900d10d745cb.png)

They will be in the _Builds_ folder:

 ![](https://us1.discourse-cdn.com/flex026/uploads/juce/original/2X/f/fb8f444cbd5d040fcb82d3fa1c7b8e36c120cb2a.png)

Now you can build one of generated platform dependent projects for your OS. If you use free version of JUCE you **must** provide **license information** in your application:

 ![](https://us1.discourse-cdn.com/flex026/uploads/juce/original/2X/4/4f7b76735ea2deca1bee47a8baefa01c9b9855ce.png)

---

<div class="post-metadata">

**Author:** ![joe-04-04](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/joe-04-04/32/2566_2.png) [@joe-04-04](https://forum.juce.com/u/joe-04-04)\
**Post date:** [December 31, 2016, 11:43am UTC](https://forum.juce.com/t/how-to-comply-with-free-version-of-juce-and-putting-out-open-source-apps/20447/3 "2016-12-31T11:43:14Z")

</div>

Thank you very much @Dr_Andrew, this is extremely helpful and informative.
