Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Replace libev with libuv
Date: Sun, 20 Jul 2014 01:12:57 +0200	[thread overview]
Message-ID: <20140719231257.GO3593@free.fr> (raw)
In-Reply-To: <CALoSW642aRZZ9koGitrGTxZ0hjpJO_9nOa5fopgkPnCrnBwM6g@mail.gmail.com>

Nimai, All,

Please, do *not* top-post. Reply in-lined, like I do below...

On 2014-07-19 09:40 -0400, Nimai Mahajan spake thusly:
> Ahh yes so I did ... sorry, stupid mistake. I will use the latest
> tree. cgit web should show all the latest commits since that just
> reflects the git repo correct?

There is a configuration glitch that makes cgit not show all commits.
Compare:
    http://git.buildroot.org/buildroot
    http://git.buildroot.org/buildroot/

The former (without the ending '/') is always up-to-date, while the
latter (with the ending '/') often lags behind, by up to a few days.

> I will use that. I thought the <at> was
> some special BR syntax I'd never seen before.

Nope, that's probably your mailer trying to be too smart, and replacing
all '@' sy,mbols with '<at>' in an attempt to thwarte spammers from
harvesting email addresses.

> Thanks Yann. Hopefully I
> will be able to contribute some new packages in the future after
> learning the syntax about all the different make types.

Do not hesitate to post new packages! Reviews are here to catch problems
in the submissions, and to direct the submitter to the adequate
ressources to fix potential issues.

A good way to add a new package in Buildroot is to:
  - look at the manual: http://buildroot.net/downloads/manual/manual.html
  - look at existing packages

> Slightly off topic question but what would be your recommendation
> about taking an existing package compiled for and written for a
> regular Linux host (i.e. Mint) and integrating it into Buildroot?
> Convert the traditional Makefile into CMake? Autotools? We have a lot
> of code with traditional Makefiles that need to be integrated into an
> embedded Buildroot environment. Thanks.

Well, it all depends. Buildroot can handle a few common, generic build
systems and types of packages, as you'll see in the manual ;-) :
  - autotools,
  - cmake
  - python
  - lua
  - perl

But it also handles packages with a specific build system, such as plain
Makefiles.

So, it is not required to convert packages to include them in Buildroot.

Regards,
Yann E. MORIN.

> On Sat, Jul 19, 2014 at 9:20 AM, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> > Nimai, All,
> >
> > On 2014-07-19 08:51 -0400, Nimai Mahajan spake thusly:
> >> I got it. Gustavo, took a slightly different approach but this works
> >> (idea taken from sdl.mk, which also has a broken build process):
> >>
> >> LIBUV_VERSION = v0.11.26
> >> LIBUV_SITE = $(call github,joyent,libuv,$(LIBUV_VERSION))
> >> LIBUV_DEPENDENCIES = host-pkgconf
> >> LIBUV_INSTALL_STAGING = YES
> >> LIBUV_AUTORECONF = YES
> >> LIBUV_LICENSE = BSD-2c, BSD-3c, ISC, MIT
> >> LIBUV_LICENSE_FILES = LICENSE
> >>
> >> # Tweaked autogen.sh
> >> #define LIBUV_FIXUP_AUTOGEN
> >> #    echo "m4_define([UV_EXTRA_AUTOMAKE_FLAGS], [serial-tests])" >$(
> >> <at> D) m4/libuv-extra-automake-flags.m4
> >> #endef
> >
> > Oh, it looks like you really have a broken (utterly broken!) tree.
> > How did you get that  $( <at> D)  stuff? Did you by chance copy-paste
> > the patch from your mailer and applied it manualy?
> >
> > Please, try the latest Buildroot tree, it should be OK.
> >
> > Regards,
> > Yann E. MORIN.
> >
> > --
> > .-----------------.--------------------.------------------.--------------------.
> > |  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
> > | +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
> > | +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
> > | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
> > '------------------------------^-------^------------------^--------------------'

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

      reply	other threads:[~2014-07-19 23:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-18 12:48 [Buildroot] Replace libev with libuv Nimai Mahajan
2014-07-18 13:12 ` Gustavo Zacarias
     [not found]   ` <CALoSW64Uisj3oLvPVKZ1nQXgCTEnt1yLMqV+Gy7aK4U=Q9FcUA@mail.gmail.com>
2014-07-18 13:32     ` Gustavo Zacarias
2014-07-18 14:02       ` Nimai Mahajan
2014-07-18 20:26         ` Gustavo Zacarias
2014-07-18 23:36         ` Nimai Mahajan
2014-07-19 12:42           ` Nimai Mahajan
2014-07-19 13:18             ` Yann E. MORIN
2014-07-19 12:51           ` Nimai Mahajan
2014-07-19 13:20             ` Yann E. MORIN
2014-07-19 13:40               ` Nimai Mahajan
2014-07-19 23:12                 ` Yann E. MORIN [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=20140719231257.GO3593@free.fr \
    --to=yann.morin.1998@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