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
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 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
For the JuliaLang project, we started with git-submodules for building some
of our loosly-coupled external dependencies, but eventually moved to a
custom-built solution (we call it "git-externals") to overcome some of the
workflow limitations. I haven't yet run across a similar suggestion
Hi,
My 2 cents on the topic:
1) I recommend not to use TortoiseGit. It tries to apply SVN workfliw to git, which doesn' t really work.
2) We use GitExtensions at our company for more than 2 years now. I prefer to use it with P4Merge instead if KDiff. It works much better(in my opinion).
And to
Hello,
Can we use GDB with lldb-server ? I see the vice-versa wroks i.e
LLDB with gdbserver. I did try using lldb-server with GDB but I got errors
(incompatible packet length). I was wondering if there is some special
tweaking needed for lldb-server to work with GDB ?
BR,
A Ravi Theja