Apologies if I am misunderstanding the question and that you are trying to so something more complicated than I think, but in Visual Studio at least, this is very easy. Suppose I am creating a multimedia library project with some C++ wrapper classes of my own that call down to the JUCE library to implement the audio and video functionality. Then, as well as my own C++ code added to the VS project, I add a cpp file for each JUCE module I need to make use of.
e.g. To add audio devices I add my own c++ file which I call "include_juce_audio_devices.cpp"
This contains the statement: #include “modules\juce_audio_devices\juce_audio_devices.cpp”
In my VS project properties I have include paths set up so that the JUCE modules directory can be found and I also have various #defines added to the preprocessor settings, such as:
JUCE_GLOBAL_MODULE_SETTINGS_INCLUDED=1;_ALLOW_KEYWORD_MACROS;JUCE_USE_CAMERA; Use whatever is appropriate for your project.
This both builds and runs fine for me. I have NEVER had to use Projucer for JUCE on Windows. What I would really like to do is have a similar convenience on Android, because a Projucer-created Android project seems to use the experimental Gradle plugin, whereas if I create a C++ project directly in the latest Android Studio it does not use that plugin. I find the Android Studio created C++ projects much easier to work with. My question would be can I do the same thing for Android Studio as I do for Visual Studio, adding my own cpp files that #include from the JUCE modules? I assume I need to tell JUCE it is on Android with a preprocessor setting ( ANDROID_CPP?) but is that all, or am I going to get bogged down in some complicated build system Java requirements nightmare?