Re: [Discuss-gnuradio] How does 'make check' find its dependencies?

[Greg Troxel]

"Johnathan Corgan" <address@hidden> writes:

> On Thu, August 10, 2006 11:52, Greg Troxel wrote:
>
>> What I really want is an easy way to build each component by
>> downloading some tarball (can be same for all) and doing some sort of
>> ./configure argument and ending up with only each logical component
>> installed.   Your detailed suggestion sounds like it does this exactly.
>
> So to build only gnuradio-core, you'd put
>
> ./configure --disable-all --enable-gnuradio-core

And really, the Makefile.common for the gnuradio family will set the
distfile and

CONFIGURE_ARGS+=        --disable-all

and the individual package Makefiles will include that and

CONFIGURE_ARGS+=        --enable-gnuradio-core

so that should work fine.

>> From the pkgsrc point of view, it's ok to insist that a depending
>> component be either already installed where it belongs
>> or built in this build tree.
>
> That will work.  It's only a 'make check' issue, not a compile issue.  For
> example, if you wanted to create a gr-usrp package (that didn't have usrp
> in it also), 'make check' would need to resolve the location of the
> libusrp shared library.  Since you're not building usrp at the same time,
> and it might not be installed, 'make check' would fail.  It wouldn't stop
> you from building a package from the 'make install' output, but you
> couldn't put the 'make check' as part of the process.

We do have that now:

fnord gdt 312 /usr/pkgsrc/ham > l /usr/pkgsrc/ham/usrp/
total 20
drwxr-xr-x  2 gdt  ir   512 Jul 10 08:57 CVS
-r--r--r--  1 gdt  ir   532 Oct  7  2005 DESCR
-r--r--r--  1 gdt  ir   578 Jul 10 08:57 Makefile
-r--r--r--  1 gdt  ir  8995 Jul 10 08:57 PLIST
-r--r--r--  1 gdt  ir   628 Jul 10 08:57 buildlink3.mk
-r--r--r--  1 gdt  ir   232 May  2 12:51 distinfo
fnord gdt 313 /usr/pkgsrc/ham > l /usr/pkgsrc/ham/gnuradio-usrp/
total 10
drwxr-xr-x  2 gdt  ir   512 May  2 12:51 CVS
-r--r--r--  1 gdt  ir   512 Oct  7  2005 DESCR
-r--r--r--  1 gdt  ir   460 May  2 12:51 Makefile
-r--r--r--  1 gdt  ir  1528 May  2 12:51 PLIST
-r--r--r--  1 gdt  ir   237 May  2 12:51 distinfo

But, gnuradio-usrp's Makefile:

        # $NetBSD: Makefile,v 1.6 2006/04/27 03:14:19 wulf Exp $

        VERSION=        0.8
        DISTNAME=       gr-usrp-${VERSION}
        PKGNAME=        gnuradio-usrp-${VERSION}
        WRKSRC=         ${WRKDIR}/${DISTNAME}
        COMMENT=        USRP bindings for GNU Radio

        PYTHON_PATCH_SCRIPTS+=  src/flexrf_debug_gui.py
        PYTHON_PATCH_SCRIPTS+=  src/tx_debug_gui.py

        .include "../../meta-pkgs/gnuradio/Makefile.common"

        .include "../../ham/usrp/buildlink3.mk"
        .include "../../math/fftwf/buildlink3.mk"
        .include "../../mk/bsd.pkg.mk"

says that usrp must be not only installed, but libraries it provides
symlinked into the build environment.  Thus, from the pkgsrc
viewpoint, it's perfectly ok to link against usrp libraries in
a gnuradio-usrp build, and surely this must usually happen for
depending builds.

> It's good to brainstorm this out because eventually we want to automate
> the creation of .rpms and .debs and this issue will show up then too.

Indeed.  Thanks for accomodating this in the gnuradio repo; it's far
easier to spiff things up there than to have to work around this with
makefile patches.

-- 
    Greg Troxel <address@hidden>

pgpX_PzjwTcFX.pgp
Description: PGP signature