I'm not sure if this is what you meant, but I don't see a lot of value in making an Xcode project that has targets for each of the gtest binaries, and then tries to run the tests. Seems to me it would be better if the gtest project just invokes whatever mechanism the cmake build would do to run the tests. That's just another set of things to keep in sync.
It is sufficient to have a target that just does whatever steps cmake/lit do to build the gtests & run them, if that is possible. I guess if you can't do this without running cmake in the lldb top-level directory that would be a problem. But it still seems better to me to wire that up, than to have to add tests to both Xcode & cmake. Jim > On Mar 12, 2015, at 3:46 PM, Zachary Turner <ztur...@google.com> wrote: > > So I'm guessing the scheme runs do-gtest.py. I'd like to delete that file as > well as all the Makefiles in the directory if possible. It seems like these > files should be built using the normal Xcode build system the same way the > rest of LLDB is built. > > The way the CMake does it is that each test folder generates a new > executable. So right now it will build HostTests.exe, ProcessLinuxTests.exe, > and UtilityTests.exe. And then CMake will invoke lit (the LLVM test runner) > to run each of the executables one by one and print the output. > > I'm not sure if that's easy or feasible to do in the Xcode build. I kind of > don't want to leave this do-gtest.py and Makefiles in the build though, > because the more of this stuff we have the more maintenance it is, and things > tend to rot. > > > On Thu, Mar 12, 2015 at 3:23 PM <jing...@apple.com> wrote: > Xcode has "projects" and then "workspaces" and "schemes". Workspaces > aggregate projects. Schemes exist in both workspaces and projects and are > the way to say "do something with some of the stuff referred to by this > project/workspace." So the way to do this formally is to have the gtest > scheme build & run the tests from the gtest project. > > The lldb.xcworkspace file does reference the gtest xcode project, and it has > a scheme for the gtest. > > Not sure what the scheme does yet, I'll look in a few minutes if nobody beats > me to it, I'm in the middle of things right now. > > Jim > > > > > On Mar 12, 2015, at 2:41 PM, Zachary Turner <ztur...@google.com> wrote: > > > > In lldb/gtest there is a gtest.xcodeproj folder with what I guess is an > > Xcode project. If I understand the way Xcode works, the way to use this is > > by opening this in another instance of Xcode separate from your normal LLDB > > project, and then building it. Is this right? > > > > I have a patch that moves some files around, and if nobody is using this > > Xcode project, I would like to delete it. Then, after I get the tests up > > and running in the CMake build, we can add it to the "real" Xcode project > > as a separate target similar to how you currently run the LLDB Test suite. > > > > Any objections to deleting the Xcode project? > _______________________________________________ lldb-dev mailing list lldb-dev@cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
