Re: [Hamlib-developer] what's up?

[Stephane F. <f4...@fr...>]

On Wed, Oct 10, 2001, Robert Steinhäußer wrote:
> My today's copy from the CVS doesn't, though. After some disk scratching,
> it says:
> 
> Making all in lib
> make[1]: Entering directory `/usr/src/hamlib/lib'
> Makefile:166: *** missing separator.  Stop.
> make[1]: Leaving directory `/usr/src/hamlib/lib'
> make: *** [all-recursive] Error 1
> 
> I'm using autoconf 2.52, automake 1.4-p5 and libtool 1.4.1.
> 
	You'll need automake 1.5. Otherwise, you may have a chance
 in regenerating all the .in files.

> Sorry, but I still haven't tested our IC275 and 475 at home. Have to find
> the old self-built interface first and then visit mom (DK3XJ) :)
> 
  Great! She will be happy to see you, but first wait IC275 and 475 
  are added..

> I'm working on my 'Kontakt' project (a GUI frontend for hamlib). Well, now
> I know a lot more about C++ (and differences to C, like using member
> functions for callback purposes... brrr!) and can actually give you a tree
> view of all devices supported by hamlib. A rig can be selected in the list
> (a subclass of QListViewItem now stores the rig_model_t entry), but that's
> about it right now. No actual controls yet, first I want to have the
> config data saved to/retrieved from the config file (hopefully this week).
 
	Let me know if some functions are missing in Hamlib, or if you
  think the design is not appropriate. Accessing the caps/state directly is
  recommanded, instead set_conf/get_conf should be used, provided more
  parameters are declared (yet to be done). Maybe there should be some
  config data file support in Hamlib, regardless the application.
  What do you think?

> If you *really* want to try it: http://sf.net/projects/kontakt -> cvs
> instructions. But please give me some feedback.

  Yep, as soon as I have downloaded the 8MB+ for the qt upgrade...

Cheers,
Stephane - F8CFE