I just found an even better way of fixing this:

Instead of creating a target for every subspec and platform, we create a single target for each platform including all subspecs. This way, jazzy only has to run one xcodebuild per platform.

At the moment, I have left in the earlier code change. Let me know, if I should remove that and have jazzy run for every platform.

Bump

Is this still active? This would be useful to me.

@joesus i think this is becalmed because none of the active maintainers are confident enough about the cocoapods internals to understand whether we really need a fix here, whether this is the right one, and what the implications are for existing users.

@johnfairh that makes sense. I'm working on a combined Swift/ObjC project and still struggling to figure out the best approach for merging the documentation. The best I can come up with is to either
a) Use sourcekitten directly for each language and then try to run jazzy directly against the files
b) Use jazzy to generate both and write a script to merge the files and use something like XSLT to combine the html.

In your opinion do you think option a will work or should I not waste time and start in on the more onerous option b?

Probably (b) -- jazzy has an all-or-nothing approach to ObjC/Swift, more discussion in #447.

This would be great to have in jazzy