Hi Tomasz, On 10/8/21, Tomasz CEDRO <to...@cedro.info> wrote: > On Fri, Oct 8, 2021 at 6:45 AM Takashi Yamamoto wrote: sic >> 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. > > Porting to FreeBSD was my first intention, no problem with that, but > then where do I even send patches if "maintenance" is just keeping old > bz2 package somewhere out there. Sorry, this is not the serious way to > go, this tool seems abandoned and you should consider abandoning it > too. > > "Works for me after I patched 38 packages that took me 18 days and > works only on my local machine"^TM makes me think "do not touch that > project"^TM :-) > > >> 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? > > Anything that has live community, source code repository, and is > proven effective in other projects will be better :-) > > There are some `*.py` files in `nuttx/tools/` already so why Python > could be a blocker? From my experience Python is the best way to > provide platform independent tools in most cases. > > > This is my "first contact" with NuttX. That could provide a valuable > feedback for you guys. I played before with FreeRTOS, ARM MBED, and > Zephyr RTOS, all of them provide Fire-and-Forget experience that is > crucial for business. There is no point in using solution that > requires +10x more time to setup than work on the target project. Sure > I can invest some time in developing the tools but first I need to get > at least one working product to prove that tool is worth the time and > effort :-) > > I don't want to sound rude, but on Zephyr I just got from scratch > working example for ESP32-C3 under 5 minutes, that proves I can > implement my project using that tool set even though it may require > some additional work. >
NuttX works out-of-the-box on many tested host OS as you can see here: https://nuttx.apache.org/docs/latest/quickstart/install.html Users of Ubuntu 19.04+ for example doesn't need to compile the kconfig-frontend because it is a package available to be installed using "apt(-get) install". Unfortunately we have only Bernd Walter, and now you, using FreeBSD. So it is easy to understand why it is not working yet and why you are facing issues. If you analyze the errors you will see they are just Warnings promoted to Errors. BR, Alan
