llvm-project/lldb/source/DataFormatters/CMakeLists.txt

add_lldb_library(lldbDataFormatters
  CXXFunctionPointer.cpp
  DataVisualization.cpp
  DumpValueObjectOptions.cpp
  FormatCache.cpp
  FormatClasses.cpp
  FormatManager.cpp
  FormattersHelpers.cpp
  LanguageCategory.cpp
  StringPrinter.cpp
  TypeCategory.cpp
  TypeCategoryMap.cpp
  TypeFormat.cpp
  TypeSummary.cpp
  TypeSynthetic.cpp
  TypeValidator.cpp
  ValueObjectPrinter.cpp
  VectorType.cpp
  )
Convert to UNIX line endings. llvm-svn: 191367 2013-09-25 18:37:32 +08:00			`add_lldb_library(lldbDataFormatters`
Nuke CXXFormatterFunctions.cpp - split the contents of it across different files, so that things are better organized along the C++/ObjC line This is preparatory work for moving these formatters into language categories llvm-svn: 246827 2015-09-04 08:33:51 +08:00			`CXXFunctionPointer.cpp`
Convert to UNIX line endings. llvm-svn: 191367 2013-09-25 18:37:32 +08:00			`DataVisualization.cpp`
Let Language plugins vend a default DeclPrintingHelper in case a custom one is not specified for the specific invocation llvm-svn: 250744 2015-10-20 06:04:25 +08:00			`DumpValueObjectOptions.cpp`
Convert to UNIX line endings. llvm-svn: 191367 2013-09-25 18:37:32 +08:00			`FormatCache.cpp`
			`FormatClasses.cpp`
			`FormatManager.cpp`
Move the functions that FormatManager uses to actually load formatters into their own file These are useful helpers over the low-level API of the FormattersContainer, and since we're actually going to start moving formatters into plugins, it makes sense to simplify things llvm-svn: 246612 2015-09-02 09:21:31 +08:00			`FormattersHelpers.cpp`
Add support for language plugins to provide data formatters (second attempt) Historically, data formatters all exist in a global repository (the category map) On top of that, some formatters can be "hardcoded" when the conditions under which they apply are not expressible as a typename (or typename regex) This change paves the way to move formatters into per-language buckets such that the C++ plugin is responsible for ownership of the C++ formatters, and so on The advantages of this are: a) language formatters only get created when they might apply b) formatters for a language are clearly owned by the matching language plugin The current model is one of static instantiation, that is a language knows the full set of formatters it vends and that is only asked-for once, and then handed off to the FormatManager In a future revision it might be interesting to add similar ability to the language runtimes, and monitor for certain shared library events to add even more library-specific formatters No formatters are moved as part of this change, so practically speaking this is NFC llvm-svn: 246568 2015-09-02 02:22:39 +08:00			`LanguageCategory.cpp`
Fix CMake build, adding StringPrinter.cpp from r220894 llvm-svn: 220909 2014-10-30 22:50:42 +08:00			`StringPrinter.cpp`
Convert to UNIX line endings. llvm-svn: 191367 2013-09-25 18:37:32 +08:00			`TypeCategory.cpp`
			`TypeCategoryMap.cpp`
			`TypeFormat.cpp`
			`TypeSummary.cpp`
			`TypeSynthetic.cpp`
Add TypeValidator.cpp to cmake build. llvm-svn: 217280 2014-09-06 05:23:09 +08:00			`TypeValidator.cpp`
Fix CMake build by including ValueObjectPrinter.cpp in list of sources llvm-svn: 191703 2013-10-01 05:30:44 +08:00			`ValueObjectPrinter.cpp`
Windows bot llvm-svn: 231450 2015-03-06 11:37:33 +08:00			`VectorType.cpp`
Convert to UNIX line endings. llvm-svn: 191367 2013-09-25 18:37:32 +08:00			`)`