| Summary: | Improve iconv support for external toolchain based builds | ||
|---|---|---|---|
| Product: | buildroot | Reporter: | Ilyas Gasanov <torso.nafi> |
| Component: | Other | Assignee: | unassigned |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | enhancement | CC: | buildroot |
| Priority: | P5 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Host: | Target: | ||
| Build: | |||
|
Description
Ilyas Gasanov
2016-10-06 15:56:35 UTC
There is already a Buildroot option to copy gconv modules to the target, it just seems you missed it. In the toolchain menu, when a glibc toolchain is used, you have: [*] Copy gconv libraries () Gconv libraries to copy If you leave the second option empty, all gconv modules are copied to the target. Otherwise, if it's non-empty, only the specified list of gconv modules are copied. I've just tested again today, leaving the list empty. Indeed, all gconv modules are copied, and a simple C program that converts an UTF-8 string to CP1251 using iconv_open() / iconv() works just fine on the target. The iconv binary itself is however indeed not copied. Maybe we should add an option to copy additional binaries from the toolchain to the target? Could you submit such a patch? |