When building TB with "enable-calendar" on linux (I can't test other platforms at the moment), the extension is installed in "objdir/dist/bin/distribution/extension" ISO "objdir/dist/bin/extension" Thus the addon is not enabled.

From my build on Windows 7 yesterday: Lightning is copied to obj-i686-pc-mingw32\dist\bin\distribution\extensions\{e2fda1a4-762b-4020-b5ad-a41df1933103} When I start Thunderbird by calling |mach run| Lightning is installed and available. Probably because it was automatically deployed into the new profile at obj-i686-pc-mingw32\tmp\scratch_user\extensions\{e2fda1a4-762b-4020-b5ad-a41df1933103} Reading e.g. http://mike.kaply.com/2012/02/09/integrating-add-ons-into-firefox/ this seems the correct way to deploy extensions automatically for users. Maybe you are using an existing profile and therefore need to install Lightning manually?

I bet this is something about the mac os signing changes. Previously just running it would be enough, at least for development mode I think we shouldn't require any more extra steps. Its probably worth asking folks in #build about this or CC'ing someone.

Stefan, you are right. I use an existing profile. But until recently, the extension was installed into ../dist/bin/extension and showed up correctly. If I copy it there manually, this still works.

This should take care. It reverts the behavior so that the extension is installed back into dist/bin, and makes sure that the rsync for mac drops it in Contents/Resources.

Comment on attachment 8509609 [details] [diff] [review] Fix - v1 Review of attachment 8509609 [details] [diff] [review]: ----------------------------------------------------------------- I'm not great on the lightning makefile stuff, but looks correct

Great, with this patch I managed to successfully run calendar xpcshell tests for local Windows build again.

Is this patch ready for checked in?

I was just missing the checkin comment, sorry for the delay.