Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] cutelyst: new package
Date: Wed, 18 Jul 2018 15:35:52 +0200	[thread overview]
Message-ID: <20180718153552.6b91b361@windsurf> (raw)
In-Reply-To: <CACo8zOfCUVXp2AGbcrFDeCvaeQGNv9_4rdsr6imRo+YYJN6iyw@mail.gmail.com>

Hello,

On Wed, 18 Jul 2018 10:24:53 -0300, Daniel Nicoletti wrote:

> > This way, it is clear that it is a new iteration, and we know what has
> > changed since the previous iteration.  
> Ok, I'm not very used to send patches with format-patch/send-email

No problem at all, it's OK to begin with some topics and learn more.
We're happy with having contributions from newcomers and share what we
believe are best practices to contribute to Buildroot (note that those
best practices also apply to a number of other embedded Linux related
open-source projects: Linux kernel, U-Boot, etc.).

> > You forgot to add an entry to the DEVELOPERS file, so I've added that.  
> Hmm speaking of that, do I need to be subscribed to this buildroot list?
> It's quite high traffic, so if I can subscribe/update package/unsubscribe
> it would work better for me.

You can also remain subscribed all the time, but disable mail delivery
(go to the mailman page, you can adjust your subscription options).
This way, you don't receive e-mails from the list, but you can post to
the list without subscribing/unsubscribing each time.


> > This is because it needs SSL support in Qt. So I've added a "select
> > BR2_PACKAGE_OPENSSL" to make sure SSL support is present in Qt.  
> hmm strange, I added a bunch of ifdefs to cutelyst for it to build without
> SSL support but I guess I missed some, will try again. I guess in the
> spirit of buildroot images trying to be minimal it could be a good thing.

Just do a minimal build with just qt5+cutelyst, and openssl disabled
(you will have to remove the select BR2_PACKAGE_OPENSSL line from
cutelyst/Config.in of course). You'll see the build fail.

> > I've fixed those three issues, and applied your patch. Once again,
> > thanks for your contribution!  
> You welcome, loving this project :)

Thanks for your contribution!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-07-18 13:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-17 20:46 [Buildroot] [PATCH] cutelyst: new package Daniel Nicoletti
2018-07-18 10:59 ` Thomas Petazzoni
2018-07-18 13:24   ` Daniel Nicoletti
2018-07-18 13:35     ` Thomas Petazzoni [this message]
2018-07-18 15:20   ` Thomas Petazzoni
2018-07-19 13:40     ` Daniel Nicoletti
  -- strict thread matches above, loose matches on Subject: below --
2018-07-16 20:49 Daniel Nicoletti
2018-07-17  7:01 ` Thomas Petazzoni
2018-07-17 13:23   ` Daniel Nicoletti
2018-07-17 14:08     ` Thomas Petazzoni

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=20180718153552.6b91b361@windsurf \
    --to=thomas.petazzoni@bootlin.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