On Mon, Oct 18, 2010 at 4:42 AM, steve donovan
<[email protected]> wrote:
> On Mon, Oct 18, 2010 at 2:14 AM, Fabio Mascarenhas <[email protected]>
> wrote:
>> Actually the original semantics relied on post_install being run after
>> everything was in its final place. :-)
>
> That makes sense - was certainly my understanding when reading the code.
>
> Alexander would like a pre_install hook as well; I have an
> experimental implementation in my clone repo. There the semantics
> would be: run after the stage has been set, i.e. dependencies
> resolved, archive expanded.
>
> Perhaps a person wants to resolve external dependencies directly, etc.
> Although we still need to strengthen that feature. In discussion
> with Gunnar about the infamous moving-header-file problem in Linux,
> this seemed like a workable idea
>
> external_dependencies = {
> FOO = {
> header = 'foo.h;foo/foo.h'
> }
> }
If I'm reading my own code correctly, right now if one does this:
external_dependencies = {
FOO = {
header = { 'foo.h', 'foo/foo.h' }
}
}
it will try each of them in turn and succeed if any of them match, right?
The only problem is that it won't setup FOO_INCDIR as
/usr/include/foo/ if the second match was found (however, it isn't
obvious that this should be the behavior, as there are programs that
do things like #include <SDL/SDL_mixer.h>).
-- Hisham
_______________________________________________
Luarocks-developers mailing list
[email protected]
http://lists.luaforge.net/cgi-bin/mailman/listinfo/luarocks-developers
