endoli / lldb-sys.rs Goto Github PK

View Code? Open in Web Editor NEW

12.0 12.0 7.0 866 KB

LLDB bindings for Rust.

License: Apache License 2.0

Rust 23.18% C++ 76.13% Shell 0.02% sed 0.14% C 0.52%

lldb-sys.rs's People

Contributors

Stargazers

Watchers

Forkers

slnpacifist no9 dzfranklin atouchet gmh5225 ldm0 roccoblues

lldb-sys.rs's Issues

Why does this package needs llvm source?

Hi!
I'm a newbee to working on library-linked crates and my task is to make this package work in linux. Working on Ubuntu 16.04 64-bit I managed to make it work (still need some experience to send a good PR), however, main question is: why is this crate needs llvm source?
I mean there are bindings generated from LLDB API header files. These header files were taken from some version of LLDB. Is not it better to put all needed files (those are from lldb/include, llvm/include and build/include). There is only one file (Compiler.h from llvm includes) that requires build/include file and this include can be ignored.
What I did for the first time:

checked out llvm,
checked out lldb into llvm/tools
checked out clang in llvm/tools
run cmake to generate /build files
built this crate using println!("cargo:rustc-link-lib=lldb-3.8"); instead of frameworks and setting needed env variables.

What I did for the second time:

copied llvm/includes into a separate directory within a crate source
copied lldb/includes into a separate directory within a crate source
commented out unnecessary include in Compiler.h
built this crate without using any references to external files.

In both cases I got working library that was used to run and close /bin/ls using LLDB (I had lldb 3.8 installed from http://apt.llvm.org/).

Are there reasons for llvm header files to be excluded from this package?

LLDB header files may have moved

Caveat: I'm used to using ptrace and libdwarf directly instead of using LLVM infrastructure, and am also a Rust newbie, so I could well be off the mark here.

Hi,

I've checked out and built LLVM, and set LLVM_ROOT and LLVM_BUILD_ROOT, essentially using the following abbreviated steps:

$ pwd
/Users/ntaylor/code
$ git clone https://github.com/llvm/llvm-project.git
$ cd llvm_project; mkdir build; cd build
$ cmake -DLLDB_INCLUDE_TESTS=OFF -DLLVM_ENABLE_PROJECTS="clang;lldb" -G "Unix Makefiles" ../llvm`
...
$ export LLVM_ROOT=~/code/llvm-project
$ export LLVM_BUILD_ROOT=~/code/llvm-project/build

However, I get the following lldb-sys build error:

$ cargo build
   Compiling lldb-sys v0.0.27
   Compiling libc v0.2.107
The following warnings were emitted during compilation:

warning: In file included from src/lldb/UnityBuild.cpp:1:
warning: src/lldb/Bindings/SBAddressBinding.cpp:10:10: fatal error: 'lldb/API/LLDB.h' file not found
warning: #include "lldb/API/LLDB.h"
warning:          ^~~~~~~~~~~~~~~~~
warning: 1 error generated.

error: failed to run custom build command for `lldb-sys v0.0.27`

A quick glance at where that header lives:

$ pwd
/Users/ntaylor/code/llvm-project
$ find . -name 'LLDB.h'
./lldb/include/lldb/API/LLDB.h
$

Not a problem to fix simply by copying that directory tree into my `build/ directory...

$ cp -r lldb/include/lldb build/include
$ find . -name 'LLDB.h'
./lldb/include/lldb/API/LLDB.h
./build/include/lldb/API/LLDB.h
$ cargo build
   Compiling lldb-sys v0.0.27
   Compiling lldb v0.0.10
   Compiling ivydb v0.1.0 (/Users/ntaylor/code/ivydb)
    Finished dev [unoptimized + debuginfo] target(s) in 1.43s

I wonder whether $LLVM_ROOT/build/include should be passed to rustc to search for headers?

Thanks!

Cannot build on Ubuntu 20.10

System info

> lsb_release -a
Distributor ID:	Pop
Description:	Pop!_OS 20.10
Release:	20.10
Codename:	groovy

> uname -a
Linux daniel-darter 5.11.0-7614-generic #15~1618626693~20.10~ecb25cd-Ubuntu SMP Thu Apr 22 16:00:45 UTC  x86_64 x86_64 x86_64 GNU/Linux

> llvm-config --version
11.0.0

Reproduced on lldb-sys.rs HEAD, v0.0.21, and v0.0.20. Didn't check older.

To reproduce

> gh repo clone endoli/lldb-sys.rs
> cd lldb-sys.rs
> cargo build

The error

src/lldb/Bindings/SBCommandInterpreterBinding.cpp: In function ‘SBCommandInterpreterRunOptionsOpaque* CreateSBCommandInterpreterRunOptions()’:
  src/lldb/Bindings/SBCommandInterpreterBinding.cpp:22:99: error: invalid use of incomplete type ‘class lldb::SBCommandInterpreterRunOptions’
     22 |     return reinterpret_cast<SBCommandInterpreterRunOptionsRef>(new SBCommandInterpreterRunOptions());
        |                                                                                                   ^
  In file included from /usr/lib/llvm-11/include/lldb/API/SBBreakpoint.h:12,
                   from src/lldb/Bindings/SBBreakpointBinding.h:15,
                   from src/lldb/Bindings/LLDBBinding.h:21,
                   from src/lldb/Bindings/SBCommandInterpreterBinding.cpp:10:

(full stderr)

endoli / lldb-sys.rs Goto Github PK

lldb-sys.rs's People

Contributors

Stargazers

Watchers

Forkers

lldb-sys.rs's Issues

Why does this package needs llvm source?

LLDB header files may have moved

Cannot build on Ubuntu 20.10

System info

To reproduce

The error

Consider removing bindings for things that are essentially deprecated?

Add bindings for `SBTrace` and `SBTraceOptions`.

Add bindings for `SBFile`.

Add bindings for `SBEnvironment`.

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent