<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=UTF-8">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META NAME="Generator" CONTENT="MS Exchange Server version 6.0.6619.12">
<TITLE>[Insight-users] Re: Installable windows ITIK programms</TITLE>
</HEAD>
<BODY dir=ltr>
<DIV>Jelle,</DIV>
<DIV> </DIV>
<DIV>I actually meant how I can make my OWN programs (which are
ITK-based) work on PC with no ITK, VS, etc.</DIV>
<DIV>I did not meant ITK itself.</DIV>
<DIV> </DIV>
<DIV>Regards, </DIV>
<DIV>Zeim</DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV><FONT size=2>-----Ursprüngliche Nachricht----- <BR><B>Von:</B>
insight-users-bounces+salah=gris.uni-tuebingen.de@itk.org im Auftrag
von jelle <BR><B>Gesendet:</B> Do 13.12.2007 16:16
<BR><B>An:</B><B>Cc:</B> <BR><B>Betreff:</B> [Insight-users] Re: Installable
windows ITIK programms<BR><BR></FONT></DIV>
<P><FONT size=2>Having a set of pre-compiled binaries for sure would lower a
threshold for<BR>starting with ITK. It sure would lower the threshold for
starting with ITK for<BR>some researchers. Speaking for myself, I wouldn't be
able to use ITK without the<BR>WrapITK project, which definitely contributes
at lowering the threshold. With<BR>binaries of examples of the ITK project (
much like a project like CGAL.org has<BR>) available, I suppose that's about
what can be done to making ITK as accesible<BR>as
possible.<BR><BR>-jelle<BR><BR>_______________________________________________<BR>Insight-users
mailing list<BR>Insight-users@itk.org<BR><A
href="http://www.itk.org/mailman/listinfo/insight-users">http://www.itk.org/mailman/listinfo/insight-users</A><BR></FONT></P></BLOCKQUOTE>
</BODY>
</HTML>