EricWF added a comment. In http://reviews.llvm.org/D11963#227933, @jroelofs wrote:
> In http://reviews.llvm.org/D11963#227444, @EricWF wrote: > > > I also just realized that this change will currently likely play havoc with > > how libc++ and libc++abi build together. In order to build libc++ and > > libc++abi together we would need to > > > > 1. Configure libc++ pointing to the libc++abi headers in order to generate > > the __config_site file. > > 2. Configure libc++abi pointing it to the libc++ build directory for the > > headers. > > 3. build libc++abi > > 4. build libc++ > > > > I'm not quite sure how this would work for an in-tree build. > > > This patch, combined with http://reviews.llvm.org/D11964, works the way you > describe. Wouldn't it still be a mess if you build both libc++ and libc++abi out-of-tree? The user would have to be aware of these weird requirements. http://reviews.llvm.org/D11963 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
