[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: a library knowing its whereabouts?
- From: Asko Kauppi <asko.kauppi@...>
- Date: Thu, 6 Jan 2005 18:31:29 +0200
Yes, this is the approach that will work with today's system.
However, I was thinking something along the lines of filling '...' (now
empty), or generally not requiring to browse the 'package.path' within
the module. Even if I'd set LUA_CPATH, Hamster needs to be functional
also in the general scenario (multiple paths to look into).
I think this will apply to any libraries having add-on files with them,
not just for Hamster.
6.1.2005 kello 17:05, Tomas kirjoitti:
On Thu, 6 Jan 2005, Asko Kauppi wrote:
I know.. you'll be saying use CPATH blahblah.. sure. Only, if my
Makefile says '-l Tools/Hamster/hamster' then what? Also to avoid
potential name clashes of subscript files, it would be better to look
straight in the right dir, imho.
Your Makefile could set LUA_CPATH and stay using '-l hamster'.
It will give the same effect, don't you think?