Hola Kai :)

Sábado 26 Agosto 2006 00:32, Kai Richter escribió a Felipe T. Dorado:

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

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

Ah, that's good news for me because I though I was back to square one :)

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

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

Fine. Understood. Thanks.

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

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

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

Yes I read that, and whatever I found in each dir. That sentence up there
maybe clear forsomeon used to compiling but I assure you it is not for one
who is not ;)

 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?

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

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

That much I already knew but this huskymak.cnf confused me a lot.

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

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

 KR> I think everybody new to compilation got trapped by that.

Ah, ok, so it is not me };)

 KR> Thanks for showing us. :-)

Well, it seems it hasbeen of some use. Good.

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

 KR> For example check the lines with "include". Here are some
lines where

Yes, I'm getting into reading these more closely by now.

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

Mmmm, the "somehow" thows me off a bit. But, ok, I'll trust };)

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

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

Yeap. So I've read.

 KR> The tool "tparser" should help you with that.

Good tool that one. I already used it on my setup to have all config in one
file. No errors :)


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

 KR> Do you want to translate it to your local language?

Yeah, sure. And if I find something useful forthe English version I'll suggest.


 KR> I have a file containing this:

 KR> ++++
 KR> This file covers all basic questions that you might have if you are new to

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

 KR> The good news is that all Husky programs only need a single configuration

 KR> Maybe that file is of use for you.

Certainly. I've gone through it quite a few times.
Tell you what, when I manage to have this point working I'll pass the
instructions to other guys and see what they make of them. Some program and
some know nothing of compiling. That will be a good test :)

I'll keep you informed.

Thank you very much for the detailed explanations, Kai  :)

Felipe :)

--- GoldED+/LNX 1.1.5