In the past i used always the static-Library with my plug-in-projects (it was perfect and easy), but now it seems the plugin-client is directly inside of a module, so i have to use one static library for every project - to set different plugin-specific flag.
I also could use the introjucer to include the juce-source directly in to the project, but i have no good feeling about this. Because, i use special prebuilt-commands and build rules (for assembler) in the MSVC settings, and every time when i use the introjucer to add files these - the settings will be overwritten.
And somehow i'm not sure how the different juce-locations are managed in the introjucer. When every Project-Exporter has different juce-location, how does this interact with module downloader?
But anyway what i need is a juce-Static Library Project (the good old monolithic style) with all modules (expect the plugin-client) and than include the plugin-specific files into my plugin-project. But then I am the only man on planet earth how does it this way, and run into a bunch of new problems?!
I'm a little bit frustrated, because i need the new juce module tree (not because of the modules, because of the changes), but i don't know what the best way how to proceed is. Any Ideas?
