[Hamlib-developer] Re: hamlib development

[<rs...@su...>]

Ah, perhaps I have found the problem: a "cvs update" instead of "cvs co".
The "co" now also got me the new directories. The ./configure now works,
but "make" fails again:

---
cd . && aclocal
aclocal: couldn't open `configure.in': No such file or directory
make: *** [aclocal.m4] Error 2
---

On Fri, 24 Aug 2001 f4...@fr... wrote:

> My guess is that's related to the version of autoconf/automake/libtool.
> see below.
>
> Okay, here we go. Hamlib-1.1.1 has been developped using autoconf 2.13,
> automake-1.4 and libtool-1.3.5 as far as I remember. Well, the big change
> with the CVS rep is we're now using autoconf 2.52, automake-1.4p4(waiting
> for automake-1.5) and libtool-1.4b. Bleeding edges can get really bloody
> sometimes.
> So, the biggest change is between autoconf-2.13 to >2.50. configure.in is
> no more. Since some macros have been redesigned, autoconf maintainers
> decided to rename this file to autoconf.ac, which clears up at the same time
> the ambiguity with Makefile.in and anything.in different purpose extension.

With these tools, I am an absolute beginner. I have been using autoconf
2.13, automake 1.4 and libtool 1.3.5.

> My quick work around consists in creating shell scripts in hamlib root
> directory, with names automake,autoconf,aclocal,autoheader containing
> something like this:
>
>         #!/bin/sh
>         exec ./missing `basename $0` $*

I have tried this, but it makes no difference. For me first tests, I will
stay with the 1.1.1 release. Perhaps I can change that soon.

> I hope we'll see better days soon. Actually, this is my first time
> using autotools, and I'm still learning the arcanes of these very powerful
> tools. In the end, it's worth it: portability of Hamlib to *any* system!

This *will be* the first time for me :-)

Let's set the range of my project first.

We said that I should code a GUI for hamlib? So what would that require?
Some C (ok), Qt, auto-*, what else? What should this GUI be capable of? If
we get that all together, then Kai and me can start making a time schedule
for planning/coding/testing/... (after all, I should learn that here as
well :-).

> > I just read the FT847 manual and found out it only needs a nullmodem
> > cable
> > for CAT operations. I might be lucky and have a ready cable in the
> > shack;
> > I'll go and test it
>
> Fine business Robert, as would say our dear GB friends. If you don't manage to
> to build the CVS version, and still want to do a  quick test,
> hamlib-1.1.1 should be okay with the FT847. Frank has tested it.
> You may run rigtest and rigctl in the tests/ subdir. Note with 1.1.1,
> you have to modify the C file to specify you rig number.
> Also, if you wanna test without installing Hamlib, you'll have to
> set your LD_LIBRARY_PATH accordingly. Provided topsrc is an env variable
> holding the path of the Hamlib source dir, add
> $(topsrc)/src/.libs:$(topsrc)/yaesu/.libs:$(topsrc)/anyrig/.libs to it.
> Hopefully, this LD_LIBRARY_PATH trick won't be needed in future versions of
> automake/libtool.

On Friday I got our TNC to work :-) Today I'll get to that cable.

> Let me know how far you get. I'll be out of town this week-end, so we'll
> have to postpone the (still unsuccessful)sked to next monday. I'm not very
> used to HF bands, but I'm learning. With my poor conditions (end-fed antenna),
> I've made QSO with 4X this week, and KA1 in CW yesterday night (too bad this
> guy didn't know what QRS means). Exciting sure, but there's room for
> improvements. Once I have work out this, maybe we can establish
> a weekly Hamlib net!

Antenna here at DK0TUX is almost the same as yours with no room on the
roof for improvements.

73, Robert
-- 
Robert Steinhaeusser, DL1NC / N9KBK                         rs...@su...
http://1409.org                                   ro...@st...