Dear Sascha and Pierre-Yves,
Thank you
for your replies! I started with the ProjectTemplate,
which works fine without changes. But when I do a replacement, e.g. awesome
-> own I get the following cmake error:
CMake Error at
C:/MITK-2014.03.0-src/Build/CTK-src/CMake/ctkMacroSetupPlugins.cmake:144
(message):
The following plug-ins are using
invalid symbolic names:
my.ownproject.exampleapp
Call Stack (most recent call first):
CMakeLists.txt:336
(ctkMacroSetupPlugins)
Can you help me with that?
Best,
Michael
Date: Tue, 29 Jul 2014 13:28:55 +0200
From: [email protected]
To: [email protected]; [email protected]
CC: [email protected]
Subject: Re: [mitk-users] Good (folder) structure for own MITK Workbench project
Hi,
as an additional note, the project generated by the plugin
generator as well as the ProjectTemplate [1] provide a full
superbuild to first build MITK itself and then your own project.
If you need to modify MITK source code, you are best off by
cloning the MITK repo (or forking it on GitHub) and maintaining
your changes there. You can then change the superbuild of your own
project to use or MITK clone instead of the official one.
Best,
Sascha
[1] https://github.com/MITK/MITK-ProjectTemplate
On 07/29/2014 11:49 AM, Pierre-Yves Menguy wrote:
Hello,
The 'good' structure to write your own plugin is to use the
Plugin generator from MITK.
On Windows with Visual Studio, it can be found here :
"MITK-superbuild\MITK-build\bin\<Debug/Release>"
Here is a bit of documentation :
http://docs.mitk.org/nightly-qt4/NewPluginPage.html
The section "Creating a new MITK project" is the most
relevant to your question.
It'll create both the plugin folder & the englobing
project to compile it, separating it from your original MITK
folder.
Regards,
Pierre-Yves.
On 29 July 2014 11:35, Michael Smith <[email protected]>
wrote:
Dear all,
I downloaded
the MITK sources (MITK 2014.03) and performed the
MITK Superbuild and the MITK
Build as described here:
http://docs.mitk.org/nightly-qt4/HowToNewProject.html
I also
activated the Workbench and wrote an own plugin,
which works great! However,
this was only done on my computer on drive C:\. Now
I would like to check the
project into a repository where several people can
work on it. But somehow it
seems not so easy, e.g. because of the two step
build system (Superbuild and
MITK build) and because I also need to make changes
in the original Workbench
code. Is there a good (folder) structure to handle
these requirements (also
with regards to new MITK versions?).
Best
regards,
Michael
------------------------------------------------------------------------------
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms
controls.
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users
------------------------------------------------------------------------------
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls.
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users
