Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(257)

Unified Diff: ppapi/tests/clang/README

Issue 297963003: PPAPI: Remove clang plugins from ppapi/tests/clang (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src
Patch Set: Created 6 years, 7 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « ppapi/tests/clang/Makefile ('k') | ppapi/tests/clang/find_affected_interfaces.cc » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: ppapi/tests/clang/README
diff --git a/ppapi/tests/clang/README b/ppapi/tests/clang/README
deleted file mode 100644
index 64dd3321e55470ee82f481b113c942817c5a22ef..0000000000000000000000000000000000000000
--- a/ppapi/tests/clang/README
+++ /dev/null
@@ -1,57 +0,0 @@
-This is a directory for Clang plugins that are designed to do analysis and/or
-manipulation of PPAPI code. Clang is an open-source C front-end that allows
-you to parse C, C++, or Objective-C code in to an abstract syntax tree (or AST)
-for processing. This README assumes that you are working in a check-out of
-chromium.
-
-To use these plugins, you will need to get Clang. Clang is rapidly changing,
-so you may want to download and build it yourself. See the instructions here:
-- http://clang.llvm.org/get_started.html
-
-To build the plugins, use the Makefile in this directory. If you want the
-provided Makefile to work out-of-the-box, in step 2 of the instructions at the
-above URL, you should do the following:
-> mkdir ~/llvm
-> cd ~/llvm
-Now continue with the svn co command to check out llvm in ~/llvm/llvm. If you
-choose to build llvm in another location, you can use environment variables to
-force the Makefile to find your build of clang. See the Makefile for details.
-
-To run a plugin, use clang with the -cc1 -load and -plugin flags and an
-otherwise normal build line. For example, to run liBPrintNamesAndSizes.so, if
-you currently build like this:
-g++ (build_options)
-Run this from the command-line instead:
-clang -cc1 -load ppapi/tests/clang/libPrintNamesAndSizes.so \
- -plugin PrintNamesAndSizes (build_options)
-
-Plugins:
- PrintNamesAndSizes : print_names_and_sizes.cc
- Print information about all top-level type definitions. You probably won't
- need to run it by itself; instead see generate_ppapi_size_checks.py, which
- uses the plugin. See print_names_and_sizes.cc for more detail on the plugin.
-
- Example command-line:
- python generate_ppapi_size_checks.py \
- --ppapi-root=/usr/local/google/chrome_build/src/ppapi
- python generate_ppapi_size_checks.py --help
-
-
- FindAffectedInterfaces : find_affected_interfaces.cc
- Given typenames as parameters, print out all types that are affected
- (including function pointer types and structs containing affected function
- pointer types) if the given type(s) change. This is meant to be used for
- determining what interfaces are affected by a change to a struct.
-
- Example command-line:
- clang -cc1 -load ppapi/tests/clang/libFindAffectedInterfaces.so \
- -plugin FindAffectedInterfaces -I. ppapi/tests/all_includes.h \
- -plugin-arg-FindAffectedInterfaces \
- "struct PP_VideoCompressedDataBuffer_Dev"
- clang -cc1 -load tests/clang/libFindAffectedInterfaces.so \
- -plugin FindAffectedInterfaces -I../ tests/all_c_includes.h \
- -plugin-arg-FindAffectedInterfaces \
- "struct PP_VideoCompressedDataBuffer_Dev,struct PP_Var"
-
-(This assumes that clang is in your path and you are running the plugin from
- the ppapi subdirectory in a chrome checkout).
« no previous file with comments | « ppapi/tests/clang/Makefile ('k') | ppapi/tests/clang/find_affected_interfaces.cc » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698