[Hamlib-developer] Re: CVS tag [Re: Hamlib-1.1.0 released , last check]

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

On Thu, Dec 21, 2000, Frank Singleton wrote:
> 
> Also, will create a yaesu directory and move 
> my common yaesu stuff stuff in there. I am starting to get
> some good structure on common code now, want to leverage
> it as much as possible.
> 
> How does that affect the Makefile stuff (not being an

Looks like a new-backend-HOWTO is on preparation...

Allright, if you want to add the yeasu/ directory,
you'll have to go through the following steps:

* create the yeasu/ directory, if not done already...

* in configure.in, at the very bottom of the file,
  add yeasu/Makefile in the AC_OUTPUT directive so 
  your Makefile will be autogenerated (using automake)

* add the directory name in the Makefile.am to SUBDIRS,
  in the root directory of hamlib. This is needed by the master
  Makefile to know where to recurse into.

* create yeasu/Makefile.am, the easiest way is to clone it from
  an existing backend. Some explanations on the content may be
  interresting. Ask if you want some.

* running make from the hamlib root dir should rebuild configure
  and rerun it. If not, just issue "autoconf", followed by "./configure"
  and that should be it.

> Also, I think there is a missing dependancy on .h
> files. When I edit one , say ft747.h and re-run make
> from the top dir, then he does not see any changes.
> 
  well, it looks like no mkdep is ran automatically.
  you might end up adding it by hand in the Makefile.am,
  while I'm figuring out how to activate automatic dependencies
  (any help welcome!).

-- 
Stephane