From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] RFC: Adding Vagrant file for provisioning
Date: Thu, 10 Sep 2015 10:07:27 +0200 [thread overview]
Message-ID: <55F13A3F.2040109@mind.be> (raw)
In-Reply-To: <CA+TH9V=k=0wijd+PaZLi-Zm07EKCWHFSkO+5goQi-jDLD4V0fQ@mail.gmail.com>
On 10-09-15 08:15, Angelo Compagnucci wrote:
> Dear Arnout Vandecappelle ,
>
> 2015-09-10 0:14 GMT+02:00 Arnout Vandecappelle <arnout@mind.be>:
>> On 10-09-15 00:01, Angelo Compagnucci wrote:
>>> This patch adds a Vagrant file to buildroot. With this file
>>> you can provision a complete buildroot developing environment
>>> in minutes on all major platforms.
>>>
>>> Signed-off-by: Angelo Compagnucci <angelo.compagnucci@gmail.com>
>>> ---
>>>
>>> This patch is a tentative approach to add a standard and official
>>> Vagrant file to buildroot. With this file you can setup an isolated
>>> build environment based on Vagrant on all major platforms.
>>>
>>> The file is fairly basic right now, it sets up correct Ubuntu version
>>> to download and install required packages for buildroot.
>>>
>>> I'm open to suggestions and critics!
>>
>> Here goes:
>>
>> If you're already on a platform that runs vagrant, then you have enough to run
>> buildroot as well, so why would you want to put it inside a VM and double your
>> build time? Buildroot really really tries very hard to make sure it runs in any
>> environment, so there should be no need for any of this trickery.
>
> Not true. I know of certain corporate environments in which you have
> to stick on windows, and usually the people working in these
> environment use virtual machines also if buildtime will be longer.
So I was wrong about Vagrant not running on Windows? Oh, now I see. Sorry for
my confusion.
At some point I considered that we should host an official VM image. This is a
lot better then, of course!
> IMHO with a fairly recent computer you will not notice of being inside
> a virtual machine.
Do the test. AFAIK it doubles the build time.
>
> Also having buildroot on mac is not that easy, Vagrant will solve
> these problems brilliantly!
Yep, I didn't think of that either.
Regards,
Arnout
--
Arnout Vandecappelle arnout dot vandecappelle at essensium dot com
Senior Embedded Software Architect . . . . . . +32-478-010353 (mobile)
Essensium, Mind division . . . . . . . . . . . . . . http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium . . . . . BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2015-09-10 8:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-09 22:01 [Buildroot] [PATCH] RFC: Adding Vagrant file for provisioning Angelo Compagnucci
2015-09-09 22:14 ` Arnout Vandecappelle
2015-09-10 6:15 ` Angelo Compagnucci
2015-09-10 8:07 ` Arnout Vandecappelle [this message]
2015-09-10 8:12 ` Angelo Compagnucci
2015-09-10 11:56 ` Nimai Mahajan
2015-09-10 12:13 ` Angelo Compagnucci
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=55F13A3F.2040109@mind.be \
--to=arnout@mind.be \
--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