llvm-mirror/tools/obj2yaml/CMakeLists.txt

set(LLVM_LINK_COMPONENTS
  BinaryFormat
  DebugInfoCodeView
  DebugInfoDWARF
  Object
  ObjectYAML
  Support
  )

add_llvm_utility(obj2yaml
  archive2yaml.cpp
  obj2yaml.cpp
  coff2yaml.cpp
  dwarf2yaml.cpp
  elf2yaml.cpp
  macho2yaml.cpp
  minidump2yaml.cpp
  xcoff2yaml.cpp
  wasm2yaml.cpp
  )
[CMake] Update LLVM_LINK_COMPONENTS for each CMakeLists.txt. llvm-svn: 196908 2013-12-10 12:13:32 +01:00			`set(LLVM_LINK_COMPONENTS`
Fix debug build by adding missing dependencies on libBinaryFormat Debug BUILD_SHARED_LIBS build was broken by rL332305 Differential Revision: https://reviews.llvm.org/D46859 llvm-svn: 332315 2018-05-15 02:46:43 +02:00			`BinaryFormat`
Resubmit "[codeview] Make obj2yaml/yaml2obj support .debug$S..." This was originally reverted because of some non-deterministic failures on certain buildbots. Luckily ASAN eventually caught this as a stack-use-after-scope, so the fix is included in this patch. llvm-svn: 305393 2017-06-14 17:59:27 +02:00			`DebugInfoCodeView`
[ObjectYAML] First bit of support for encoding DWARF in MachO This patch adds the starting support for encoding data from the MachO __DWARF segment. The first section supported is the __debug_str section because it is the simplest. llvm-svn: 288774 2016-12-06 07:00:49 +01:00			`DebugInfoDWARF`
[CMake] Update LLVM_LINK_COMPONENTS for each CMakeLists.txt. llvm-svn: 196908 2013-12-10 12:13:32 +01:00			`Object`
Move ObjectYAML code to a new library. It is only ever used by obj2yaml and yaml2obj. No point in linking it everywhere. llvm-svn: 262368 2016-03-01 20:15:06 +01:00			`ObjectYAML`
[CMake] Update LLVM_LINK_COMPONENTS for each CMakeLists.txt. llvm-svn: 196908 2013-12-10 12:13:32 +01:00			`Support`
			`)`
New test tool: obj2yaml llvm-svn: 158730 2012-06-19 20:02:35 +02:00
[llvm] Make obj2yaml and yaml2obj LLVM utilities instead of tools For testing purposes I need a way to build and install FileCheck and yaml2obj. I had to choose between making FileCheck an LLVM tool and making obj2yaml and yaml2obj utilities. I think the distinction is rather arbitrary but my understanding is that tools are things meant for the toolchain while utilities are more used for things like testing, which is the case here. The functional difference is that these tools now end up in the ${LLVM_UTILS_INSTALL_DIR}, which defaults to the ${LLVM_TOOLS_INSTALL_DIR}. Unless you specified a different value or you added obj2yaml and yaml2obj to ${LLVM_TOOLCHAIN_TOOLS}, this patch shouldn't change anything. Differential revision: https://reviews.llvm.org/D89357 2020-10-19 19:18:20 +02:00			`add_llvm_utility(obj2yaml`
[yaml2obj][obj2yaml] - Teach tools to work with regular archives. This teaches obj2yaml to dump valid regular (not thin) archives. This also teaches yaml2obj to recognize archives YAML descriptions, what allows to craft all different kinds of archives (valid and broken ones). Differential revision: https://reviews.llvm.org/D89949 2020-10-20 14:12:28 +02:00			`archive2yaml.cpp`
Initial add for MachO support for obj2yaml Adding the initial files for adding MachO support to obj2yaml. Passing a MachO file will result in a new not_implemented error. I will be implementing obj2yaml and yaml2obj for MachO in parallel so that one can be used to test the other. llvm-svn: 269243 2016-05-12 00:07:45 +02:00			`obj2yaml.cpp`
			`coff2yaml.cpp`
[obj2yaml] Refactor and abstract dwarf2yaml This makes the dwarf2yaml code separated and reusable allowing ELF and COFF to share implementations with MachO. llvm-svn: 288986 2016-12-07 22:47:28 +01:00			`dwarf2yaml.cpp`
Initial add for MachO support for obj2yaml Adding the initial files for adding MachO support to obj2yaml. Passing a MachO file will result in a new not_implemented error. I will be implementing obj2yaml and yaml2obj for MachO in parallel so that one can be used to test the other. llvm-svn: 269243 2016-05-12 00:07:45 +02:00			`elf2yaml.cpp`
			`macho2yaml.cpp`
Add minidump support to obj2yaml Summary: This patch adds the code needed to parse a minidump file into the MinidumpYAML model, and the necessary glue code so that obj2yaml can recognise the minidump files and process them. Reviewers: jhenderson, zturner, clayborg Subscribers: mgorny, lldb-commits, amccarth, markmentovai, aprantl, llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D59634 llvm-svn: 357469 2019-04-02 13:58:37 +02:00			`minidump2yaml.cpp`
[XCOFF] Add functionality for parsing AIX XCOFF object file headers Summary: 1. Add functionality for parsing AIX XCOFF object files headers. 2. Only support 32-bit AIX XCOFF object files in this patch. 3. Print out the AIX XCOFF object file header in YAML format. Reviewers: sfertile, hubert.reinterpretcast, jasonliu, mstorsjo, zturner, rnk Reviewed By: sfertile, hubert.reinterpretcast Subscribers: jsji, mgorny, hiraditya, jdoerfert, llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D59419 Patch by Digger Lin llvm-svn: 357663 2019-04-04 02:53:21 +02:00			`xcoff2yaml.cpp`
[WebAssembly] Improve support for WebAssembly binary format Mostly this change adds support converting to and from YAML which will allow us to write more test cases for the WebAssembly MC and lld ports. Better support for objdump, readelf, and nm will be in followup CLs. I had to update the two wasm test binaries because they used the old style 'name' section which is no longer supported. Differential Revision: https://reviews.llvm.org/D31099 Patch by Sam Clegg llvm-svn: 299101 2017-03-30 21:44:09 +02:00			`wasm2yaml.cpp`
New test tool: obj2yaml llvm-svn: 158730 2012-06-19 20:02:35 +02:00			`)`