Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Mednyy <swexru@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1 v3] ubus: new package
Date: Wed, 15 Oct 2014 16:05:06 +0400	[thread overview]
Message-ID: <543E62F2.3010608@gmail.com> (raw)
In-Reply-To: <CAHXCMMKOZ16ePJpq-pvzRTht1RsuTmqpMXSuLTgO7WamP9-GAQ@mail.gmail.com>

Thank you for reviews!

On 10/14/2014 11:22 PM, Samuel Martin wrote:
>> ++
>> + ADD_EXECUTABLE(cli cli.c)
>> + SET_TARGET_PROPERTIES(cli PROPERTIES OUTPUT_NAME ubus)
>> +-TARGET_LINK_LIBRARIES(cli ubus ubox blobmsg_json ${json})
>> ++TARGET_LINK_LIBRARIES(cli ubus ubox blobmsg_json)
> I didn't check in the previous review, but blobmsg_json is provided by
> another project, so either it is a required dependency that should be
> integrated in Buildroot too, or this is an optional dependency and you
> should disable it (something similar to what you've done for json-c,
> but always forcing its option to OFF in the _CONF_OPTS).
>
No, blobmsg_json provided by libubox which already in Buildroot.
>> ++IF(JSONC_FOUND)
>> ++  TARGET_LINK_LIBRARIES(cli ${JSONC_LIBRARIES})
>> ++ENDIF()
> Same here (no if/endif lines). So, ${JSONC_LIBRARIES} can go back with
> the others libs (in the first targte_link_library call.
>
>> +
>> + ADD_SUBDIRECTORY(lua)
>> + ADD_SUBDIRECTORY(examples)
> Also, while checking the upstream project, I noticed that:
> - "-Werror" is added to the cflags.
>   Please remove it, otherwise it may/will fail in a number of build
> configuration.
>   Usually, -Werror is good during the development but bad/PITA for integration.
> - BUILD_EXAMPLES is ON by default, consider disabling it or add an
> option driving it.
>
>> diff --git a/package/ubus/ubus.mk b/package/ubus/ubus.mk
>> new file mode 100644
>> index 0000000..652ab48
>> --- /dev/null
>> +++ b/package/ubus/ubus.mk
>> @@ -0,0 +1,28 @@
>> +################################################################################
>> +#
>> +# UBUS
>> +#
>> +################################################################################
>> +
>> +UBUS_VERSION = 4c4f35cf2230d70b9ddd87638ca911e8a563f2f3
>> +UBUS_SITE = git://nbd.name/luci2/ubus.git
>> +UBUS_LICENSE = LGPLv2.1
>> +UBUS_DEPENDENCIES = json-c libubox
>> +
>> +ifeq ($(BR2_USE_MMU)$(BR2_PACKAGE_LUA_5_1),yy)
> Why BR2_USE_MMU?
Not sure, just took it from libubox.mk which is mandatory dependency.. I
think I must disable it. There is no such requirement.

-- 
_________________________________
Best regards, Mednyy Alexey.

  reply	other threads:[~2014-10-15 12:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-14  9:46 [Buildroot] [PATCH 1/1 v3] ubus: new package Alexey Mednyy
2014-10-14 19:22 ` Samuel Martin
2014-10-15 12:05   ` Alexey Mednyy [this message]
2014-10-15 12:08     ` Samuel Martin
2014-10-14 21:33 ` Arnout Vandecappelle

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=543E62F2.3010608@gmail.com \
    --to=swexru@gmail.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