quicksilver/Firefox-qsplugin — comment on commit 2a4c8c43fd1027d0d558895f7fafecdbb13ca015
File:  line 0
By HenningJ:

> make sure they’re properly including the configuration

Well...the configuration folder should be included as a group, not as a folder (it should have the yellow folder symbol, not the blue one). The path type (in the group info) should be set to "Relative to Quicksilver Source Code". And all the files from the [configuration folder](https://github.com/quicksilver/Quicksilver/tree/master/Quicksilver/Configuration) should show and not be in red. This should already be the case for most plugins. At least the ones that compile.

It's basically what Etienne was describing (what you put in the [plugin dev reference](http://projects.skurfer.com/QuicksilverPlug-inReference.mdown#getting_started)). And what I was expanding on in the [debugging plugins section](http://projects.skurfer.com/QuicksilverPlug-inReference.mdown#debugging_plugins) step 5. If you can make your build settings "Based On" the correct things, it should all be fine.

> Then there’s the issue of updating the configuration so it will build 32/64 plug-ins. Does the whole application need to build as 32/64 for that to work?

I'm not sure. When building 32/64 bit plugins, is it enough to change the build settings of the target? Or do you need to change the build settings of the project as well? I was never really sure what the difference was between those two.