I don't think you need to concern yourself with that comment. We
should make the dependency graph cleaner, but that is not something
related to your current problem.
IIUC, in case of a standalone build, you can assume that the relevant
target was already built, and you don't need to add it to the
On Fri, Jun 10, 2016 at 4:25 PM, Pavel Labath wrote:
> This is a side-effect of the cmake version bump to 3.4. Cmake now
> errors out on non-existing targets. You'll need to figure out a way to
> avoid adding this target to the dependency list. Patches welcome. :)
Comment in cmake/modules/AddLLDB
This is a side-effect of the cmake version bump to 3.4. Cmake now
errors out on non-existing targets. You'll need to figure out a way to
avoid adding this target to the dependency list. Patches welcome. :)
pl
On 10 June 2016 at 16:20, Eugene Zelenko via lldb-dev
wrote:
> Hi!
>
> I got next messa
Hi!
I got next message for each internal library when building standalone
LLDB on RHEL 6:
CMake Warning (dev) at cmake/modules/AddLLDB.cmake:90 (add_dependencies):
Policy CMP0046 is not set: Error on non-existent dependency in
add_dependencies. Run "cmake --help-policy CMP0046" for policy de
