> On Jan 18, 2020, at 3:48 PM, Gregory Nutt wrote:
>
>
>> This is not to say that this is a 100% stable development platform. There
>> are still a few dangling, loose ends that I am aware and most likely more
>> that I am not aware of. ... So basic functionality is there, but any real
Hello, all,
I spent that last two days working on the Windows Native build (just a
few hours a day) and I want to report that the Native windows build is
now mostly functional. I can build NuttX directly in a Windows CMD.exe
shell!
As a proof of concept, this says that the Native build is
The Windows Cygwin build is a lot slower but it works. (See my video). My vote
goes to keeping Windows. It keeps Nuttx followers and Windows is, as stated
before, really making effort to support the IoT concept. And its also getting
better in Open Source projects. Also their Cloud (Edge)
On Thu, Jan 16, 2020 at 8:45 AM Gregory Nutt wrote:
> But there
> are a minority of Windows SDK developers that require pure Native
> support, not via some intermediary framework. I don't know the full
> reasoning; I am not an SDK/IDE person. I always believe the reason
> involves Visual
I am for option 3 FIX THE WINDOWS NATIVE SUPPORT
Okay. Let's consider the status quo unacceptable. The status quo being
that Windows Native support is a DIY project and not necessarily ready
for use "out of the box." That brings us back to a binary decision
Remove or Fix (which is easier
+1 FIX THE WINDOWS NATIVE SUPPORT && add a native test environment
-Original Message-
From: Alin Jerpelea [mailto:jerpe...@gmail.com]
Sent: Thursday, January 16, 2020 4:06 AM
To: dev@nuttx.apache.org
Subject: Re: [DISCUSS] Remove Windows Native support?
I am for option 3 FIX THE
What I means the full is that all config must pass the automation
build and run the build system regularly like other host.
Yes, the problem is a circular one. Why is the native build always out
of date? Because it is not tested. Why don't we test it? Because it
is out of date.
There
I would prefer that we keep the ability to build on native Windows. That is
still the most prolific OS and is used heavily in the embedded development
world. Every microcontroller vendor I've worked with seems to support
Windows based tools first and other platforms as an option. Sometimes
Item 2 isn't a good option: a broken build system just give the user a
very bad impression that OS self isn't workable or stable. It's better
that we fully support Windows native or remove from the list at all.
What I means the full is that all config must pass the automation
build and run the
I am for option 3 FIX THE WINDOWS NATIVE SUPPORT
An initial effort is worth updating the support and I we can add a native
test environment to be sure that it builds daily
Alin
On Thu, Jan 16, 2020 at 12:22 PM Nathan Hartman
wrote:
> On Wed, Jan 15, 2020 at 8:25 PM Gregory Nutt wrote:
>
> > I
On Wed, Jan 15, 2020 at 8:25 PM Gregory Nutt wrote:
> I would like to open a discussion for 72 hours then call a vote. The
> topic is "Should we remove Windows native build support?"
>
> What is the Windows native build? Is is a build option that supports
> building NuttX in a pure Windows
Hi Justin,
On 1/16/20, Justin Mclean wrote:
> Hi,
>
> The linux bash shell works on windows 10 (via WSL) these days. Is that an
> option?
>
Yes, it is already supported by default:
https://acassis.wordpress.com/2018/01/10/how-to-build-nuttx-on-windows-10/
Should be nice if you could try it. I
Item 2 isn't a good option: a broken build system just give the user a
very bad impression that OS self isn't workable or stable. It's better
that we fully support Windows native or remove from the list at all.
What I means the full is that all config must pass the automation
build and run the
Hi,
The linux bash shell works on windows 10 (via WSL) these days. Is that an
option?
Justin
I would like to open a discussion for 72 hours then call a vote. The
topic is "Should we remove Windows native build support?"
It occurs to me that there are really three options:
1. Remove all support for Windows native builds
2. Keep the seldom unverified Window native build, just as
I would like to open a discussion for 72 hours then call a vote. The
topic is "Should we remove Windows native build support?"
It occurs to me that there are really three options:
1. Remove all support for Windows native builds
2. Keep the seldom unverified Window native build, just as we
I would like to open a discussion for 72 hours then call a vote. The
topic is "Should we remove Windows native build support?"
There have been several SDKs build for Windows native in the past. One
obstacle for the Windows native build is that it requires a Windows
native port of
I would like to open a discussion for 72 hours then call a vote. The
topic is "Should we remove Windows native build support?"
What is the Windows native build? Is is a build option that supports
building NuttX in a pure Windows environment such as from a Windows IDE
or from CMD/PowerShell
18 matches
Mail list logo
