<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Good to hear :-)<br>
<br>
The example project is a good idea. I already created one for testing
the changes:<br>
<br>
<a class="moz-txt-link-freetext" href="https://github.com/saschazelzer/CTKPluginProject">https://github.com/saschazelzer/CTKPluginProject</a><br>
<br>
I could polish it (add some more useful information) and move it to the
commontk organization.<br>
<br>
Thanks,<br>
<br>
Sascha<br>
<br>
On 11/24/2010 07:42 PM, Jean-Christophe Fillion-Robin wrote:
<blockquote
cite="mid:AANLkTimFQzHYB5bNjqtti5A6rMK3ZKA9nv7ajo=OQRz7@mail.gmail.com"
type="cite">Seems good to me. <br>
I compiled the branch successfully and build Slicer against it without
problem.<br>
<br>
Would be great if we could have very simple project, for example <a
moz-do-not-send="true"
href="http://github.com/commontk/CTKPluginExample">github.com/commontk/CTKPluginExample</a>,
illustrating how a plugin could be developed.<br>
<br>
Thks<br>
Jc<br>
<br>
<div class="gmail_quote">On Tue, Nov 23, 2010 at 4:26 AM, Sascha
Zelzer <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:s.zelzer@dkfz-heidelberg.de">s.zelzer@dkfz-heidelberg.de</a>></span>
wrote:<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi
Folks,<br>
<br>
I would like to merge yet another couple of changes to the CTK
buildsystem. They enable support for writing CTK plug-ins in external
projects, which use CTK as a toolkit. The changes also improve the
buildsystem for CTK itself. Here are the details:<br>
<br>
Branch: <a moz-do-not-send="true"
href="https://github.com/saschazelzer/CTK/commits/buildsystem"
target="_blank">https://github.com/saschazelzer/CTK/commits/buildsystem</a><br>
Relevant commit: <a moz-do-not-send="true"
href="https://github.com/saschazelzer/CTK/commit/9a6381c9074d2a7a77967da50e2a4db237435dee"
target="_blank">https://github.com/saschazelzer/CTK/commit/9a6381c9074d2a7a77967da50e2a4db237435dee</a><br>
<br>
Overview of changes:<br>
<br>
- Setup include directories inside a function (special support for
non-CTK plug-ins added)<br>
- Use the above function in the ctkMacroBuild* macros<br>
- Added a check if plug-in dependencies exist at all (known_targets
variable in ctkMacroValidateBuildOptions.cmake)<br>
- Smalle changes to ctkMacroValidateBuildOptions.cmake to generalize
it so it is usable outside of CTK<br>
- Added a function (ctkFunctionSetupExternalPlugins.cmake) for easy
configuration of plug-ins in external projects<br>
- Use the EXPORT CMake command and include the exports file in
CTKConfig.cmake<br>
<br>
The last item in the list might be the one with the biggest overall
influence, since it changes the way how CTK libraries are linked from
inside external projects (i.e. Slicer).<br>
<br>
Thanks for your feedback,<br>
<br>
Sascha<br>
<br>
_______________________________________________<br>
Ctk-developers mailing list<br>
<a moz-do-not-send="true" href="mailto:Ctk-developers@commontk.org"
target="_blank">Ctk-developers@commontk.org</a><br>
<a moz-do-not-send="true"
href="http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers"
target="_blank">http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers</a><br>
</blockquote>
</div>
<br>
<br clear="all">
<br>
-- <br>
Phone: 1-518-836-2174<br>
Ext: 304<br>
</blockquote>
<br>
</body>
</html>