Well that’s s great question! Right now my spec for building plugins downloads entire bro tree and does some cmake plugin to avoid waiting for the tree to build.
> On May 24, 2018, at 9:50 PM, Vlad Grigorescu <[email protected]> wrote: > > There are a couple of cases where I think it'd be useful to have a bro-devel > package -- a package that I can install on a system, and then be able to > build plugins against Bro. (This is the same model as other *-devel packages, > such as openssl, libpcap, etc.) > > Right now, if I compile Bro from source, run make install, I can't build a > package with what's in /usr/local -- Bro needs the entire source tree, since > the required headers are not present in /usr/local. > > I'm curious how people are dealing with this issue, and if anyone has > thoughts on whether this would be useful, and if so, what it would take to > build such a package. > > Thanks, > > --Vlad > _______________________________________________ > bro-dev mailing list > [email protected] > http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev _______________________________________________ bro-dev mailing list [email protected] http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev
