| 1 |
On 03/07/2011 07:46 PM, solar wrote: |
| 2 |
> On Mon, 2011-03-07 at 14:50 +0100, Martin Gysel wrote: |
| 3 |
>> Hi there |
| 4 |
>> |
| 5 |
>> I'm looking for a 'good' INSTALL_MASK file/definition to use with my |
| 6 |
>> embedded system. As the flash on the boards is rather small I only want |
| 7 |
>> to have the really required files on it. |
| 8 |
>> Can anyone share his INSTALL_MASK? |
| 9 |
>> |
| 10 |
>> Thanks in advance |
| 11 |
>> Martin |
| 12 |
> For a read-only compat flash based system and ~10 or so pkgs. I've used |
| 13 |
> *.a *.o *.la /usr/include *.pc *.pyc *.pyo *.example *.sample |
| 14 |
> |
| 15 |
> Clearly you can nail it down abit more for your own needs. But for mine |
| 16 |
> that was fairly good to grab the majorituy of the bloat. |
| 17 |
> |
| 18 |
|
| 19 |
Related to this... Does anyone know if the PKG_INSTALL_MASK functionality is |
| 20 |
broken? It seems to function exactly the same as INSTALL_MASK. The make.conf |
| 21 |
man page says PKG_INSTALL_MASK applies only when creating a binary package. |
| 22 |
|
| 23 |
I'm a relative newbie, but my thinking (consistent with my understanding of the |
| 24 |
docs and wisdom gleaned from this list) was to maintain a cross development tree |
| 25 |
on my build host with everything installed, including all the build deps |
| 26 |
(libraries, header files, etc), while at the same time building binary packages |
| 27 |
for what will go onto the target filesystem, using PKG_INSTALL_MASK to filter |
| 28 |
out unwanted header files, etc from the binary packages. Then I can create my |
| 29 |
lean target filesystem from the binary packages with the |
| 30 |
'--root=/target/filesystem' emerge option. But PKG_INSTALL_MASK seems to apply |
| 31 |
to my development tree as well. Am I missing anything? |
| 32 |
|
| 33 |
Thanks, |
| 34 |
Mike |
Archives