Hi Christopher, Andreas,
> > I could install all my supporting files in @lib/ in the picolisp
> > installation directory.
> That is one way to do it. Alex usually does it this way afaik.
I would not store application-specific stuff under @lib/, but it is true that on
production servers I
all includes from relative paths.
Best regards,
beneroth
- Original Message -
From: Christopher Howard [mailto:christopher.how...@qlfiles.net]
To: picolisp@software-lab.de
Sent: Sat, 02 Sep 2017 07:47:42 -0800
Subject: Installation / Load Paths
Hi, what is the customary way PicoLisp prog
Hi, what is the customary way PicoLisp programmers deal with load path
issues when trying to install a completed program onto a Gnu/Linux
system? My program has two *.l files. What I wanted to do was:
- Put the *.l files in $(PREFIX)/share/programname/
- Have a bash or picolisp script in
