All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ivan Kuten <ivan.kuten@promwad.com>
To: buildroot@busybox.net
Subject: [Buildroot] PATCH [1/2] try2: make Makefile.autotools.in not to use hardcoded x11r7 name when patching
Date: Sat, 29 Sep 2007 02:51:28 +0300	[thread overview]
Message-ID: <46FD9380.9090905@promwad.com> (raw)
In-Reply-To: <20070928224019.GG20951@aon.at>

Bernhard Fischer ?????:
> 
> One nice example that, if it is handled properly by the autotools.in is
> package/gmp or mpfr for that matter.
> 
> This package shows nicely what the autotools.in should provide in the
> long run:
> - downloading a PATCH_FILE to the dl/
> - patching package/$name/$name$version
>   or 
>   patching package/$name/$version
>   or 
>   patching package/$name/$($(name)_patch_regex)
>   or the like
> - in configure, honor PREFERRED_LIB_FLAGS et al
> - $(STRIP) the target, perhaps. Distinguish between binaries and libs
> - optionally install headers if BR2_HAVE_HEADERS
> - package-specific additional {C,LD,CPP,...}FLAGS
> - package-specific additional configure-opts
> - knowledge if both staging and target or only one of these should be
>   populated with libs/binaries
> 

I'll try to follow this but a bit later, now my priority is  directfb/x11r7/gtk+ running on ARM.
I'll post a bunch of patches related to selecting gtk+ depends on directfb or on x11r7.

Best regards,
Ivan
--------------------------------
Embedded Linux engineer,
Promwad Company: http://www.promwad.com/
Homepage : http://www.ivankuten.com/
--------------------------------

      reply	other threads:[~2007-09-28 23:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-28 21:23 [Buildroot] PATCH [1/2] make Makefile.autotools.in not to use hardcoded x11r7 name when patching Ivan Kuten
2007-09-28 20:36 ` Bernhard Fischer
2007-09-28 23:25   ` [Buildroot] PATCH [1/2] try2: " Ivan Kuten
2007-09-28 22:40     ` Bernhard Fischer
2007-09-28 23:51       ` Ivan Kuten [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=46FD9380.9090905@promwad.com \
    --to=ivan.kuten@promwad.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.