From: Daniel Laird <daniel.j.laird@nxp.com>
To: buildroot@busybox.net
Subject: [Buildroot] xml2-config and xslt-config editing
Date: Wed, 27 Aug 2008 04:57:04 -0700 (PDT) [thread overview]
Message-ID: <19179467.post@talk.nabble.com> (raw)
I have found that I need to edit the xml2-config and xslt-config file after
doing a build.
Much the same as freetype.
Would anyone have any objections to this being done?
$(LIBXSLT_HOOK_POST_INSTALL):
$(SED) "s,^prefix=.*,prefix=\'$(STAGING_DIR)/usr\',g"
$(STAGING_DIR)/usr/bin/xslt-config
$(SED) "s,^exec_prefix=.*,exec_prefix=\'$(STAGING_DIR)/usr\',g"
$(STAGING_DIR)/usr/bin/xslt-config
$(SED) "s,^includedir=.*,includedir=\'$(STAGING_DIR)/usr/include\',g"
$(STAGING_DIR)/usr/bin/xslt-config
$(SED) "s,^libdir=.*,libdir=\'$(STAGING_DIR)/usr/lib\',g"
$(STAGING_DIR)/usr/bin/xslt-config
touch $@
Similar for xml2-config
Finally,
Would it be too dangerous to in Makefile.autotools.in do the above on all
/usr/bin/*-config. Is it better to have this done on a per package basis or
hidden?
--
View this message in context: http://www.nabble.com/xml2-config-and-xslt-config-editing-tp19179467p19179467.html
Sent from the BuildRoot mailing list archive at Nabble.com.
reply other threads:[~2008-08-27 11:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=19179467.post@talk.nabble.com \
--to=daniel.j.laird@nxp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox