[Xcode] management of header-files

In article <d7sj8i$1jd$04$1@news.t-online.com>,
Albert Zeyer <ich.RemoveThis@az2000.de> wrote:

 > While compiling, there are many errors because of the missing headers
 > because they are not in the subfolder "az" (include is <az/string.h> for
 > example). Another silly problem is, that cstring or other files include
 > my string.h now.

You should not be using <> to reference project-local files; use "" for
that. As far as the search path solution, the workaround would be to
use "." and not "az", since your include already contains that.<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: [Xcode] management of header-files 

Doc O'Leary wrote:

 > In article <d7sj8i$1jd$04$1@news.t-online.com>,
 > Albert Zeyer <ich.TakeThisOut@az2000.de> wrote:
 >
 >
  >>While compiling, there are many errors because of the missing headers
  >>because they are not in the subfolder "az" (include is <az/string.h> for
  >>example). Another silly problem is, that cstring or other files include
  >>my string.h now.
 >
 >
 > You should not be using <> to reference project-local files; use "" for
 > that. As far as the search path solution, the workaround would be to
 > use "." and not "az", since your include already contains that.

I am working on a framework (but by the way I don't set is as a
framework in Xcode, there it is a dynamic library), so every other
project based on this framework will also use the includes like
<az/...>. I think, it is confusing, if the includes in the framework
itself seems different. Because it is a framework, this is another
reason to put the headers into a subfolder.

See my answer to Johnny, then you can better understand my problem.

Greets
Albert<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: [Xcode] management of header-files 

In article <d7v8o5$b7m$05$1@news.t-online.com>,
Albert Zeyer <ich DeleteThis @az2000.de> wrote:

 > I am working on a framework (but by the way I don't set is as a
 > framework in Xcode, there it is a dynamic library), so every other
 > project based on this framework will also use the includes like
 > <az/...>. I think, it is confusing, if the includes in the framework
 > itself seems different. Because it is a framework, this is another
 > reason to put the headers into a subfolder.
 >
 > See my answer to Johnny, then you can better understand my problem.

It seems like your problem is that you want to do things wrong. Best of
luck with that.<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: [Xcode] management of header-files 

Doc O'Leary wrote:
 > In article <d7v8o5$b7m$05$1@news.t-online.com>,
 > Albert Zeyer <ich.TakeThisOut@az2000.de> wrote:
 >
 >
  >>I am working on a framework (but by the way I don't set is as a
  >>framework in Xcode, there it is a dynamic library), so every other
  >>project based on this framework will also use the includes like
  >><az/...>. I think, it is confusing, if the includes in the framework
  >>itself seems different. Because it is a framework, this is another
  >>reason to put the headers into a subfolder.
  >>
  >>See my answer to Johnny, then you can better understand my problem.
 >
 >
 > It seems like your problem is that you want to do things wrong. Best of
 > luck with that.

What exactly is wrong of what i want to do?
It is wrong to want the header files to be in a subfolder? I think most
projects use folders to manage the header-files and I hope every
framework has the headers in a subfolder to avoid problems with same
named files. (wxWidgets have all includes in <wx/...>)

I think you think of my management of the hole project in Xcode when you
say I want to do things wrong. I hope you understand, which type of
project this is, so how do I do this right?

Greets
Albert<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: [Xcode] management of header-files