[Insight-users] '/' vs. '\' in includes for headers

[Bill Hoffman]

Could it be that you do not have the correct -I paths in the IDE?
CMake is doing a bunch of work for you when it creates makefiles, 
like adding -I paths to the compiler.   If this was a manual created
IDE file, and you did not give all the include directories required by ITK,
it will not be able to find the file.    It has nothing to do with the /.

-Bill


At 02:14 PM 2/7/2003 -0500, dean.inglis@on.aibn.com wrote:
>Hi Bill,
>
>I tried something simple, no GUI:
> Insight/Examples/Installation/HelloWorld.cxx
>
>cmake 1.6.2 builds the exe fine with bcc32.  The
>BCB5 IDE (build a console app) on compile I get
>[C++ Error] itkVector.h(21): E2209 Unable to open include file 'vnl/vnl_vector_ref.h'
>[C++ Error] itkVector.h(81): E2293 ) expected
>[C++ Error] itkVector.h(84): E2303 Type name expected
>[C++ Error] itkVector.h(84): E2139 Declaration missing ;
>[C++ Error] itkVector.h(87): E2303 Type name expected
>[C++ Error] itkVector.h(87): E2139 Declaration missing ;
>
>etc.  E2209 states that:
>The compiler could not find the named file.
>Possible Causes
>        The named file does not exist.
>        An #include file included itself.
>        You do not have FILES set in CONFIG.SYS on your root directory.
>
>Solutions
>        Verify that the named file exists.
>        Set FILES = 20 in CONFIG.SYS.
>
>Dean
>
>> 
>> From: Bill Hoffman <bill.hoffman@kitware.com>
>> Date: 2003/02/07 Fri PM 01:20:54 GMT-05:00
>> To: "Dean Inglis" <dean.inglis@on.aibn.com>, 
>>  "Insight Users" <insight-users@public.kitware.com>
>> Subject: Re: [Insight-users] '/' vs. '\' in includes for headers
>> 
>> I think there must be some other problem.
>> The C++ language specifies that / should work.
>> What is the error you are getting?
>> 
>> -Bill
>> 
>> 
>> At 01:04 PM 2/7/2003 -0500, Dean Inglis wrote:
>> >Hi,
>> >
>> >I am attempting to build a segmentation gui in the Borland C++ Builder
>> >environment, but the IDE/compiler objects to unix style paths:
>> >e.g. in itkVector.h : #include "vnl/vnl_vector_ref.h"
>> >
>> >any work arounds for this?
>> >
>> >Dean
>> >
>> >_______________________________________________
>> >Insight-users mailing list
>> >Insight-users@public.kitware.com
>> >http://public.kitware.com/mailman/listinfo/insight-users 
>> 
>> 
>> 
>> 
>
>_______________________________________________
>Insight-users mailing list
>Insight-users@public.kitware.com
>http://public.kitware.com/mailman/listinfo/insight-users