<!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">
On 07/29/2011 01:50 PM, Steve Pieper wrote:
<blockquote
cite="mid:CA+OFd4zo9dCLFd6n2GDqJu+mDn7BzWJvNusfPCn9K2rD+zj4tg@mail.gmail.com"
type="cite">Okay - make sense to me - add me to the forming
consensus :) <br>
</blockquote>
Okay ;-)<br>
<blockquote
cite="mid:CA+OFd4zo9dCLFd6n2GDqJu+mDn7BzWJvNusfPCn9K2rD+zj4tg@mail.gmail.com"
type="cite">
<div><br>
</div>
<div>When it's all working let's offer back our changes to the
astyle team in hopes that they can be in future releases.
Dominique has me trained now to think about the packaging
implications of our changes to upstream libraries.<br>
</div>
</blockquote>
Yes, good point. We have to take packaging issues seriously. In this
case, there are no code changes to the library itself. We would need
a "FindAStyle.cmake" script and maybe a CTK_USE_SYSTEM_ASTYLE
variable to find an already installed library. If it is missing we
can conveniently build it from our commontk repo.<br>
<br>
Thanks for your suggestions,<br>
<br>
Sascha<br>
<blockquote
cite="mid:CA+OFd4zo9dCLFd6n2GDqJu+mDn7BzWJvNusfPCn9K2rD+zj4tg@mail.gmail.com"
type="cite">
<div>
<br>
</div>
<div>Best,</div>
<div>Steve</div>
<div><br>
<div class="gmail_quote">On Fri, Jul 29, 2011 at 7:35 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="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000"> Hi Steve<br>
<br>
I thought about that too, but after looking at the build
system which comes with the download-able source packages,
I was getting scared... There are three different packages
for each major OS, each again with different make files or
IDE project files. Therefore I think we will have less
troubles with our own repo which adds CMake scripts to the
library.<br>
<br>
Thanks,<br>
<font color="#888888"> Sascha</font>
<div>
<div class="h5"><br>
<br>
On 07/29/2011 01:01 PM, Steve Pieper wrote:
<blockquote type="cite">Hi Sascha -
<div><br>
</div>
<div>This sounds a nice addition. </div>
<div><br>
</div>
<div>One question; could this be done as an external
project? I think we would only need a repository
if the library requires patches in order to work
in CTK. Ideally these patches will be sent back
upstream so we can use a release version of the
library.</div>
<div><br>
</div>
<div>-Steve</div>
<div><br>
</div>
<div><br>
<br>
<div class="gmail_quote">On Fri, Jul 29, 2011 at
5:19 AM, Sascha Zelzer <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:s.zelzer@dkfz-heidelberg.de"
target="_blank">s.zelzer@dkfz-heidelberg.de</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:
0pt 0pt 0pt 0.8ex; border-left: 1px solid
rgb(204, 204, 204); padding-left: 1ex;"> Hi
guys,<br>
<br>
I would like to exercise the "getting
consensus" model for changes in commontk, as
suggested by JC. Currently, there is a small
program in CTK which allows to generate source
code for CTK plug-ins (the
ctkPluginGenerator). I'd like to add the
ArtisticStyle library as a new project to
commontk to use its code formatting
capabilities to generate nicely formatted
sources inside the ctkPluginGenerator.<br>
<br>
Any thoughts or objections?<br>
<br>
Thanks,<br>
Sascha<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>
</div>
</blockquote>
<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</body>
</html>