FWGS/waf
2
0
Fork 0
mirror of https://gitlab.com/ita1024/waf.git synced 2025-01-22 08:20:02 +01:00
Code Issues Projects Releases Wiki Activity

extras: protoc: document protoc trickiness

Browse Source 
I tried to quickly go through the protoc source to find how the include
paths are interpreted, but I'm sleepy now.
This commit is contained in:
Jérôme Carretero 2013-09-05 01:10:20 -04:00
parent bf5ce8b30c
commit 00946bacdb
1 changed files with 13 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
waflib/extras/protoc.py
View File

@ -10,6 +10,8 @@ from waflib.TaskGen import extension
""" """
A simple tool to integrate protocol buffers into your build system. A simple tool to integrate protocol buffers into your build system.
Example::
def configure(conf): def configure(conf):
conf.load('compiler_cxx cxx protoc') conf.load('compiler_cxx cxx protoc')
@ -20,9 +22,20 @@ A simple tool to integrate protocol buffers into your build system.
include = '. proto', include = '. proto',
target = 'executable') target = 'executable')
Notes when using this tool:
- protoc command line parsing is tricky.
The generated files can be put in subfolders which depend on
the order of the include paths.
Try to be simple when creating task generators
containing protoc stuff.
""" """
class protoc(Task): class protoc(Task):
# protoc expects the input proto file to be an absolute path.
run_str = '${PROTOC} ${PROTOC_FLAGS} ${PROTOC_ST:INCPATHS} ${SRC[0].abspath()}' run_str = '${PROTOC} ${PROTOC_FLAGS} ${PROTOC_ST:INCPATHS} ${SRC[0].abspath()}'
color = 'BLUE' color = 'BLUE'
ext_out = ['.h', 'pb.cc'] ext_out = ['.h', 'pb.cc']