llvm-project/clang/examples/CMakeLists.txt

if(NOT CLANG_BUILD_EXAMPLES)
  set_property(DIRECTORY PROPERTY EXCLUDE_FROM_ALL ON)
  set(EXCLUDE_FROM_ALL ON)
endif()

add_subdirectory(clang-interpreter)
add_subdirectory(PrintFunctionNames)
add_subdirectory(AnnotateFunctions)
add_subdirectory(Attribute)
add_subdirectory(CallSuperAttribute)
Adjust CLANG_BUILD_EXAMPLES to mean whether the examples are built by default, rather than whether they may be built at all. llvm-svn: 149037 2012-01-26 03:33:40 +00:00			`if(NOT CLANG_BUILD_EXAMPLES)`
Honour CLANG_BUILD_EXAMPLES correctly, by setting the directory's EXCLUDE_FROM_ALL property. llvm-svn: 156090 2012-05-03 19:11:45 +00:00			`set_property(DIRECTORY PROPERTY EXCLUDE_FROM_ALL ON)`
[CMake] Fix installation without CLANG_BUILD_EXAMPLES When CLANG_BUILD_EXAMPLES is not on we set the EXCLUDE_FROM_ALL directory property for the examples/ directory to tell CMake not to build them by default. The AddLLVM.cmake APIs are not aware of this and try to install targets that are not built. This does not cause an install-time error because CMake excludes the directory from the default installation. However, now that installation attaches targets to the LLVMExports export set CMake-based applications that find_package(LLVM) fail because the example plugin binary is not available. Tell the AddLLVM.cmake APIs to exclude the examples from installation by setting the EXCLUDE_FROM_ALL variable they check. Patch by Brad King! llvm-svn: 201799 2014-02-20 17:43:31 +00:00			`set(EXCLUDE_FROM_ALL ON)`
Adjust CLANG_BUILD_EXAMPLES to mean whether the examples are built by default, rather than whether they may be built at all. llvm-svn: 149037 2012-01-26 03:33:40 +00:00			`endif()`

Wire up Daniel's new spiffy C interpreter into the CMake build system llvm-svn: 97311 2010-02-27 07:46:49 +00:00			`add_subdirectory(clang-interpreter)`
Add missed CMake file for adding clang examples to CMake build. llvm-svn: 89080 2009-11-17 09:40:40 +00:00			`add_subdirectory(PrintFunctionNames)`
Make it possible for AST plugins to enable themselves by default Currently when an AST plugin is loaded it must then be enabled by passing -plugin pluginname or -add-plugin pluginname to the -cc1 command line. This patch adds a method to PluginASTAction which allows it to declare that the action happens before, instead of, or after the main AST action, plus the relevant changes to make the plugin action happen at that time automatically. Differential Revision: http://reviews.llvm.org/D17959 llvm-svn: 263546 2016-03-15 12:51:40 +00:00			`add_subdirectory(AnnotateFunctions)`
Add an attribute plugin example Differential Revision: https://reviews.llvm.org/D31343 2020-03-25 13:49:02 +00:00			`add_subdirectory(Attribute)`
Add a call super attribute plugin example If a virtual method is marked as call_super, the override method must call it, simpler feature like @CallSuper in Android Java. 2020-11-20 08:50:39 -05:00			`add_subdirectory(CallSuperAttribute)`