<html><head><style data-externalstyle="true">
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph {
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
}
p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParagraphCxSpFirst, p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListParagraphCxSpMiddle, p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagraphCxSpLast {
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
line-height:115%;
}
</style></head><body><div data-externalstyle="false" style="font-family:Calibri,'Segoe UI',Meiryo,'Microsoft YaHei UI','Microsoft JhengHei UI','Malgun Gothic','Khmer UI','Nirmala UI',Tunga,'Lao UI',Ebrima,sans-serif;font-size:16px;"><div>Run CMake on this CMakeLists.txt file:</div><div> </div><div> <a tabindex="-1" href="https://gist.github.com/dlrdave/5172611">https://gist.github.com/dlrdave/5172611</a></div><div> </div><div>That should give you most (but not quite all) of what you need to know to link to VTK from a non-CMake based project...</div><div> </div><div> </div><div>Cheers,</div><div>David C.</div><div> </div><div> </div><div data-signatureblock="true"> </div> <div style="border-top-color: rgb(225, 225, 225); border-top-width: 1px; border-top-style: solid;"> <strong>From:</strong> Sean McBride<br> <strong>Sent:</strong> March 15, 2013 1:38 PM<br> <strong>To:</strong> Marcus D. Hanwell<br> <strong>CC:</strong> vtkusers@vtk.org<br> <strong>Subject:</strong> Re: [vtkusers] VTK 6 porting<br> </div> <div> </div>On Fri, 15 Mar 2013 13:29:19 -0400, Marcus D. Hanwell said:<br><br>>If you don't want to use CMake you will have to generate the compiler<br>>definitions yourself. You can easily build a small CMake project, get<br>>the definitions and use them. Alternatively we could document what<br>>those definitions trigger so that you could add a source file manually<br>>to your project. I added runtime warnings about abstract objects in<br>>master to make this easier to diagnose too.<br><br>Yes, I see those warnings you added... but it's not clear to me how to act on them (I haven't had the time to look deeply).<br><br>I like the idea of you documenting 'what those definitions trigger', not only to make my life easier :) but because I suspect it's fairly common that people use the resulting VTK libraries in their favourite IDEs (VS, Xcode). It's totally understandable/reasonable to require people to use CMake to *build* VTK, but once built, it's just a bunch of library files that should be usable in Xcode, VS, or automake projects... it was possible in VTK 5, and this may catch people by surprise, as I believe is what has happened here.<br><br>Cheers,<br><br>-- <br>____________________________________________________________<br>Sean McBride, B. Eng sean@rogue-research.com<br>Rogue Research www.rogue-research.com <br>Mac Software Developer Montréal, Québec, Canada<br><br><br>_______________________________________________<br>Powered by www.kitware.com<br><br>Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html<br><br>Please keep messages on-topic and check the VTK FAQ at: http://www.vtk.org/Wiki/VTK_FAQ<br><br>Follow this link to subscribe/unsubscribe:<br>http://www.vtk.org/mailman/listinfo/vtkusers<br></div></body></html>