Hello All!

While building i changed PREFIX and CFGDIR location. The result of prefix ~/test was a nice overview which files have been built and it was easy to move them to the final node system. I made a mistake and needed to change the CFGDIR path but the next make run did not rebuild any files?

I did a text search and found there is no CFGDIR in the project root Makefile but i found it in the fidoconfig module Makefile.

Is the FIDOCONFIG environment variable the only way to define the config entry point?

In the long term maybe i'm going to need a hardcoded initial config location.

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)

Hello Kai,

Friday July 14 2023, Kai Richter wrote to All:

While building i changed PREFIX and CFGDIR location. The result of
prefix ~/test was a nice overview which files have been built and it
was easy to move them to the final node system. I made a mistake and needed to change the CFGDIR path but the next make run did not rebuild
any files?

I'll try to reproduce that.

I did a text search and found there is no CFGDIR in the project root Makefile but i found it in the fidoconfig module Makefile.

Is the FIDOCONFIG environment variable the only way to define the
config entry point?

You may define the config path in FIDOCONFIG environment variable or with "-c" command line option when you run some Husky program. If you define both, then the command line option is used.

In the long term maybe i'm going to need a hardcoded initial config location.

Michael

... node (at) f1042 (dot) ru
--- GoldED+/LNX 1.1.5-b20230221
* Origin: Moscow, Russia (2:5020/1042)

Hello Kai,

Friday July 14 2023, Kai Richter wrote to All:

While building i changed PREFIX and CFGDIR location. The result of
prefix ~/test was a nice overview which files have been built and it
was easy to move them to the final node system. I made a mistake and needed to change the CFGDIR path but the next make run did not rebuild
any files?

Fixed.

I did a text search and found there is no CFGDIR in the project root Makefile but i found it in the fidoconfig module Makefile.

Is the FIDOCONFIG environment variable the only way to define the
config entry point?

In the long term maybe i'm going to need a hardcoded initial config location.

If neither "-c" command line option, nor FIDOCONFIG environment variable is defined, then the fidoconfig location is given by CFGDIR and CFGNAME defined in huskymak.cfg during compilation. If CFGNAME is not defined there, "config" is used.

Michael

... node (at) f1042 (dot) ru
--- GoldED+/LNX 1.1.5-b20230221
* Origin: Moscow, Russia (2:5020/1042)

Hello Michael!

18 Jul 23, Michael Dukelsky wrote to Kai Richter:

mistake and needed to change the CFGDIR path but the next make
run did not rebuild any files?

Fixed.

Fetched. But not tested yet. I'll report if done.

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)

Hello Michael!

20 Jul 23, Kai Richter wrote to Michael Dukelsky:

mistake and needed to change the CFGDIR path but the next make
run did not rebuild any files?

Fixed.

Fetched. But not tested yet. I'll report if done.

Sorry, long time no see.

The build script fails on every second run.
For static and dynamic building i prepared huskymak with the dynlib and path adjustment settings.

cd ~/husky
cat mk.static.sh

#!/bin/sh
cp huskymak.stat huskymak.cfg
./build.sh


% ./mk.static.sh
Trying to update huskybse
Trying to update huskylib
Trying to update smapi
Trying to update fidoconf
Trying to update areafix
Trying to update hpt
Trying to update htick
Trying to update hptkill
Trying to update hptsqfix
Trying to update sqpack
Trying to update fidoroute
Trying to update msged
Trying to update util
Trying to update areastat
Trying to update nltools
Already up to date.
[up to date for all above]
diff: invalid option -- Z
usage: diff [-aBbdilpTtw] [-c | -e | -f | -n | -q | -u] [--ignore-case]
[--no-ignore-case] [--normal] [--strip-trailing-cr] [--tabsize]
[-I pattern] [-L label] file1 file2
[more diff useage]

### Config name and/or path has changed. Please run the same command again ###

If i do run the same command again then i can see clang linking many .o files. The last linked are msged then nltools then the msged help compiler reported two times "done".

During this run i didn't noticed any errors.

If i start the mk.static.sh again then i get the same "run again" result as seen above. I tried the build.sh alone and got the same results.

I have no idea where the trigger "config changed" does come from.

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)

Hello Kai,

Tuesday September 19 2023, Kai Richter wrote to Michael Dukelsky:

cp huskymak.stat huskymak.cfg
./build.sh

[...]

diff: invalid option -- Z

Fixed.

If you change CFGDIR and/or CFGNAME in huskymak.cfg and you are asked to run build.sh again, please run it with the -n option (or with the --offline option which implies -n) since you do not want the build.sh script to change huskymak.cfg. See build.sh --help.

Michael

... node (at) f1042 (dot) ru
--- GoldED+/LNX 1.1.5-b20230221
* Origin: Moscow, Russia (2:5020/1042)

Hello Michael!

22 Sep 23, Michael Dukelsky wrote to Kai Richter:

diff: invalid option -- Z

Fixed.

Building works fine. :-)

If you change CFGDIR and/or CFGNAME in huskymak.cfg and you are asked
to run build.sh again, please run it with the -n option (or with the

It looks like it's working without the -n option and that should be normal.

Because the huskymak.cfg is the user controlled configuration file it should not be replaced or changed by the automatic build process. This avoids surprising unwanted behavior.

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)