a1a0315b9c
NuttX generates the app main name from Kconfig symbol xxxx_PROGNAME. The documentation was defining manually the entry point as custom_hello(int char, char *argv[]) and pointing CONFIG_INIT_ENTRYPOINT="custom_hello". The right thing to do is creating the application entry point as "int main(int char, char *argv[])" and the build system will add "_main" to the PROGNAME. Signed-off-by: Alan C. Assis <acassis@gmail.com> |
||
|---|---|---|
| .. | ||
| image | ||
| automounter.rst | ||
| citests.rst | ||
| coredump.rst | ||
| cortexmhardfaults.rst | ||
| cpp_cmake.rst | ||
| customapps.rst | ||
| customboards.rst | ||
| drivers.rst | ||
| etcromfs.rst | ||
| gdbwithpython.rst | ||
| index.rst | ||
| minidumpserver.rst | ||
| nestedinterrupts.rst | ||
| nfs.rst | ||
| ofloader.rst | ||
| pysimcoder.rst | ||
| qemugdb.rst | ||
| rndis.rst | ||
| simulator.rst | ||
| stackrecord.rst | ||
| stm32ccm.rst | ||
| stm32nullpointer.rst | ||
| tasktrace.rst | ||
| tasktraceinternal.rst | ||
| tasktraceuser.rst | ||
| testingtcpip.rst | ||
| thread_local_storage.rst | ||
| usbtrace.rst | ||
| zerolatencyinterrupts.rst | ||