From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] liberation: add support for custom target directory
Date: Fri, 14 Jan 2011 18:12:54 +0100 [thread overview]
Message-ID: <20110114181254.3e773a18@surf> (raw)
In-Reply-To: <LF0UP9$6C050B5F0CF790CC5FFC45AB98AF886D@aruba.it>
On Fri, 14 Jan 2011 17:48:45 +0100
"Luca Ceresoli" <list@lucaceresoli.net> wrote:
> > That could be one solution. The other solution would be to hide this
> > from the user, i.e an unvisible configuration option to select the
> > installation location of the fonts (i.e ? fonts in subdirs ? or ? all
> > fonts in /usr/share/fonts ?). ? fonts in subdirs ? would be the
> > default, and ? all fonts in /usr/share/fonts/ ? would be selected by
> > Nano-X/Microwindows. This way, the user wouldn't have to worry about
> > the installation location of fonts.
>
> That would not be enough in my case.
> I don't use Nano-x/Microwin, my setup is based on qt + directfb + freetype.
> I am not sure which of these components needs fonts in a specific dir,
> but if fonts are in subdirs they won't be found.
Sorry, but I do not understand why it wouldn't be enough. If you need
all the fonts in a single directory, you would just select the ? all
fonts in /usr/share/fonts ? case, and that would work, no ?
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-01-14 17:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-12 13:51 [Buildroot] [PATCH 1/2] liberation: add support for custom target directory Luca Ceresoli
2011-01-14 8:47 ` Thomas Petazzoni
2011-01-14 16:48 ` Luca Ceresoli
2011-01-14 17:12 ` Thomas Petazzoni [this message]
2011-01-15 12:23 ` Luca Ceresoli
-- strict thread matches above, loose matches on Subject: below --
2011-01-12 11:03 Daniel Nyström
2011-01-12 11:08 ` Thomas Petazzoni
2011-01-12 13:14 ` Daniel Nyström
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=20110114181254.3e773a18@surf \
--to=thomas.petazzoni@free-electrons.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.