French
Nouvelles
Pages à mettre à jour
Documentation à mettre à jour
English
Drafts, concepts
News
Pages to update
Documentation to update
UNTRANSLATED
Différences
Cette page vous donne les différences entre la révision choisie et la version actuelle de la page.
|
en:code:howto_write_a_fmf_plugin [2012/08/16 00:02] Eric Maeker, MD [Final steps] |
en:code:howto_write_a_fmf_plugin [2013/04/09 23:04] (Version actuelle) Christian A. Reiter [Final steps] remove "plugin" |
||
|---|---|---|---|
| Ligne 45: | Ligne 45: | ||
| Under the last page, **Project Management**, it's very important that you choose **plugins.pro** as the project where to add this new subproject - otherwise it won't work. | Under the last page, **Project Management**, it's very important that you choose **plugins.pro** as the project where to add this new subproject - otherwise it won't work. | ||
| - | choose any VCS you are worknig with, we are using **git** at the main FMF repository. | + | choose any VCS you are working with, we are using **git** at the main FMF repository. |
| Then click //Finish//. | Then click //Finish//. | ||
| ===== Final steps ===== | ===== Final steps ===== | ||
| - | the wizard is not able to write a little speciality that is needed by FMF. All the common plugins live in ///plugins//, but there is also a //%application%/plugins// directory (where application means freepad, freediams etc.) with a plugins.pro file for only that application. This file is the main plugins project file for that application, but it has to reference the plugins relatively in ../../plugins. | + | The wizard is not able to write a little speciality that is needed by FMF. All the common plugins live in ///plugins//, but there is also a //%application%/plugins// directory (where //%application%// means freepad, freediams etc.) with a plugins.pro file for only that application. This file is the main plugins project file for that application, but it has to reference the plugins relatively in ../../plugins. |
| Therefore you have to open the plugins.pro file in QtCreator, and change what the wizard just wrote manually: | Therefore you have to open the plugins.pro file in QtCreator, and change what the wizard just wrote manually: | ||
| Ligne 56: | Ligne 56: | ||
| <code> | <code> | ||
| - | ../../plugins/myplugin | + | ../../plugins/myspecialplugin |
| </code> | </code> | ||
| Ligne 62: | Ligne 62: | ||
| <code> | <code> | ||
| - | myplugin | + | myspecial |
| </code> | </code> | ||
| instead. Now scroll down to the lower part, create a new section and write | instead. Now scroll down to the lower part, create a new section and write | ||
| <code> | <code> | ||
| - | myplugin.subdir = ../../plugins/myplugin | + | myspecial.subdir = ../../plugins/myplugin |
| - | myplugin.depends += core | + | myspecial.depends += core |
| - | myplugin.depends += %whatElseItDependsOn% | + | myspecial.depends += %whatElseItDependsOn% |
| </code> | </code> | ||
| Then you should have no problem compiling and running the plugin. | Then you should have no problem compiling and running the plugin. | ||
|
FreeMedForms © Eric Maeker, MD |