<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">Ok, thanks all, finally I generated VS
      projects of VTK's examples through CMake and I found what I
      searched :<br>
      <br>
      To have the os/rendering system  dependent classes created, I
      assume I must set following macro : <br>
      <i>#define vtkRenderingCore_AUTOINIT
4(vtkInteractionStyle,vtkRenderingFreeType,vtkRenderingFreeTypeOpenGL,vtkRenderingOpenGL)</i><br>
      <br>
      or add in my preprocessor definitions a reference to a file,
      containing the previous macro, like this :<br>
      <i>vtkRenderingCore_INCLUDE="vtkRenderingCore_AUTOINIT_vtkInteractionStyle_vtkRenderingFreeType_vtkRenderingFreeTypeOpenGL_vtkRenderingOpenGL.h"<br>
        <br>
      </i>Cannot be these parameters set in VTK build, to be included in
      VTK resulting dll ?<br>
      <br>
      Else I must add these definitions in all my VTK dependent projects
      which is not very elegant ...<br>
      <i><br>
        <br>
        <br>
      </i>Frédéric S.<i><br>
        <br>
        <br>
      </i>Le 15/03/2013 20:54, David Cole a écrit :<br>
    </div>
    <blockquote cite="mid:20130315200034.BF20C61F73@public.kitware.com"
      type="cite">
      <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>
      <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 moz-do-not-send="true" 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> <a class="moz-txt-link-abbreviated" href="mailto:vtkusers@vtk.org">vtkusers@vtk.org</a><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>
        &gt;If you don't want to use CMake you will have to generate the
        compiler<br>
        &gt;definitions yourself. You can easily build a small CMake
        project, get<br>
        &gt;the definitions and use them. Alternatively we could
        document what<br>
        &gt;those definitions trigger so that you could add a source
        file manually<br>
        &gt;to your project. I added runtime warnings about abstract
        objects in<br>
        &gt;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                 <a class="moz-txt-link-abbreviated" href="mailto:sean@rogue-research.com">sean@rogue-research.com</a><br>
        Rogue Research                        <a class="moz-txt-link-abbreviated" href="http://www.rogue-research.com">www.rogue-research.com</a> <br>
        Mac Software Developer              Montréal, Québec, Canada<br>
        <br>
        <br>
        _______________________________________________<br>
        Powered by <a class="moz-txt-link-abbreviated" href="http://www.kitware.com">www.kitware.com</a><br>
        <br>
        Visit other Kitware open-source projects at
        <a class="moz-txt-link-freetext" href="http://www.kitware.com/opensource/opensource.html">http://www.kitware.com/opensource/opensource.html</a><br>
        <br>
        Please keep messages on-topic and check the VTK FAQ at:
        <a class="moz-txt-link-freetext" href="http://www.vtk.org/Wiki/VTK_FAQ">http://www.vtk.org/Wiki/VTK_FAQ</a><br>
        <br>
        Follow this link to subscribe/unsubscribe:<br>
        <a class="moz-txt-link-freetext" href="http://www.vtk.org/mailman/listinfo/vtkusers">http://www.vtk.org/mailman/listinfo/vtkusers</a><br>
      </div>
    </blockquote>
    <br>
  </body>
</html>