0

I've found std lib header cstdio (libcxx implementation line 100) to include stdio.h. So now clang (using via libclang - C API) diagnostics reports that stdio.h is not found (in some device specific environment which i'm configuring). It seems to be include paths problem (-I) and i'm just trying to understand dependencies and the reason and build correct includes path.

4ntoine
  • 19,816
  • 21
  • 96
  • 220
  • 3
    The `` header file is just a wrapper into the standard `std` namespace of the `` header file. Exactly *how* that wrapping is done doesn't matter, but it's easy to just `#include ` inside instead of rewriting the whole file. – Some programmer dude Aug 18 '14 at 06:22
  • ok, that's clear. Does it mean libcxx requires libc installed on the device (afaik stdio.h is libc header) and including libc include paths for the app that uses libc++? – 4ntoine Aug 18 '14 at 06:26
  • Much of the functionality of C has to be available in C++. Exactly how that is done is implementation-specific, but, again, why rewrite when the support is already there in the C library? – Some programmer dude Aug 18 '14 at 06:29
  • ok, now i understand libcxx is not standalone and libc headers should be available to make libcxx working too, – 4ntoine Aug 18 '14 at 06:49
  • That depends on which part of libcxx you want, of course - ``, `` and so on typically don't depend on libc. – Tom Aug 18 '14 at 07:36

0 Answers0