[Rprotobuf-yada] Autoconf help
mstokely at google.com
Sat Jul 13 05:52:56 CEST 2013
I see thanks. Taking another look, I see that FreeBSD -CURRENT does
provide correct information returned from pkg-config -cflags protobuf as is
checked at the top of configure :
protobuf_cxxflags=`pkg-config --cflags protobuf`
protobuf_libs=`pkg-config --libs protobuf`
And these values are added to src/Makevars so that the compile can use them
if it gets that far, but the subsequent configure checks that look for the
protobuf headers aren't using these new cxxflags.
I added these 3 lines and now it works in FreeBSD and doesn't break Ubuntu
12 LTS either, so I submitted it:
## And make sure these flags are used for the tests below.
Thanks for the pointers.
On Fri, Jul 12, 2013 at 5:45 PM, Dirk Eddelbuettel <edd at debian.org> wrote:
> On 12 July 2013 at 13:46, Murray Stokely wrote:
> | RProtoBuf on FreeBSD doesn't find the protobuf headers even from the
> | system location /usr/local/include without setting an environment
> variable or
> | command-line flag.
> | I'm completely ignorant of autoconf. Does anyone know how best to add
> | something to configure.in to tell it to check /usr/local/include in
> addition to
> | wherever it is currently checking that seems to work on Debian/Ubuntu?
> I can definitely help you with that.
> For approaches uses pkg-config, check RcppGSL or RQuantLib. For simpler /
> mechanical approaches see RPostgreSQL or Rmpi which essentially
> loop over 'suspected' locations. We can certainly hack that.
> More once I'm back in Chicago.
> Dirk, still at SFO
> Dirk Eddelbuettel | edd at debian.org | http://dirk.eddelbuettel.com
> Rprotobuf-yada mailing list
> Rprotobuf-yada at lists.r-forge.r-project.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Rprotobuf-yada