[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] compiling c++ blocks

From: Milo Wong
Subject: Re: [Discuss-gnuradio] compiling c++ blocks
Date: Tue, 25 Aug 2009 11:55:36 -0700

Hi all,

If I have .cc .h .i and Makefile.am all ready, could I go back to the top directory containing "configure" and make again(make from the top) instead of using automake at src/lib directory in order to generate the make file?

Thank you,


On Fri, Aug 21, 2009 at 9:15 AM, Douglas Geiger <address@hidden> wrote:
I believe you need to re-generate it manually (I'm not sure if the
intent was to have it automagically re-built or not). If you go into
the directory(s) that contain the .i files, you can call:
 make generate-makefile-swig
And the Makefile.swig.gen's will be rebuilt from the top-level
template (Makefile.swig.gen.t) according to the names you've set in
the Makefile.am. Removing it entirely does seem to make the
automake/autoconf system choke.

On Mon, Aug 17, 2009 at 4:44 PM, Jordan J Riggs<address@hidden> wrote:
>> You don't need to modify that file; it's [Makefile.swig.gen] generated.
> Are you sure about this? When I replace every occurrence of "howto" in
> Makefile.swig.gen with my own package name, it seems to work. However, when
> I leave this file as it is in gr-how-to-write-a-block, or remove it
> entirely, the build process fails. (At make or in bootstrap, respectively.)
> After looking closely at that file, it looks like it should be generated,
> but my experiences say otherwise.
> _______________________________________________
> Discuss-gnuradio mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Doug Geiger

Discuss-gnuradio mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]