Hi Frans,
On Fri, Feb 8, 2013 at 9:24 AM, Frans Meulenbroeks
<fransmeulenbro...@gmail.com> wrote:
> There is also a default base_do_install() that is empty.
> Wouldn't it be more logical if the base_do_install would read:
>
> Currently people using only base, need to add a do_install to their recipe
> but no do_compile (which is somewhat odd; if there is a makefile it seems
> logical to use it for install too).
In my experience when someone manually generates a Makefile for their
project by hand it always includes an 'all' or default target but
almost never includes a 'check', 'uninstall', or 'install' target;
there's a 50/50 chance of it having a 'clean' target of some sort. So
I don't think it's a stretch for the Yocto system to assume a Makefile
doesn't contain an 'install' target. But even if you get lucky and it
does include an 'install' target, what are the chances it has been
designed to properly handle a 'PREFIX' or 'DESTDIR'?
So you're starting with a low probability that a hand-generated
Makefile includes an 'install' target, then coupling that with an even
lower probability that it can flexibly install somewhere other than
/usr/bin or /bin. Yocto's behaviour seems reasonable to me :-)
Best regards,
Trevor
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
