Date: Fri, 20 Apr 2012 19:17:43 +0300 From: Vitaly Magerya <vmagerya@gmail.com> To: Chris Inacio <nacho319@gmail.com> Cc: Jeremy Messenger <mezz.freebsd@gmail.com>, freebsd-ports@freebsd.org Subject: Re: port dependencies with port options Message-ID: <CAL409Ky3birNuUHBj2i2Ht%2Boww2n-v9Kn9QY=65tTMaR1bU8AA@mail.gmail.com> In-Reply-To: <CAG_PEewPT5jYM%2BRNy=64cN0Je0phC8CiuNCU9xiHeDMCWCW-gA@mail.gmail.com> References: <CAG_PEeyM78_8vdpLy5g%2BWRAsEW51T2OZertcB_NGwogh0TSceA@mail.gmail.com> <4F913A7C.7050601@gmail.com> <CADLFttdcjGboDWsvKaaRsi0OAcYRLOR5N2WVuFdAyWMXZNkWRg@mail.gmail.com> <CAG_PEewPT5jYM%2BRNy=64cN0Je0phC8CiuNCU9xiHeDMCWCW-gA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Chris Inacio <nacho319@gmail.com> wrote: > So let me see if I understand the conversation so far correctly: > > (*) If I want to detect it, then I would need something like a new library > name output from from fixbuf based on the build. (This currently doesn't > exist.) New library name is not for detection; net/libfixbuf installs libfixbuf.so (and a bunch of related files), what you need is a separate port, net/libfixbuf-spread, that would compile libfixbuf with Spread support and install a separate library (so it would not conflict with the one net/libfixbuf installs), e.g. libfixbuf-spread.so. Then your port, net-mgmt/yaf, depending on the USE_SPREAD option, will either depend on net/libfixbuf and link with -lfixbuf, or will depend on net/libfixbuf-spread and will link with -lfixbuf-spread. > (*) I could do some split port, but (even being a noob) sounds pretty bad. It's not hard, and we can help you. > (*) There isn't a current method that directly queries build options from > one port to another. Right. > Am I capturing current state?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAL409Ky3birNuUHBj2i2Ht%2Boww2n-v9Kn9QY=65tTMaR1bU8AA>