From: Nicolas Serafini <nicolas.serafini@sensefly.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] exiv2: new package
Date: Thu, 6 Nov 2014 16:06:52 +0100 [thread overview]
Message-ID: <545B8E8C.7020807@sensefly.com> (raw)
In-Reply-To: <20141106160141.61314607@free-electrons.com>
Dear THomas,
Ok I will fix all this.
I was a little to fast with the v2 of the Patch so do not take into account.
Thanks,
Nicolas
Le 06. 11. 14 16:01, Thomas Petazzoni a ?crit :
> Dear Nicolas Serafini,
>
> On Thu, 6 Nov 2014 15:18:04 +0100, Nicolas Serafini wrote:
>
>> Ok I fix this.
>> I have not found the rule for maximum column in Config.in and *.mk files
>> in the manual. Maybe we should add.
>
> Feel free to submit a patch :-)
>
>>>> +ifeq ($(BR2_PACKAGE_EXIV2_COMMERCIAL),y)
>>>> +EXIV2_CONF_OPTS += --enable-commercial --disable-nls --disable-lensdata
>>>> +endif
>>>
>>> Why --disable-nls here? It is already passed automatically by the
>>> package infrastructure when locale support is not available.
>>>
>>> Maybe a comment about why --disable-lensdata is passed when the
>>> commercial license is used would be useful.
>>
>> The --disable-lensdata disable an included Nikon lens database for
>> conversion to readable lens name and this database is free use only in
>> non-commercial projects.
>
> This is *bad*. It's not because you use the GPLv2 version of the
> library that you're not making a commercial product. So please add a
> separate Config.in option for this lensdata, disabled by default, with
> a warning in the Config.in help text.
>
>> For the --disable-nls, I don't know exactly why it's requested in
>> commercial version.
>> This is what is specified in the README file.
>
> Then please add a comment above the usage of --disable-nls to explain
> that.
>
>>>> +ifeq ($(BR2_PACKAGE_EXIV2_XMP),y)
>>>> +EXIV2_CONF_OPTS += --with-expat=$(STAGING_DIR)/usr/lib
>>>
>>> Maybe --enable-xmp here?
>>
>> It works in both cases because XMP is automatically enabled if expat is
>> found.
>
> If --enable-xmp exists, then I would prefer to see it explicitly used.
>
> Thanks,
>
> Thomas
>
prev parent reply other threads:[~2014-11-06 15:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-05 14:30 [Buildroot] [PATCH 1/1] exiv2: new package Nicolas Serafini
2014-11-06 7:30 ` Thomas Petazzoni
2014-11-06 14:18 ` Nicolas Serafini
2014-11-06 15:01 ` Thomas Petazzoni
2014-11-06 15:06 ` Nicolas Serafini [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=545B8E8C.7020807@sensefly.com \
--to=nicolas.serafini@sensefly.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