build: separate lldb_include_dir and lldb_lib_dir #185
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
since the headers can be downloaded by us while the libraries
cannot at the moment. On some systems we are not able to
find the non-versioned liblldb dynamic library (
-llldb) anyway,it's working fine until now because the lldb will resolve the
symbols before loading the plugin, but this will have to be handled
differently in the case of addons which need the symbols at build time.
Also use ldd to find the correct name of the library.
lldb_include_dirandlldb_lib_dirandpoint them to subdirectories of the lldb installation to
match the concepts in llvm-config.
$lldb_include_dir/lldb/APIfor headers since someincomplete installations may not have the API headers installed.
which can write the path to the headers in the config.gypi anyway.
can be shared by the addon target later.
step.
always trying to run it in each configuration step.
In preparation for the addon API.
Refs: #147