From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH 1/2] gtk2: Disable rebuilds of pregenerated files
Date: Thu, 4 Dec 2014 17:29:17 +0100 [thread overview]
Message-ID: <20141204162917.GE16181@pengutronix.de> (raw)
In-Reply-To: <547C5CF8.6030303@gr13.net>
On Mon, Dec 01, 2014 at 01:20:08PM +0100, Enrico Weigelt, metux IT consult wrote:
> On 27.11.2014 11:43, Markus Pargmann wrote:
> > As we don't want to use tools outside of ptxdist, we should avoid
> > regenerating generated files within the gtk sources. For example
> > gtk-update-icon-cache may fail with different non-compatible versions.
>
> hmm, pragmatic, but not really optimal.
> the optimal way would be fixing these tools to be usable for
> crosscompilng. yes, I know, that could be a huge amount of work :(
>
> by the way: I'm really in favour of _always_ regenarating the whole
> build script stuff (autotools+friends) ... had more than enough
> trouble w/ them in recent years.
That's not good either. A lot of packages are missing files needed to run
autotools sucessfully or require older autotols versions.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2014-12-04 16:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-27 10:43 Markus Pargmann
2014-11-27 10:43 ` [ptxdist] [PATCH 2/2] gtk2: Remove leftover GTK2CORE Markus Pargmann
2014-11-27 13:59 ` Michael Olbrich
2014-12-01 12:20 ` [ptxdist] [PATCH 1/2] gtk2: Disable rebuilds of pregenerated files Enrico Weigelt, metux IT consult
2014-12-04 16:29 ` Michael Olbrich [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=20141204162917.GE16181@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox