Brian Ingerson <[EMAIL PROTECTED]> writes:
[...]
> I wanted to let the programmer decide what a dependency is. For example:
>
> use Inline C => DATA =>
> DEPS => ['./lib/foo.so', './inc/header.h',
> './src/code.c', '-lbar'];
>
> I would keep an MD5 key of each file in the .inl. If anything changed,
> recompile.
>
> BTW, in a release or two, I am not even going to check .inl deps for
> installed modules. In fact I won't even install the .inl. So basically
> these deps go away after you install. I think that's as it should be.
>
> Thoughts?
I think I don't understand DEPS. Doesn't it just say that if any of
these files is changed then recompilation is needed? (Also, I've been
unable to get DEPS to work; does it currently exist?)
But DEPS doesn't solve my problem. Say I say
perl -le 'use Inline C => Config => LIBS => "-lreadline" => DEPS =>
['-lreadline']; use Inline C => q{ char *readline(char *);}; print ::readline("xyz:
");'
Then it doesn't work (I need to link against more libraries). If I
now add the libraries I want:
perl -le 'use Inline C => Config => LIBS => "-lreadline -lcurses -ltermcap" =>
DEPS => [qw/-lreadline -lcurses -ltermcap/]; use Inline C => q{ char *readline(char
*);}; print ::readline("xyz: ");'
then the MD5 checksum of the code still hasn't changed, and none of
the dependencies is newer than the compiled code -- so why should
Inline recompile?
--
Ariel Scolnicov |"GCAAGAATTGAACTGTAG" | [EMAIL PROTECTED]
Compugen Ltd. |Tel: +972-2-5713025 (Jerusalem) \ We recycle all our Hz
72 Pinhas Rosen St. |Tel: +972-3-7658117 (Main office)`---------------------
Tel-Aviv 69512, ISRAEL |Fax: +972-3-7658555 http://3w.compugen.co.il/~ariels
