Did you get a chance to test this today? On Fri, Mar 25, 2016 at 9:32 AM Greg Clayton <clayb...@gmail.com> wrote:
> Will do. > > On Mar 24, 2016, at 3:30 PM, Zachary Turner <ztur...@google.com> wrote: > > > > Is there any way you could try it out for me? It still doesn't build > successfully from the IDE with those steps. > > > > The patch should apply cleanly at tip. Later this week I can try to > nuke my whole lldb directory and start over with a clean repo. > > > > On Thu, Mar 24, 2016 at 3:26 PM Greg Clayton <clayb...@gmail.com> wrote: > > You might need to set your workspace settings for the lldb.xcworkspace > as follows: > > > > File -> Workspace Settings... > > > > > > Derived Data: Workspace-relative Location > > > > and use the value "build" for it > > > > Then click the "Advanced..." button and select "Legacy". > > > > The test suite automatically looks in the lldb root directory's build > folder for any LLDB stuff. If you built with "xcodebuild -configuration > Debug" then there will be files. The LLDB should be in: > > > > $(lldb)/build/Debug/lldb > > $(lldb)/build/Debug/LLDB.framework > > > > where $(lldb) is your LLDB root folder... > > > > > > > > > > > > > On Mar 24, 2016, at 3:19 PM, Zachary Turner <ztur...@google.com> > wrote: > > > > > > Figured as much. Thanks for the tip. > > > > > > Back to the issue of the test suite, I ran the test suite but I get a > ton of errors in Objective C tests even without my patch applied. So I > must still be doing something worng. I used the xcodebuild command line, > then ran `test/dotest.py` with no arguments. I also tried `test/dotest.py > --executable bin/Debug/lldb packages/Python/lldbsuite/test` but that > doesn't seem to work either. What's the proper way to run the test suite > (given that building from the IDE doesn't work for me) > > > > > > > > > On Thu, Mar 24, 2016 at 2:54 PM Enrico Granata <egran...@apple.com> > wrote: > > >> On Mar 24, 2016, at 2:53 PM, Zachary Turner <ztur...@google.com> > wrote: > > >> > > >> Is it one time until I reboot, or until the end of the test suite? > > >> > > > > > > The former. > > > > > >> On Thu, Mar 24, 2016 at 2:51 PM Enrico Granata <egran...@apple.com> > wrote: > > >>> On Mar 24, 2016, at 2:44 PM, Zachary Turner via lldb-commits < > lldb-commits@lists.llvm.org> wrote: > > >>> > > >>> It's updated now. I'm still getting errors building from inside > Xcode when I use the IDE, but it works from the command line. But running > the test pops up hundreds of dialogs asking me to enter my password to take > control of another process, so I'm not sure how to disable that. > > >>> > > >> > > >> If you type your password once, then you should be able to dismiss > all other prompts with no detriment. > > >> Essentially, the first time you try to actually use the lldb_codesign > certificate to take control of an inferior process, OS X asks for your > password for extra security > > >> > > >>> Anyway I updated my patch if you want to give it a go. I'm not sure > why I didn't get any linker errors, because I didn't update the Xcode > project to include ClangUtil.cpp, so I was expecting some undefined symbol > errors. > > >>> > > >>> On Thu, Mar 24, 2016 at 2:34 PM Greg Clayton <clayb...@gmail.com> > wrote: > > >>> I usually select "desktop" as the target. Is this patch up to date? > If so, I can apply and compile it and let you know what the results are. > > >>> > > >>> > On Mar 24, 2016, at 2:21 PM, Zachary Turner <ztur...@google.com> > wrote: > > >>> > > > >>> > Yes I was doing it from inside the IDE though. I selected > lldb-tool, 64-bit, and hit Product -> Build > > >>> > > > >>> > On Thu, Mar 24, 2016 at 2:11 PM Greg Clayton <clayb...@gmail.com> > wrote: > > >>> > You you building with Xcode? You should be building by checking > out lldb at the top level, then typing: > > >>> > > > >>> > % xcodebuild -configuration Debug > > >>> > > > >>> > > > >>> > > On Mar 24, 2016, at 12:31 PM, Zachary Turner <ztur...@google.com> > wrote: > > >>> > > > > >>> > > Having trouble building on OSX. > > >>> > > > > >>> > > ERROR:root:Unable to find swig executable: 'module' object has > no attribute 'OSError' > > >>> > > > > >>> > > Command /bin/sh failed with exit code 250 > > >>> > > > > >>> > > > > >>> > > > > >>> > > But "which swig" finds it just fine. It's been a long time > since I've built on OSX so I don't know if something has changed. > > >>> > > > > >>> > > In any case, let me know if there's something I should be doing. > > >>> > > > > >>> > > > > >>> > > On Wed, Mar 23, 2016 at 4:12 PM Zachary Turner < > ztur...@google.com> wrote: > > >>> > > zturner added a comment. > > >>> > > > > >>> > > It's been a while since I've used my Mac. I'll fire it up and > see if I can get it going, but no promises. I'll update tomorrow > > >>> > > > > >>> > > > > >>> > > http://reviews.llvm.org/D18381 > > >>> > > > > >>> > > > > >>> > > > > >>> > > > >>> > > >>> _______________________________________________ > > >>> lldb-commits mailing list > > >>> lldb-commits@lists.llvm.org > > >>> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits > > >> > > >> > > >> Thanks, > > >> - Enrico > > >> 📩 egranata@.com ☎️ 27683 > > >> > > > > > > > > > Thanks, > > > - Enrico > > > 📩 egranata@.com ☎️ 27683 > > > > > > >
_______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
