From: SG15 <sg15-bounces@lists.isocpp.org> on behalf of Gamblin, Todd via SG15 <sg15@lists.isocpp.org>
Sent: Wednesday, October 27, 2021 1:31:43 PM
To: Michael Spencer via SG15 <sg15@lists.isocpp.org>
Cc: Gamblin, Todd <gamblin2@llnl.gov>
Subject: Re: [SG15] RFC: Requirements to consume a prebuilt library from arbitrary build systems

I don’t think this is a borderline topic if you really want people to use packages that are prebuilt and, say, installed on a system. People don’t consume “libraries” — they consume *packages* as installed by the packages’ maintainers. In many cases that may include programs that need to be exec’d either by the client code or by the package, at build or runtime. Similarly there are libraries out there that aren’t usable without associated data.

One example of such a library would be SWIG (https://github.com/swig/swig). It generates C and C++ bindings for higher level languages. There are lots of code generators like this.

-Todd

On Oct 27, 2021, at 12:24 PM, Daniel Ruoso via SG15 <sg15@lists.isocpp.org> wrote:

On Wed, Oct 27, 2021, 12:06 Ben Craig <ben.craig@ni.com> wrote:

How do I invoke your code generator (like with gRPC, Apache Thrift, Microsoft RPC, QT)? How do I deal with dependencies with your code generator?

That's an interesting borderline topic.

There's a line to be drawn between consuming libraries and describing how tools are used.

I'd be interested to learn more about the scenario where this comes in the context of a prebuilt library dependency.

_______________________________________________
SG15 mailing list
SG15@lists.isocpp.org
https://urldefense.us/v3/__https://lists.isocpp.org/mailman/listinfo.cgi/sg15__;!!G2kpM7uM-TzIFchu!gU5mpBDujul3qtXXFtvkg5HMK3BX7z4PrcJ50Kx_jNFDGJSj6a9UhhsFz0IvbXKp$