<div class="gmail_quote">On Sun, Jun 10, 2012 at 11:43 AM, Pratik Talole <span dir="ltr"><<a href="mailto:pratiktalole@gmail.com" target="_blank">pratiktalole@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
David,<br>
<br>
The existing non-ITK project, i.e. the one I am trying to link my ITK<br>
project to, is quite big. Does that mean I have redo it all over again? Isnt<br>
there a simpler way to borrow ITK functionality into an existing non-ITK<br>
project without redoing it completely?</blockquote><div><br></div><div>Nope :). Others may comment here, but as far as I think most people are concerned, ITK does not support it's use via non-cmake techniques.</div><div>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> I thought building my ITK project<br>
into a lib, and then static linking this lib to my existing non-ITK project<br>
would do the job. Is that not so?</blockquote><div><br></div><div>No, as you've seen your include path is not setup correctly. I suppose you'd have to add *every* path in the ITK source tree to your include path:</div>
<div><br></div><div>src/ITK/Modules/Core/Common</div><div>src/ITK/Modules/Core/ImageAdpators</div><div>.......</div><div>src/ITK/Modules/Filtering/*</div><div>...</div><div>src/ITK/Modules/IO/*</div><div>...</div><div><br>
</div><div>this would be an enormous list, and I don't know if it would even work.</div><div><br></div><div>David</div></div>