[Buildroot] [PATCH] Add package fribidi

[Peter Korsgaard <jacmet@uclibc.org>]

>>>>> "Murat" == Murat Demirten <mdemirten@yh.com.tr> writes:

 Murat> Hi Peter,

 Murat> There is no information about toolchain or localization
 Murat> requirements. But I just look at the source code and it seems
 Murat> that? this library can be compiled in all the cases, there is no
 Murat> special requirements.

OK, good - I didn't actually check, just expected so because of the
unicode handling.

 Murat> We need a custom install step because we don't want to see other
 Murat> than the library itself on the target.

 Murat> But in some cases, maybe fribidi and fribidi-config binary
 Murat> required by someone else on target. So, keeping these binaries
 Murat> in target usr/bin and giving the possibility to remove with
 Murat> standard postbuild script mechanism will be fine (Is there any
 Murat> hints to not install header files on the target?).

 Murat> What do you think about? Is there any policy for the packages
 Murat> which provides useful libraries and some binaries rarely need on
 Murat> target? Do we have to put all the binaries in target too?
 Murat> Sometimes these types of binaries not prepared for running on
 Murat> the target (like navit->maptool). Putting this binaries only to
 Murat> staging area keeps the target clean but I see that, there must
 Murat> be a policy, we can't put custom binary install logic for every
 Murat> single package.

Buildroot already cleans up header files and so on if not wanted on a
global level (see target-finalize).

For optional binaries and similar, it is typically handled by a sub
option in the package you can enable if you want them.

-- 
Bye, Peter Korsgaard