[lldb-dev] Incorrect libclang dependency in standalone build

Pavel Labath via lldb-dev lldb-dev at lists.llvm.org
Mon Jun 13 20:51:11 PDT 2016

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
dependency list. So, you should just be able to wrap that statement in
an if(). Ideally something like IF(LLDB_STANDALONE_BUILD), but it that
is not possible IF(TARGET libclang) will work as well...


On 10 June 2016 at 16:34, Eugene Zelenko via lldb-dev
<lldb-dev at lists.llvm.org> wrote:
> On Fri, Jun 10, 2016 at 4:25 PM, Pavel Labath <labath at google.com> 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.cmake tells:
> # Hack: only some LLDB libraries depend on the clang autogenerated headers,
> # but it is simple enough to make all of LLDB depend on some of those
> # headers without negatively impacting much of anything.
> add_dependencies(${name} libclang)
> May be dependencies should be expressed explicitly? Of course, if
> libraries will be valid.
>> pl
> Eugene.
> _______________________________________________
> lldb-dev mailing list
> lldb-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

More information about the lldb-dev mailing list