You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nuttx.apache.org by xi...@apache.org on 2020/03/27 07:42:21 UTC
[incubator-nuttx] branch master updated (ebc6627 -> 4f130d4)
This is an automated email from the ASF dual-hosted git repository.
xiaoxiang pushed a change to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-nuttx.git.
from ebc6627 Bump DEFAULT_TASK_STACKSIZE for the sim
new 2f6d458 sim/README: Mention macOS
new f1a68ab Revert "Revert "README.txt: add MacOS section for flock installation""
new 4f130d4 README.txt: Mention a few tools for macOS
The 3 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
README.txt | 21 +++++++++++++++++++++
boards/sim/sim/sim/README.txt | 17 +++++++++--------
2 files changed, 30 insertions(+), 8 deletions(-)
[incubator-nuttx] 03/03: README.txt: Mention a few tools for macOS
Posted by xi...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
xiaoxiang pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-nuttx.git
commit 4f130d42742f67dc5b4dddece716df5c739038e9
Author: YAMAMOTO Takashi <ya...@midokura.com>
AuthorDate: Fri Mar 27 15:54:20 2020 +0900
README.txt: Mention a few tools for macOS
---
README.txt | 23 ++++++++++++++++++-----
1 file changed, 18 insertions(+), 5 deletions(-)
diff --git a/README.txt b/README.txt
index 338fb3f..0526f5d 100644
--- a/README.txt
+++ b/README.txt
@@ -4,6 +4,7 @@ README
o Environments
- Installing Cygwin
- Ubuntu Bash under Windows 10
+ - Using macOS
o Installation
- Download and Unpack
- Semi-Optional apps/ Package
@@ -388,12 +389,24 @@ Ubuntu Bash under Windows 10
framework like GTK or Qt. So this might be a trip down the rabbit hole.
Using macOS
-----------
- You need install flock from https://github.com/discoteq/flock
- before the build start:
+-----------
+
+ You need to install at least the following tools specific to macOS.
+
+ * flock (used by APPDIR build logic)
+
+ A macOS port is available at: https://github.com/discoteq/flock
+
+ brew tap discoteq/discoteq
+ brew install flock
+
+ If you want to build the sim:
+
+ * Xcode (the native compiler and the rest of the toolchain)
+
+ * ELF toolchain (if you want to build modules for CONFIG_LIBC_MODLIB)
- brew tap discoteq/discoteq
- brew install flock
+ brew install x86_64-elf-gc
INSTALLATION
^^^^^^^^^^^^
[incubator-nuttx] 02/03: Revert "Revert "README.txt: add MacOS
section for flock installation""
Posted by xi...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
xiaoxiang pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-nuttx.git
commit f1a68ab4447a02ce77f174dcd935c36387e41b48
Author: YAMAMOTO Takashi <ya...@midokura.com>
AuthorDate: Fri Mar 27 15:49:28 2020 +0900
Revert "Revert "README.txt: add MacOS section for flock installation""
This reverts commit 884fcb605dd68494ba83da8b9f951f879487014f.
---
README.txt | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/README.txt b/README.txt
index d3b0dfe..338fb3f 100644
--- a/README.txt
+++ b/README.txt
@@ -387,6 +387,14 @@ Ubuntu Bash under Windows 10
Many Linux graphics programs would, however, also require a graphics
framework like GTK or Qt. So this might be a trip down the rabbit hole.
+Using macOS
+----------
+ You need install flock from https://github.com/discoteq/flock
+ before the build start:
+
+ brew tap discoteq/discoteq
+ brew install flock
+
INSTALLATION
^^^^^^^^^^^^
[incubator-nuttx] 01/03: sim/README: Mention macOS
Posted by xi...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
xiaoxiang pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-nuttx.git
commit 2f6d458bcfd0fa75378dc4119e16192b39ac2743
Author: YAMAMOTO Takashi <ya...@midokura.com>
AuthorDate: Fri Mar 27 15:43:47 2020 +0900
sim/README: Mention macOS
---
boards/sim/sim/sim/README.txt | 17 +++++++++--------
1 file changed, 9 insertions(+), 8 deletions(-)
diff --git a/boards/sim/sim/sim/README.txt b/boards/sim/sim/sim/README.txt
index a52e31b..4875d83 100644
--- a/boards/sim/sim/sim/README.txt
+++ b/boards/sim/sim/sim/README.txt
@@ -27,7 +27,7 @@ Description
-----------
This README file describes the contents of the build configurations available
for the NuttX "sim" target. The sim target is a NuttX port that runs as a
-user-space program under Linux or Cygwin. It is a very "low fidelity"
+user-space program under Linux, Cygwin, or macOS. It is a very "low fidelity"
embedded system simulation: This environment does not support any kind of
asynchronous events -- there are nothing like interrupts in this context.
Therefore, there can be no pre-empting events.
@@ -84,8 +84,9 @@ graphical front-end to GDB:
gdb> b user_start
gdb> r
-NOTE: This above steps work fine on both Linux and Cygwin. On Cygwin, you
-will need to start the Cygwin-X server before running ddd.
+NOTE: This above steps work fine on Linux, Cygwin, and macOS.
+On Cygwin, you will need to start the Cygwin-X server before running ddd.
+On macOS, it's probably easier to use lldb instead of gdb.
Issues
^^^^^^
@@ -121,11 +122,11 @@ NuttX heap. The memory management model is exactly the same in the simulation
as in a real, target system. This is good because this produces a higher
fidelity simulation.
-However, when the simulation calls into Linux/Cygwin libraries, it will still
+However, when the simulation calls into the host OS libraries, it will still
use these small simulation stacks. This happens, for example, when you call
into the system to get and put characters to the console window or when you
make X11 calls into the system. The programming model within those libraries
-will assume a Linux/Cygwin environment where the stack size grows dynamically
+will assume the host OS environment where the stack size grows dynamically
and not the small, limited stacks of a deeply embedded system.
As a consequence, those system libraries may allocate large data structures on
@@ -156,9 +157,9 @@ The simulation build is a two pass build:
and then linked with nuttx.rel to generate the simulation program.
NuttX is a POSIX compliant RTOS and is normally built on a POSIX compliant
-host environment (like Linux or Cygwin). As a result, the same symbols are
-exported by both the NuttX domain and the host domain. How can we keep them
-separate?
+host environment (like Linux, Cygwin, or macOS). As a result, the same
+symbols are exported by both the NuttX domain and the host domain. How can
+we keep them separate?
This is done using the special file nuttx-name.dat. This file just contains a
mapping of original function names to new function names. For example, the