From: Privat <zentrale.at.work@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Gettext / GLib headers in target
Date: Fri, 16 Nov 2007 10:25:17 +0100 [thread overview]
Message-ID: <473D61FD.5040900@googlemail.com> (raw)
In-Reply-To: <473D523C.10206@Kriegisch.name>
Alexander Kriegisch schrieb:
>> Would it be possible have the gettext and header in the target to be
>> able to build tools using the natively?
>
> I do not understand your English, I am afraid. Maybe you can explain
> again (differently) or just add a German version of your question so at
> least some people understand what you want to know.
English:
Sure. I'm using a BR-created Root-FS with a native toolchain. Using this
native toolchain, i would need to be able to build some packages that
rely on the gettext and glib libraries. As far as i can see, the
respective header files are not copied to the target file system. Is
there a way to have this automated, or is the only solution at the
moment copying the files by hand?
Deutsch:
Gerne! Ich benutze ein Root-FS, das mittels BR erzeugt wird und eine
native Toolchain beinhaltet. Mittels dieser Toolchain m?chte ich
in-target einige Pakete kompilieren, die die gettext- und glib-
Bibliotheken nutzen. Die damit notwendigen header files dieser beiden
Bibliotheken werden allerdings von BR nicht ins target-filesystem
kopiert, soweit ich das sehen kann. Kann dieser Vorgang automatisiert
erfolgen, oder besteht im Moment die einzige L?sung darin, die Dateien
von Hand "nachzukopieren"?
Best Regard / Viele Gr?sse
--
Sepp "ZaP" Holzmayr
please reply to:
zentrale.at.work at googlemail.com
watch out for:
www.rocksociety.de
prev parent reply other threads:[~2007-11-16 9:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-16 7:54 [Buildroot] Gettext / GLib headers in target Privat
2007-11-16 8:18 ` Alexander Kriegisch
2007-11-16 9:25 ` Privat [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=473D61FD.5040900@googlemail.com \
--to=zentrale.at.work@gmail.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.