On 02/06/2013 04:03 PM, Fabiola wrote:
Hi,

yes I read this page. I think my problem is related to the Inject a MITK build. Martin was quicker, so I'll try your answer to him.

This Inject a MITK build is the solution for my wrong approach of modifying the source to making visible myPlugin from mitkWorkbench?

No, using the project generated by the MITK Plugin Generator would be the "solution". Injecting an existing MITK build just avoids building MITK again for your specific project. If you didn't build MITK before, you wouldn't need to "inject" anything as the generated project's superbuild mechanism by default takes care of building MITK.

Best,
Sascha


Thx,
Fabiola

On 02/06/2013 02:51 PM, Sascha Zelzer wrote:
Hi,

did you read

http://docs.mitk.org/nightly-qt4/HowToNewProject.html ?

If yes, with which step are your struggling with, exactly?

Best,
Sascha

On 02/06/2013 02:34 PM, Fabiola wrote:
Hi Sascha,

sorry for barging in, but I saw an opportunity to find out how it should work. I know it is not nice to modify the source but I didn't find other way where can I place my plugin to the main MITK build "see it". I placed to the Plugin folder in MITK-superbuild but the mitkWorkbench didn't "see it". Should I make a *.so from my plugin and copy to MITK-superbuild/MITK-build/bin?

Can you explain me please the exact procedure where can I copy my plugin and what have to set for the mitkWorkbench notice it? I think Martin also struggling with this problem.

Thank you in advance and sorry for being so annoying,
Regards,
Fabiola

On 02/06/2013 01:21 PM, Sascha Zelzer wrote:
Hi,

Thanks Fabiola for your tips.

However, I would strongly advise against modifying the MITK sources. The MITK Plugin Generator can create a project for you. It is documented on the same page Martin cited below.

Everything in MITK is designed such that it can be used/extended by external projects without modifying the MITK source tree.

- Sascha


On 02/06/2013 12:10 PM, Fabiola wrote:
Hi Martin,

I think I know the answer for this:
The PluginList.cmake you will find in the MITK source\Plugin directory.
Step1: You copy your plugin to this directory
Step2: add your plugin name to the PluginList.cmake setting ON (e.g. org.mitk.yourplugin:ON) Step3: Rebuild your workbench in the MITK-build/bin directory from your MITK-superbuild directory.

Kind regards,
Fabiola

On 02/06/2013 11:36 AM, Martin Tatzber wrote:
Hi guys!

So I successfully built MITK under Windows 7 and Visual Studio 2008 Express. I also generated a new plugin with the MITK Plugin Generator. According to this description: http://docs.mitk.org/nightly-qt4/NewPluginPage.html#NewPluginOnly I now have to move the plugin-folder to my project and edit the Plugins.cmake

In my MITK-superbuild tree, I cannot find a Plugins.cmake. Where is the file I have to edit? Simply moving the folder to MITK-build/Plugins doesn't work.

Or do I have to create a completely new project? Can I do this with using the existing MITK build and NOT building the whole MITK once again?

Best Regards,
Martin


------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb


_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users






------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013 
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users

Reply via email to