I'm open to improvements here but I'm not sure I understand what exactly is being proposed. Under what circumstances, exactly, would someone want the capnp binary to have a different default import location than /usr/include?
It doesn't seem to make sense for cross compiling because I would expect users to use the same capnp binary for all target platforms, since capnpc's behavior is not in any way dependent on target platform, nor would I expect different platforms to have different .capnp files available. -Kenton On Thu, Jun 30, 2016 at 10:53 AM, David Lamparter <[email protected]> wrote: > On Thu, Jun 30, 2016 at 07:43:26PM +0200, David Lamparter wrote: > > I've recently added a "c.capnp" file with annotations to control code > > generation to the Cap'n Proto C bindings. Now I have to figure out what > > to do with it... it seems the C++ core stuff installs c++.capnp, > > schema.capnp and rpc.capnp to /usr/include/capnp; I assume that's the > > intended target location? If so - why doesn't capnpc search that > > directory by default? > > Scratch that, for some reason the examples I looked at had > 'import "c++.capnp"' instead of 'import "/capnp/c++.capnp"'. The latter > obviously makes way more sense. Derp. > > Still leaves the question on how to get an install path. The > compiler/capnp.c++ currently hardcodes /usr/local/include + /usr/include > + CAPNP_INCLUDE_DIR. In the hopes that this will change at some point > for better multi-environment (cross compiling, alternate roots, etc.) > support, it'd be nice if this could actually be queried off the install? > > -David > > > And is there some way to get the path to that directory? (e.g. > > pkg-config --variable?) > > > > Also, I should point out that C and C++ collide in the names of the > > generated header files (e.g. schema.capnp.h). I'll have to put them in > > another directory... > > > > (Unfortunately, the C bindings emit "#include foo.capnp.h" for any > > "import foo.capnp" they see, even if it's not neccessary...) > > > > > > Cheers, > > > > -David > > > > -- > > You received this message because you are subscribed to the Google > Groups "Cap'n Proto" group. > > To unsubscribe from this group and stop receiving emails from it, send > an email to [email protected]. > > Visit this group at https://groups.google.com/group/capnproto. > > -- > You received this message because you are subscribed to the Google Groups > "Cap'n Proto" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > Visit this group at https://groups.google.com/group/capnproto. > -- You received this message because you are subscribed to the Google Groups "Cap'n Proto" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/capnproto.
