[ITK] ITK headers included using angle brackets

Francois Budin francois.budin at kitware.com
Thu Feb 2 11:00:04 EST 2017


Thanks for sharing the solution. That might help other people having the
same issue.

Francois

On Thu, Feb 2, 2017 at 10:53 AM, Fijoy Vadakkumpadan <tofijoy at gmail.com>
wrote:

> Hi Francios,
>
> I was able to resolve this problem as I found out about an option to that
> different compiler (Lattice C compiler), which made it search for the
> include files in the local directory also.
>
> Thanks for your reply.
>
> --Fijoy
>
> On Wed, Feb 1, 2017 at 11:00 AM, Francois Budin <
> francois.budin at kitware.com> wrote:
>
>> Hello Fijoy,
>>
>> Including file using double quotes or angle brackets should not create an
>> issue (although the behavior is implementation-defined). Can you give more
>> information about the "different compiler" you are using?
>>
>> Francois
>>
>> On Tue, Jan 31, 2017 at 12:41 PM, Fijoy Vadakkumpadan <tofijoy at gmail.com>
>> wrote:
>>
>>> Hello,
>>>
>>> I built ITK 4.10.0 using CMake & Visual Studio Express 2013 on Windows,
>>> and am running into an issue with header files. In the header files that
>>> are generated, some of the ITK-specific header files are included using
>>> angle brackets. For example vcl_compiler.h contains "#include
>>> <vcl_config_manual.h>". This is causing an issue when I'm trying to link to
>>> the ITK libraries using a different compiler, which looks for these
>>> ITK-specific header files in the system path because of the angle brackets.
>>>
>>> Is there an option in CMake to make the #includes use quotes instead of
>>> angle brackets for ITK-specific header files?
>>>
>>> Thank you,
>>> --Fijoy
>>>
>>> _______________________________________________
>>> Community mailing list
>>> Community at itk.org
>>> http://public.kitware.com/mailman/listinfo/community
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/community/attachments/20170202/280da0b9/attachment.html>


More information about the Community mailing list