From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] re: new package
Date: Mon, 23 Jan 2012 21:31:09 +0100 [thread overview]
Message-ID: <201201232131.09850.arnout@mind.be> (raw)
In-Reply-To: <20120123111235.58b957ff@skate>
On Monday 23 January 2012 11:12:35 Thomas Petazzoni wrote:
> Le Sun, 22 Jan 2012 14:50:24 +0100,
> "Arnout Vandecappelle (Essensium/Mind)" <arnout@mind.be> a ?crit :
>
> > package/Config.in | 1 +
> > package/re/Config.in | 11 +++++++++++
> > package/re/re.mk | 49 +++++++++++++++++++++++++++++++++++++++++++++++++
>
> Upstream, the package seems to be named 'libre' (the tarball is named
> re-..., but the library is documented as libre on the website),
> shouldn't we use the same name in Buildroot?
I also found libre a more logical name, but since the tar was called
re-$(VERSION).tar.gz I thought to keep that. I hadn't thought of looking
at the official name on the website, though.
I'll make a respin with libre instead of re.
> > +define RE_INSTALL_TARGET_CMDS
> > + $(INSTALL) -m 644 -D $(@D)/libre.so $(TARGET_DIR)/usr/lib/libre.so
> > +endef
>
> I guess that the package build system doesn't use .so versioning?
Not that I could find, no.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
prev parent reply other threads:[~2012-01-23 20:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-22 13:50 [Buildroot] [PATCH 1/2] re: new package Arnout Vandecappelle
2012-01-22 13:50 ` [Buildroot] [PATCH 2/2] baresip: " Arnout Vandecappelle
2012-01-23 10:12 ` [Buildroot] [PATCH 1/2] " Thomas Petazzoni
2012-01-23 20:31 ` Arnout Vandecappelle [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=201201232131.09850.arnout@mind.be \
--to=arnout@mind.be \
--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.