incubator-nuttx/libs/libxx
Lee Lup Yuen 6cad7e9582 arm, arm64, xtensa, libxx: Change sed -r to sed -E to support macOS
When we build NuttX on macOS, it shows many `sed` messages (and the build still completes successfully):

```text
$ tools/configure.sh pinephone:nsh
$ make
sed: illegal option -- r
```

This is due to the Makefiles executing `sed -r` which is not a valid option on macOS.

This PR proposes to change `sed -r` to `sed -E` because:

- `sed -E` on macOS is equivalent to `sed -r` on Linux

- `sed -E` and `sed -r` are aliases according to the GNU `sed` Manual

- `sed -E` is already used in nuttx_add_romfs.cmake, nuttx_add_symtab.cmake and process_config.sh
2023-10-10 11:36:32 +03:00
..
libcxxmini libs/libxx: remove redundant code 2023-05-03 19:54:19 +08:00
.gitignore build: add initial cmake build system 2023-07-08 13:50:48 +08:00
0001-uClibcxx-basic_definitions-fix-GCC-specific-definiti.patch libxx:uClibcxx:fix-GCC-specific-definitiion error 2021-08-31 11:23:29 +08:00
0001-uclibxx-use-overload-constructor-of-filebuf-ostream.patch libxx:uclibxx: add patch use overload constructor of filebuf & ostream 2022-01-24 23:26:59 +08:00
CMakeLists.txt build: add initial cmake build system 2023-07-08 13:50:48 +08:00
Kconfig libxx: Use gnu++20 option only if using libcxx 2023-10-05 13:09:20 +08:00
Makefile Minor style clean up 2023-01-28 19:53:20 +02:00
README.txt libxx: Stop mentioning libs not integrated with this version of libxx 2020-10-26 22:07:39 -07:00
__config_site libcxx: Remove exiting patches and update libcxx version to 15.0.7 2023-09-24 08:40:10 +03:00
etl.defs treewide: add DOWNLOAD variable as unification of curl call 2023-03-08 17:05:05 +08:00
libcxx.cmake libcxx: Remove exiting patches and update libcxx version to 15.0.7 2023-09-24 08:40:10 +03:00
libcxx.defs arm, arm64, xtensa, libxx: Change sed -r to sed -E to support macOS 2023-10-10 11:36:32 +03:00
libcxxabi.cmake libcxx: Remove exiting patches and update libcxx version to 15.0.7 2023-09-24 08:40:10 +03:00
libcxxabi.defs libcxx: Remove exiting patches and update libcxx version to 15.0.7 2023-09-24 08:40:10 +03:00
libcxxmini.cmake build: add initial cmake build system 2023-07-08 13:50:48 +08:00
libcxxmini.defs libxx: Move the partial c++ abi implementation to libcxxmini sub folder 2021-08-31 06:52:10 -03:00
system_configuration.h libc/wchar: remove unnecessary config 2022-07-27 00:36:49 +08:00
uClibc++.defs Don't download tarballs if a local git repo found 2022-12-05 10:47:36 +01:00

README.txt

libs/libxx/README.txt
^^^^^^^^^^^^^^^^^^^^^

This directory contains three C++ library:

 - A fragmentary C++ library that will allow to build only the simplest of
   C++ applications. In the deeply embedded world, that is probably all
   that is necessary.

   At present, only the following are supported here:

     - void *operator new(std::size_t nbytes);
     - void operator delete(void* ptr);
     - void operator delete[](void *ptr);
     - void __cxa_pure_virtual(void);
     - int __aeabi_atexit(void* object, void (*destroyer)(void*),
                          void *dso_handle);
     - int __cxa_atexit(__cxa_exitfunc_t func, FAR void *arg,
                        FAR void *dso_handle);

   This implementation is selected when neither of the following
   two options are enabled.

 - LLVM "libc++" C++ library (http://libcxx.llvm.org/)
   This implementation is selected with CONFIG_LIBCXX=y.

 - uClibc++ C++ library (http://cxx.uclibc.org/)
   This implementation is selected with CONFIG_UCLIBCXX=y.

operator new
------------

  This operator should take a type of size_t.  But size_t has an unknown underlying
  type.  In the nuttx sys/types.h header file, size_t is typed as uint32_t
  (which is determined by architecture-specific logic).  But the C++
  compiler may believe that size_t is of a different type resulting in
  compilation errors in the operator.  Using the underlying integer type
  instead of size_t seems to resolve the compilation issues. Need to
  REVISIT this.

  Once some C++ compilers, this will cause an error:

    Problem:     "'operator new' takes size_t ('...') as first parameter"
    Workaround:  Add -fpermissive to the compilation flags