[vtkusers] VTK + Qt + Intel C++ Compiler

[Jim]

Dave and Mathieu,
   
  Thank you very much. I will run a test myself and post my findings here.
  

Dave Partyka <dave.partyka at kitware.com> wrote:
  Sure thing!

  On Tue, Jan 13, 2009 at 11:41 AM, Mathieu Malaterre <mathieu.malaterre at gmail.com> wrote:
  Oh ok. So you could maybe fix
VTK/CMake/vtkDetermineCompilerFlags.cmake to accomodate for intel
compiler:

...
IF(CMAKE_COMPILER_2005)
 ADD_DEFINITIONS(-D_CRT_SECURE_NO_DEPRECATE -D_CRT_NONSTDC_NO_DEPRECATE)
 ADD_DEFINITIONS(-D_SCL_SECURE_NO_DEPRECATE)
ENDIF(CMAKE_COMPILER_2005)
...

This should get you rid of tons of warnings.

Thanks,
    
  
On Tue, Jan 13, 2009 at 5:38 PM, Dave Partyka <dave.partyka at kitware.com> wrote:
> Yeah thats how the Intel compiler works (at least on Windows). It requires
> either Visual Studio or the Windows SDK and sets itself up to act as a
> replacement for the compiler executable "cl.exe" and then makes use of all
> of the MS headerfiles and probably the libraries too.
>
> On Tue, Jan 13, 2009 at 11:14 AM, Mathieu Malaterre
> <mathieu.malaterre at gmail.com> wrote:
>>
>> Dave,
>>
>>  This line looks suspicious:
>>
>> ...
>> C:\Kitware\VTK\Utilities\kwsys\ProcessFwd9x.c(91): warning #1786:
>> function "sscanf" (declared at line 324 of "C:\Program Files
>> (x86)\Microsoft Visual Studio 9.0\VC\INCLUDE\stdio.h") was declared
>> "deprecated ("This function or variable may be unsafe. Consider using
>> sscanf_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS.
>> See online help for details.") "
>> ...
>>
>> why would intel compiler use M$ stdio.h file ? Did you set INCLUDE env
>> var to M$ stuff on purpose ?
>>
>> Thanks
>>
>>
>> On Tue, Jan 13, 2009 at 4:26 PM, Dave Partyka <dave.partyka at kitware.com>
>> wrote:
>> > Hi Jim,
>> > Here is the dashboard I ran last night building VTK with nmake (using
>> > the
>> > Intel Compiler). It has plenty of warnings but does build successfully.
>> > http://www.cdash.org/CDash/buildSummary.php?buildid=249449
>> > To do this you run cmake from the intel command prompt. From there when
>> > you're prompted to pick a generator select NMake Makefiles and then
>> > select
>> > "Compiler Setup". In there set C and C++ compilers to point to the
>> > location
>> > of icl.exe. You can also use the visual studio IDE, in which you just
>> > hit
>> > the Intel C++ button on the toolbar.
>> > On Mon, Jan 12, 2009 at 4:16 PM, Dave Partyka <dave.partyka at kitware.com>
>> > wrote:
>> >>
>> >> Hi Jim,
>> >> I have recently been experimenting with building VTK with the latest
>> >> Intel
>> >> C++ compiler. I will run an experimental dashboard tonight and send you
>> >> a
>> >> link to it. As I recall it had a ton of warnings in it that needed to
>> >> be
>> >> cleaned up. I wouldn't be surprised that in the near future we'll have
>> >> a
>> >> regular nightly dashboard using that compiler.
>> >>
>> >> On Mon, Jan 12, 2009 at 3:51 PM, Jim <jiksed at yahoo.com> wrote:
>> >>>
>> >>> Dear vtkusers,
>> >>>
>> >>> Will VTK + Qt + Intel C++ a good combination for numerical modeling
>> >>> and
>> >>> data visualizaton on Win32 and Win64? I don't see any testing data on
>> >>> VTK
>> >>> Quality Dashboard.
>> >>>
>> >>> Thank you.
>> >>> Jim
>> >>>
>> >>> _______________________________________________
>> >>> This is the private VTK discussion list.
>> >>> Please keep messages on-topic. Check the FAQ at:
>> >>> http://www.vtk.org/Wiki/VTK_FAQ
>> >>> Follow this link to subscribe/unsubscribe:
>> >>> http://www.vtk.org/mailman/listinfo/vtkusers
>> >>>
>> >>
>> >
>> >
>> > _______________________________________________
>> > This is the private VTK discussion list.
>> > Please keep messages on-topic. Check the FAQ at:
>> > http://www.vtk.org/Wiki/VTK_FAQ
>> > Follow this link to subscribe/unsubscribe:
>> > http://www.vtk.org/mailman/listinfo/vtkusers
>> >
>> >
>>
>>
>>
>> --
>> Mathieu
>
>





--
Mathieu




       
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.vtk.org/pipermail/vtkusers/attachments/20090114/ee5e4d32/attachment.htm>