Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Le Bihan <eric.le.bihan.dev@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Makefile for iotivity-1.1.1 build under buildroot
Date: Mon, 24 Jul 2017 20:16:26 +0200	[thread overview]
Message-ID: <20170724181626.GA4226@itchy> (raw)
In-Reply-To: <CAL6UhvSj4kKS4E0VhFSfD+E2_K_ese8r_ubktdBPTotgOQsCRA@mail.gmail.com>

Hi!

On 17-07-24 13:48:16, Linux Edwin K wrote:
> Hi buildroot,
>
> I have done a specific project on buildroot environment and I wanted to add
> *ioTivity-1.1.1* as a /buildroot/package/iotivity/
>
> Either OCF or buildroot were not given official support for iotivity build
> under buildroot.
>
> Since my project completion time is shorter, am finding difficulty to write
> my own *iotivity.mk <http://iotivity.mk>* file.
>
> Will I get help ?

Out of curiosity, I briefly looked at iotivity [1]. It uses Scons as its
build system. So if you want to add a new Buildroot package for
iotivity, you can take package/mongodb/mongodb.mk as an example, as this
package also uses Scons.

Scons is not used directly, as a wrapper script named `auto_build.py` is
provided. It may have to be invoked from IOTIVITY_BUILD_CMDS in the
package Makefile.

I also noticed it relies on some external libraries, like Boost,
tinycbor or gtest. Some are available in Buildroot, others are not. So
you may have to add additional packages for the missing ones and list
them in the package dependencies (surprisingly, depending on the missing
library, it either asks the user to perform the clone manually or does
it on its own when building).

Hope this helps.

[1] https://wiki.iotivity.org/build_for_your_system

Regards,

--
ELB

  reply	other threads:[~2017-07-24 18:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-24  8:18 [Buildroot] Makefile for iotivity-1.1.1 build under buildroot Linux Edwin K
2017-07-24 18:16 ` Eric Le Bihan [this message]
2017-07-27  6:24   ` Linux Edwin K

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=20170724181626.GA4226@itchy \
    --to=eric.le.bihan.dev@free.fr \
    --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