quicksilver/elements.support.mail-qsplugin — pull request #1 by skurfer (2012-07-17 20:39:32+00:00)
Title: updates and fixes

This includes the usual updates for 64-bit, of course. It should also address:

* quicksilver/Quicksilver#816
* quicksilver/Quicksilver#922

I didn’t see quicksilver/Quicksilver#907 until just now, but I could add another commit if you think it’s worth it.

I’ve updated the included README to explain how to get MailCore in the right place. I don’t want to spoil the ending, but it’s not going to build. :-) I followed [the instructions](http://libmailcore.com/#macadding) for adding MailCore to the project, but they’ve changed just in the last couple of days. It used to include a step where you’d add `../Support/MailCore/include` to the target’s Header Search Paths (which you’ll see I’ve done), but it no longer includes that step and no longer creates that directory. As a result, you’ll get errors when importing `MailCore.h`. If someone can figure it out, please let me know and I’ll update the README.

You’ll see I’ve also added `../Support/MailCore/libetpan/build-mac/include` to the Header Search Paths. I had to do this from the plug-in’s project to get it to build, though it wasn’t necessary if building MailCore directly. I suspect the Header Search Paths can be cleared entirely once we figure out how to get it to build without `../Support/MailCore/include`.

And finally, I’m not settled on the location of the MailCore source (`../Support`), so we can certainly discuss that. Why not add it as a submodule?

* It’s going to be used by the Mail plug-in too, so I wanted to put to somewhere they could both use it. But since the Mail plug-in requires this one anyway, maybe that’s not a good reason.
* It contains submodules itself. I wasn’t sure if `git submodule update` would work recursively.

In theory, having the MailCore framework bundled with this plug-in should allow the Mail plug-in to use it too (without including it there as well), but so far that hasn’t worked out.