diff --git a/docs/JUCE readme.html b/docs/JUCE readme.html index 8a669a64c8..87f643eb11 100644 --- a/docs/JUCE readme.html +++ b/docs/JUCE readme.html @@ -65,13 +65,22 @@ operating systems and compilers.
Inside the juce folder is a demo application that shows off a few of Juce's features.
The juce/extras/juce demo/build folder contains projects and workspaces for the various platforms and compilers.
A recent new feature is that Juce can be used as a monolithic C++ file, instead of a statically linked
+library. This means that you can write a juce application without actually needing to build the
+library beforehand, but instead by just adding juce_amalgamated.cpp to the project, and including
+juce_amalagamated.h instead of juce.h. The demo apps are designed using this approach, because it means
+there's less setting-up required for a new user to do before getting stuck-in, but some compilers
+and debuggers can struggle with the huge files involved, so you may prefer to build
+your project in the traditional way, using it as a separate library.
The quickest way to get started is to try building the demo application - there's a Visual Studio
-soluion in juce/extras/juce demo/build/win32_vc8/jucedemo.sln which contains both the juce
-library project and the demo application project.
juce/extras/juce demo/build/win32_vc8/jucedemo.sln.
This should build and run with no extra set-up needed in Visual Studio. (If you're using VCExpress Edition see below for the few extra steps needed).
The only thing to check if you're unfamiliar with Visual Studio is that the jucedemo
@@ -97,6 +106,14 @@ Generation options panel. In Visual Studio, it's in the project properties.
JUCEApplication class to find out how to create the application launch code.
+
Alternatively, you can use the amalgamated form of Juce (see note above). To do this,
+all need to do is to add juce_amalagamated.cpp to your project, and include
+juce_amalagamated.h instead of juce.h. This pulls the entire library into
+your project without needing to link to it separately, so you can skip the steps above that involve
+setting up the link paths, etc. Most of the demo apps are written using the amalgamated version,
+so refer to these for an example of how to do this.
Although VCExpress is basically the same thing as Visual Studio 2005, it doesn't come
@@ -192,21 +209,35 @@ also add Juce to your target's "Direct Dependency" list (show information for th
"general" tab).
Alternative ways of linking to juce would be to add the libjuce.a or libjucedebug.a library to
your "External Frameworks and Libraries" list, or to add switch to the linker's command-line of either "-ljuce"
or "-ljucedebug".
-
Cocoa.framework +CoreFoundation.framework +CoreServices.framework +ApplicationServices.framework Carbon.framework IOKit.framework +QuickTime.framework CoreAudio.framework CoreMIDI.framework -QuickTime.framework +AudioUnit.framework OpenGL.framework -AGL.framework+AGL.framework +WebKit.framework +DiscRecording.framework + In future there may be other frameworks that you'll need to link with to support new JUCE features. (It should be pretty obvious from the link-time error when one of these is missing).
If all this seems too complicated, you can use the amalgamated form of Juce (see earlier note). To do this,
+all need to do is to add juce_amalagamated.cpp to your project, and include
+juce_amalagamated.h instead of juce.h. This pulls the entire library into
+your project without needing to link to it separately, so you can skip the steps above that involve
+compiling the library, setting up the link paths, etc. Most of the demo apps are written using the amalgamated version,
+so refer to these for an example of how to do this.
juce/build/win32/codeblocks/juce.cbp