Re: gar.lib.mk still wrong

[guenther <guenther rudersport de>]

> > I know you talked to Joseph about these external dependencies before,
> > and I do have an idea to implement automatic, conditional build of them
> > (supporting explicit disabling of external deps). Which should make you
> > happy, once I got around to implementing this. :)
> 
> Oh don't misunderstand me. I am happy now :) garnome is a terriic platform
> and build system. I just try and save some time since other applications
> benefit from many common libraries and applications (e.g. dbus, hal, etc).

Thanks. :)

Also, don't worry, I am not misunderstanding you. Quite the contrary --
I do see your point about (some) external deps. We had to implement some
hacks in the past to support for example a system Mozilla, and that's
exactly where I am aiming at with my plans. I want to unify such hacks,
make it more easy to understand, and configurable. Also I want to extend
this mechanism once implemented to more external deps.

The exact details are not done yet, but I got a picture of it in my
head. ;)  Just let's reschedule this part of the discussion. You will be
noticed early, for some smoke-testing. And the result should make you
(even more) happy. ;)


> Trying to figure out library versions, especially for packages that don't
> use pkgconfig is very hard. Not worth the effort if you ask me.
> 
> 
> > I would like to see how this works out in your case, and I definitely
> > will ping you for some testing. :)  If you want to discuss such issues
> > in a more interactive way, feel free to join us on IRC.
> 
> I think the best approach would be to have a user config file only for use
> by those who WANT to bypass files or libraries. I don't think trying to make
> garnome too smart is worthwhile.

Agreed. The default should be pretty much predictable (can you say
support?) and it isn't worth the effort for some lightweight thingies
like intltool anyway.


> > char *t="\10pse\0r\0dtu\0  ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
> > main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
> > (c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
> 
> I finally compiled your sig. Very cute :)

Thanks. :)  Now, the your-weight-in-beer question is, which commonly
known algorithm does it implement? ;-)

(Btw, I found that one sometimes needs to explicitly run it with a
newline added, like './sig; echo', to actually get the result not
overwritten by the shell prompt.)

  guenther


-- 
char *t="\10pse\0r\0dtu\0  ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}