OSDev.org

I am thinking as most of my development depend on clang (LOVE it's beautiful debug output and fix-it) so I am thinking is using LLVM userland libraries a good idea? (It is known to be good on OS X, as Apple dropped libstdc++ on OS X 10.9 and symlinked it to libc++)

Components include:
* newlib libc (LLVM does not have a libc though)
* libc++rt C++ runtime library,
* libc++ C++ standard library (C++11 feature complete)

Also, since my init is in Objective-C, those are required too:
* libobjc2+libGNUObjCRuntime (GNUstep Objective-C 2.0 runtime, as init requires it)
* libgnustep-base (GNUstep's clone of Apple's Foundation Kit, as init requires it)

Didn't get your question.

If you want to use those libraries, use them. If you don't then don't.

You will still need to do a bit of porting to your platform.

I'm using libc++ myself, although I have disabled all iostreams functionality (not necessary in the kernel and needs some porting before it can be used).

In terms of design or implementation ?

technix wrote:(It is known to be good on OS X, as Apple dropped libstdc++ on OS X 10.9 and symlinked it to libc++)

No they didn't. They have different ABIs. Doing that would break every C++ app not compiled against libc++.

libc++ is just now the default (and by far most complete, because Mac OS X will forever be stuck at libstdc++ 4.2)