Justin, Really appreciate you doing this testing. It is on us to make the getting started process much smoother and we will make that a priority for the next release. In the meantime figuring out where we lead you wrong would be helpful.
> > ---------- Forwarded message --------- > From: Justin Mclean <jus...@classsoftware.com> > Date: Sat, May 2, 2020 at 12:09 AM > Subject: Re: [VOTE] Release Apache NuttX (Incubating) 9.0.0 [RC1] > To: <gene...@incubator.apache.org> > > I think someone new to this would find it very hard to compile from > source. I followed the instruction and they have improved, but there still > a lot of assumptions and other tools need to setup it correctly (e.g > kconfig-tweak / kconfig-conf and kconfig is in a seperate external repo and > doesn’t seem to compile on OSX). If any of these tools are need to compile > they really should be moved to the ASF if at all possible. > We certainly can look at what to do about the kconfig-frontend code. Some distributions package it up, there is no brew install for it :/ it is GPL code if I remember correctly so officially bringing it under the project might be hard. I can look at if outside of the project we could maintain a tap for it which would provide easier onboarding. I think that is the only tool that we rely for all builds that is usually built from source. gperf uboot-tools are fairly easy to get via other sources. It does build on macOS (we do it in CI every day) so let's see what went wrong. For the kconfig-frontends: $ mkdir buildtools $ export NUTTXTOOLS=`pwd`/buildtools $ export NUTTXTOOLS_PATH=$NUTTXTOOLS/bin:$NUTTXTOOLS/usr/bin $ git clone https://bitbucket.org/nuttx/tools.git tools $ cd tools/ $ cd kconfig-frontends $ ./configure --prefix=$NUTTXTOOLS \ --enable-mconf --disable-gconf --disable-qconf $ touch aclocal.m4 Makefile.in $ make $ make install $ export PATH=$NUTTXTOOLS_PATH For Flock $ brew tap discoteq/discoteq $ brew install flock Thanks again, Brennan
