Well, taking X-Code as an example, they have their XML formatted project files, which Projucer is creating. Once the project is “up and running” in X-Code, it’s inevitable that there will be X-Code specific controls that will modify the project files in a way that Projucer won’t be able to handle or perform.
There aren’t that many modules so I’m just leaning towards adding them all, and trying to comment them out manually in the appropriate include. Just at first glance, looks like this would be in “Juce Library Code/JuceHeader.h”. One line comment and should be 100% handled! I’ll test this out of course.
I’m also leaning towards “copy the modules to the project” so the project can be properly checked in to version control. Projucer is pretty slick, and it’s amazing that it’s cross platform, so they designed it with this specific workflow. The copying of modules to the project seems like a minor work-around. (Normally you’d have some mechanism for external dependencies like cocoapods, and you wouldn’t check those into version control).
So my plan isn’t ideal but seems fairly easy to work around if needed. For instance, if there’s a new module or an updated module, I’ll just export a hello world and extract the dependency manually and add it to the already-in-motion X-Code project.
If there’s a better way, please LMK. Thanks.