This website requires JavaScript.
Explore
Help
Sign In
MirrorSave
/
nodemcu-firmware
mirror of
https://github.com/nodemcu/nodemcu-firmware.git
Watch
1
Star
0
Fork
You've already forked nodemcu-firmware
0
Code
Issues
Packages
Projects
Releases
Wiki
Activity
9e08be7b28
nodemcu-firmware
/
sdk-overrides
/
include
/
mem.h
4 lines
71 B
C
Raw
Normal View
History
Unescape
Escape
Major cleanup - c_whatever is finally history. (#2838) The PR removed the bulk of non-newlib headers from the NodeMCU source base. app/libc has now been cut down to the bare minimum overrides to shadow the corresponding functions in the SDK's libc. The old c_xyz.h headerfiles have been nuked in favour of the standard <xyz.h> headers, with a few exceptions over in sdk-overrides. Again, shipping a libc.a without headers is a terrible thing to do. We're still living on a prayer that libc was configured the same was as a default-configured xtensa gcc toolchain assumes it is. That part I cannot do anything about, unfortunately, but it's no worse than it has been before. This enables our source files to compile successfully using the standard header files, and use the typical malloc()/calloc()/realloc()/free(), the strwhatever()s and memwhatever()s. These end up, through macro and linker magic, mapped to the appropriate SDK or ROM functions.
2019-07-21 23:58:21 +02:00
#
include
<stdlib.h>
Dev make cleanup (#2842)
2019-07-23 17:47:18 +02:00
#
define MEM_DEFAULT_USE_DRAM
Major cleanup - c_whatever is finally history. (#2838) The PR removed the bulk of non-newlib headers from the NodeMCU source base. app/libc has now been cut down to the bare minimum overrides to shadow the corresponding functions in the SDK's libc. The old c_xyz.h headerfiles have been nuked in favour of the standard <xyz.h> headers, with a few exceptions over in sdk-overrides. Again, shipping a libc.a without headers is a terrible thing to do. We're still living on a prayer that libc was configured the same was as a default-configured xtensa gcc toolchain assumes it is. That part I cannot do anything about, unfortunately, but it's no worse than it has been before. This enables our source files to compile successfully using the standard header files, and use the typical malloc()/calloc()/realloc()/free(), the strwhatever()s and memwhatever()s. These end up, through macro and linker magic, mapped to the appropriate SDK or ROM functions.
2019-07-21 23:58:21 +02:00
#
include
_next "mem.h"