Moin Felipe!

Am 25 Aug 06, Felipe T. Dorado schrieb an Maurice Kinal:

 FD> Ok. I have managed to compile everything :)   but for huskybse  :(
 FD> No way.
 FD> And it is the only package still to compile.

Ah, finally i do understand. There is no need to compile huskybse.

Huskybse is just the base for all husky modules like smapi, hpt and so on.

That is because it contains the description of the compilation process and
with the file huskymak.cfg the base configuration for all other husky
software.
It is not an executable software module.

That information can be found in the file README of the huskybse:

++++
This package contains some files common to all packages of the Husky-project.

File/Directory  Description
INSTALL         How to compile, install and use the Husky software. READ THIS!
++++

 FD> Is there a way by which I can see what make expects to find in the
 FD> present dir or the one above it?

Yes. But for huskybse you don't need it.

make use the configuration file "Makefile" in the current
directory by default.

Your error message "no target found" is because there is no
target because there is no Makefile. The error msg is confusing, try this:

$:/usr/src/husky/sm24 # make
make: *** No targets specified and no makefile found.  Stop.
mox:/usr/src/husky/sm24 # make install
$: *** No rule to make target `install'.  Stop.

I think everybody new to compilation got trapped by that.
Thanks for showing us. :-)

But back to your question, you can see what make need if you read the Makefile.

For example check the lines with "include". Here are some lines
where parts of the targets are shown, in this case the install and
uninstall targets.

++++
install: install-h instdyn
        -$(MKDIR) $(MKDIROPT) $(LIBDIR)
        $(INSTALL) $(ISLOPT) $(TARGET) $(LIBDIR)

uninstall:
        -cd $(INCDIR)$(DIRSEP)smapi$(DIRSEP) ;\
++++

The buildup of the Makefile looks confusing at first. But you may find that
some variables are defined by the include of the huskymak.cfg. Somehow the
Makefile is like a shell-script.

 FD> I'd like to  finish this up and get it working

You are close to it. Your next step is to configure the fidoconfig
configuration file. :)

The tool "tparser" should help you with that.

For the husky modules all man files or info files should be installed.
Try "man fidoconfig" or "info fidoconfig".
(I prefer the tool "pinfo" instead of "info").

 FD> to be able to write some instrucctions for other newbies before
 FD> getting into downloading the stuff in th cvs.

Do you want to translate it to your local language?
I have a file containing this:

++++
This file covers all basic questions that you might have if you are new to
the Husky software. Please read those sections that are of interest to you
carefully.
++++

It also covers your actual point of work, the configuration of the husky:

++++
We assume you have now a set of executables of the Husky software. Either
compiled manually, or downloaded in binary form from somewhere. Now - where
do you go from here?

III.1 Creating the configuration file
-------------------------------------

The good news is that all Husky programs only need a single configuration
file. It's filename is "config", and you should put it into the directory
that you have configured as CFGDIR in huskymak.cfg.
++++

Maybe that file is of use for you.

Tschuess

Kai

--- GoldED+/LNX 1.1.4.7