On Fri, Oct 8, 2021 at 12:51 PM Tomasz CEDRO <to...@cedro.info> wrote: > > On Fri, Oct 8, 2021 at 5:15 AM Tomasz CEDRO wrote: > > On Fri, Oct 8, 2021 at 4:47 AM Nathan Hartman wrote: > > > There is a NuttX Tools repo at > > > https://bitbucket.org/nuttx/tools/downloads/ > > > > > > I think I built the kconfig-frontends from there a long time ago. > > > > Thank you for this hint I will try to build that on my FreeBSD. I > > could not find kconfig sources :-) > > `kconfig-frontends-4.11.0.1` does not build on FreeBSD: > > CC libs/parser/libs_parser_libkconfig_parser_la-yconf.lo > In file included from libs/parser/yconf.c:252: > libs/parser/hconf.gperf:153:1: error: conflicting types for 'kconf_id_lookup' > kconf_id_lookup (register const char *str, register unsigned int len) > ^ > libs/parser/hconf.gperf:12:31: note: previous declaration is here > static const struct kconf_id *kconf_id_lookup(register const char > *str, register GPERF_LEN_TYPE len); > ^ > libs/parser/hconf.gperf:40:44: warning: static variable > 'kconf_id_strings_contents' is used in an inline function with > external linkage [-Wstatic-in-inline] > register const char *s = o + kconf_id_strings; > ^ > libs/parser/hconf.gperf:145:43: note: expanded from macro 'kconf_id_strings' > #define kconf_id_strings ((const char *) &kconf_id_strings_contents) > ^ > libs/parser/hconf.gperf:147:1: note: use 'static' to give inline > function 'kconf_id_lookup' internal linkage > > There is `gperf-3.1` package installed. > > > Can anyone point me to the official `kconfig-frontends` website and > source code repository? > > I can find 28 repositories on GitHub all seems to be outdated forks: > https://github.com/search?q=kconfig-frontends > > > One of them is https://github.com/NuttX/tools/tree/master/kconfig-frontends, > where I find: > > This is a snapshot of the kconfig-frontends version 4.11.0.1 tarball taken > from http://ymorin.is-a-geek.org/projects/kconfig-frontends. > > But that server does not respond. > > > Another finding is https://github.com/espressif/kconfig-frontends but > that is explicitly a modified version so its a different tool with the > same name. > > > I hope NuttX does not have a critical dependency on abandoned > unmaintained tool ?
i guess "we are maintaining the fork by ourselves" is a better description of the current situation. as it can be built for macOS. i guess it isn't too difficult to port it to FreeBSD. i think kconfiglib is a better tool in general. at least it's definitely easier for someone new to nuttx to start with. but it seems for some people python dependency is not acceptable. maybe we can support the both? how others think? > > > I need to deliver a result to my client in a form where they clone a > git repo, bootstrap one script, and build the firmware ready to use. > Is it possible with NuttX? It can be done with Zephyr. > > -- > CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
