You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Peter Donald (JIRA)" <ji...@apache.org> on 2012/10/07 01:49:06 UTC
[jira] [Updated] (BUILDR-563) protobuf addon including source
directories to protoc breaks build
[ https://issues.apache.org/jira/browse/BUILDR-563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Donald updated BUILDR-563:
--------------------------------
Fix Version/s: 1.5
> protobuf addon including source directories to protoc breaks build
> ------------------------------------------------------------------
>
> Key: BUILDR-563
> URL: https://issues.apache.org/jira/browse/BUILDR-563
> Project: Buildr
> Issue Type: Bug
> Reporter: Robin Palotai
> Priority: Trivial
> Fix For: 1.5
>
>
> In "addon/buildr/protobuf.rb", the following line:
> (paths_from_sources(*args) + options[:include]).each { |i| command_line << "-I#{i}" }
> Incorrectly puts "/a/b" on the include path for any input file "/a/b/xyz.proto". This is bad, the user should support the _root_ include path(s) if they wish to, and not any paths below it. The current scheme breaks compilation of proto files organised under an "a.b" package hierarchy.
> Excerpts from the message http://www.mail-archive.com/protobuf@googlegroups.com/msg04129.html
> 'when you pass "../P/a.proto" on the command line, protoc concludes that because "../P" is in the import path, this file's canonical name is "a.proto" [...] In general, you should never pass overlapping -I flags to protoc.'
> Fix:
> Delete including the source directories, change the line to
> (options[:include]).each { |i| command_line << "-I#{i}" }
> and include the instruction to use the include path to the documentation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira