Greetings, As previously mentioned, the unwind contents are going to be moved today. Im working on this now. If you could please hold off any commits to the Unwind part of things, it would be greatly appreciated. See you on the new layout! -- Saleem Abdulrasool compnerd (at) compnerd (dot) org -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150424/0848b094/attachment.html>
On Fri, Apr 24, 2015 at 12:14 PM, Saleem Abdulrasool <compnerd at compnerd.org> wrote:> Greetings, > > As previously mentioned, the unwind contents are going to be moved today. > Im working on this now. If you could please hold off any commits to the > Unwind part of things, it would be greatly appreciated. > > See you on the new layout! >Okay, the source and headers have been moved over. For now, libc++abi refers to the peer libunwind directory. This is a temporary thing until we get cmake properly sorted out and reorganised. However, this permits us to continue development in the mean time with a minor disruption (once for re-running cmake now and once later when we get the new build setup). Thanks for bearing with this. Until a git mirror is setup, we will need to use subversion (for those running subversion, I guess this is less of a concern). You can do the following to get libunwind back (if you are building with LIBCXXABI_USE_LLVM_UNWINDER=YES). cd ${LLVM_SOURCE_DIR}/projects svn co https://llvm.org/svn/llvm-project/libunwind/trunk libunwind --> Saleem Abdulrasool > compnerd (at) compnerd (dot) org >-- Saleem Abdulrasool compnerd (at) compnerd (dot) org -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150424/14cb63aa/attachment.html>
On 24 April 2015 at 21:32, Saleem Abdulrasool <compnerd at compnerd.org> wrote:> Okay, the source and headers have been moved over. For now, libc++abi > refers to the peer libunwind directory. This is a temporary thing until we > get cmake properly sorted out and reorganised. However, this permits us to > continue development in the mean time with a minor disruption (once for > re-running cmake now and once later when we get the new build setup).Thanks Saleem! This is a much better temporary solution than having two repositories. :) My libc++ buildbot is, obviously, red, but I won't change it, so that you can check when your CMake changes made it work again: http://lab.llvm.org:8011/builders/libcxx-libcxxabi-arm-linux Once you're done, I'll have to change the Clang driver to import libunwind with compiler-rt and then add libunwind to our compiler-rt buildbots. I'll wait until you're finished. cheers, --renato