[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Discuss-gnuradio] C++ Block Development / configure.ac
From: |
Martin Braun |
Subject: |
[Discuss-gnuradio] C++ Block Development / configure.ac |
Date: |
Tue, 11 Dec 2007 13:21:09 +0100 |
User-agent: |
KMail/1.9.5 |
Hi block developers,
I've some questions regarding block development. First of all, what I did was
take the gr-howto-write-xxx package, chuck out anything that was
howto-specific and replace it with my own code. Is this how everone else goes
along?
Next, I realized that if I don't want to call my module 'howto' I need to edit
configure.ac. Here is what I guessed:
AC_INIT
AC_PREREQ(2.57)
AC_CONFIG_SRCDIR([src/lib/howto.i])
AM_CONFIG_HEADER(config.h)
AC_CANONICAL_TARGET([])
AM_INIT_AUTOMAKE(gr-howto-write-a-block,3.1.1)
Changing AC_CONFIG_SRCDIR to the source of my i-files and putting in the
directory name of my block in AM_INIT_AUTOMAKE seemed to work, after
re-running ./bootstrap.
This all seems to work, but I'd like to know if I've missed anything else
which is usually changed (but not in the docs for howto-write-a-block)?
I apologize if this all seems trivial, but it caused some confusion for me
(e.g., I wasn't able to run `make check' without installing my modules at
first, before I had the configure.ac settings right). I wouldn't mind
righting some lines for the howto-write-a-block docs if anyone else feels
this is worth mentioning to autoconf and automake newbies.
--
Martin Braun
Institut fuer Nachrichtentechnik
Universitaet Karlsruhe
http://www.int.uni-karlsruhe.de
- [Discuss-gnuradio] C++ Block Development / configure.ac,
Martin Braun <=