jameswalmsley / bitthunder

BitThunder - Reliable, real time, portable, scalable, embedded operating system, RTOS.
http://bitthunder.org
Other
170 stars 48 forks source link

How to get kconfig-mconf? #1

Open mikes-spindance opened 11 years ago

mikes-spindance commented 11 years ago

How do you get kconfig-mconf?

Here's what I tried...

mikes@ubuntu ~/james-walmsley-kconfig-frontends $ git clone https://github.com/jameswalmsley/kconfig-frontends.git
Cloning into 'kconfig-frontends'...
remote: Counting objects: 1171, done.
remote: Compressing objects: 100% (485/485), done.
remote: Total 1171 (delta 675), reused 1168 (delta 674)
Receiving objects: 100% (1171/1171), 608.66 KiB, done.
Resolving deltas: 100% (675/675), done.
mikes@ubuntu ~/james-walmsley-kconfig-frontends $ ./bootstrap
bash: ./bootstrap: No such file or directory
mikes@ubuntu ~/james-walmsley-kconfig-frontends $ cd kconfig-frontends/
mikes@ubuntu ~/james-walmsley-kconfig-frontends/kconfig-frontends $ ls
AUTHORS  bootstrap  configure.ac  COPYING  docs  frontends  INSTALL  libs  Makefile.am  README  scripts  utils
mikes@ubuntu ~/james-walmsley-kconfig-frontends/kconfig-frontends $ ./bootstrap
Creating macrodir...
Running autoreconf...
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `scripts/.autostuff/scripts'.
libtoolize: copying file `scripts/.autostuff/scripts/config.guess'
libtoolize: copying file `scripts/.autostuff/scripts/config.sub'
libtoolize: copying file `scripts/.autostuff/scripts/install-sh'
libtoolize: copying file `scripts/.autostuff/scripts/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `scripts/.autostuff/m4'.
libtoolize: copying file `scripts/.autostuff/m4/libtool.m4'
libtoolize: copying file `scripts/.autostuff/m4/ltoptions.m4'
libtoolize: copying file `scripts/.autostuff/m4/ltsugar.m4'
libtoolize: copying file `scripts/.autostuff/m4/ltversion.m4'
libtoolize: copying file `scripts/.autostuff/m4/lt~obsolete.m4'
configure.ac:50: installing `scripts/.autostuff/scripts/ar-lib'
configure.ac:209: installing `scripts/.autostuff/scripts/compile'
configure.ac:31: installing `scripts/.autostuff/scripts/missing'
frontends/conf/Makefile.am: installing `scripts/.autostuff/scripts/depcomp'
libs/parser/Makefile.am:45: user target `.l.c' defined here...
/usr/share/automake-1.11/am/lex.am: ... overrides Automake target `.l.c' defined here
configure.ac: installing `scripts/.autostuff/scripts/ylwrap'
Done. You may now run:
    ./configure
mikes@ubuntu ~/james-walmsley-kconfig-frontends/kconfig-frontends $ ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking for ar... ar
checking the archiver (ar) interface... ar
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking how to print strings... printf
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking how to convert i686-pc-linux-gnu file names to i686-pc-linux-gnu format... func_convert_file_noop
checking how to convert i686-pc-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for mt... mt
checking if mt is a manifest tool... no
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking dependency style of gcc... (cached) gcc3
checking whether gcc and cc understand -c and -o together... yes
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking for ld used by g++... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC -DPIC
checking if g++ PIC flag -fPIC -DPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking if g++ supports -c -o file.o... (cached) yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... (cached) GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking for inline... inline
checking whether make sets $(MAKE)... (cached) yes
checking for gperf... gperf
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for flex... flex
checking lex output file root... lex.yy
checking lex library... -lfl
checking whether yytext is a pointer... yes
checking for bison... bison -y
checking libintl.h usability... yes
checking libintl.h presence... yes
checking for libintl.h... yes
checking whether gettext is declared... yes
checking for library containing gettext... none required
checking ncursesw/curses.h usability... no
checking ncursesw/curses.h presence... no
checking for ncursesw/curses.h... no
checking ncurses/ncurses.h usability... no
checking ncurses/ncurses.h presence... no
checking for ncurses/ncurses.h... no
checking ncurses/curses.h usability... no
checking ncurses/curses.h presence... no
checking for ncurses/curses.h... no
checking ncurses.h usability... no
checking ncurses.h presence... no
checking for ncurses.h... no
checking curses.h usability... no
checking curses.h presence... no
checking for curses.h... no
checking for library containing initscr... no
checking for library containing setupterm... no
checking for library containing new_panel... no
checking for library containing menu_init... no
checking for gtk... no
checking for qt4... no
configure: creating ./config.status
config.status: creating Makefile
config.status: creating docs/Makefile
config.status: creating libs/Makefile
config.status: creating libs/images/Makefile
config.status: creating libs/lxdialog/Makefile
config.status: creating libs/parser/Makefile
config.status: creating frontends/Makefile
config.status: creating frontends/conf/Makefile
config.status: creating frontends/mconf/Makefile
config.status: creating frontends/nconf/Makefile
config.status: creating frontends/gconf/Makefile
config.status: creating frontends/qconf/Makefile
config.status: creating utils/Makefile
config.status: creating scripts/Makefile
config.status: creating scripts/.autostuff/config.h
config.status: executing depfiles commands
config.status: executing libtool commands
configure: 
configure: Configured with:
configure: - parser library     : shared (version: 3.10.0)
configure:   - root-menu prompt : Configuration
configure:   - config prefix    : CONFIG_
configure: - frontends          : conf
configure:   - transform name   : s&^&kconfig-&
configure:   - localised        : yes
configure: - install utilities  : yes
configure: - CFLAGS CXXFLAGS    : -Wall -Werror
mikes@ubuntu ~/james-walmsley-kconfig-frontends/kconfig-frontends $ make
Making all in docs
make[1]: Entering directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/docs'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/docs'
Making all in libs
make[1]: Entering directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/libs'
Making all in parser
make[2]: Entering directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/libs/parser'
gperf -t --output-file hconf.c -a -C -E -g -k 1,3,$ -p -t hconf.gperf
flex -L -P zconf  -olconf.c lconf.l
make  all-am
make[3]: Entering directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/libs/parser'
/bin/bash ../../scripts/.autostuff/scripts/ylwrap yconf.y y.tab.c yconf.c y.tab.h yconf.h y.output yconf.output -- bison -y -t -l -p zconf 
/bin/bash ../../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I../../scripts/.autostuff  -DROOTMENU="\"Configuration\"" -DCONFIG_=\"CONFIG_\"    -Wall -Werror -g -O2 -MT libkconfig_parser_la-yconf.lo -MD -MP -MF .deps/libkconfig_parser_la-yconf.Tpo -c -o libkconfig_parser_la-yconf.lo `test -f 'yconf.c' || echo './'`yconf.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../scripts/.autostuff -DROOTMENU=\"Configuration\" -DCONFIG_=\"CONFIG_\" -Wall -Werror -g -O2 -MT libkconfig_parser_la-yconf.lo -MD -MP -MF .deps/libkconfig_parser_la-yconf.Tpo -c yconf.c  -fPIC -DPIC -o .libs/libkconfig_parser_la-yconf.o
mv -f .deps/libkconfig_parser_la-yconf.Tpo .deps/libkconfig_parser_la-yconf.Plo
/bin/bash ../../libtool  --tag=CC   --mode=link gcc  -Wall -Werror -g -O2 -release 3.10.0 -no-undefined  -o libkconfig-parser.la -rpath /usr/local/lib libkconfig_parser_la-yconf.lo  
libtool: link: gcc -shared  -fPIC -DPIC  .libs/libkconfig_parser_la-yconf.o    -O2   -Wl,-soname -Wl,libkconfig-parser-3.10.0.so -o .libs/libkconfig-parser-3.10.0.so
libtool: link: (cd ".libs" && rm -f "libkconfig-parser.so" && ln -s "libkconfig-parser-3.10.0.so" "libkconfig-parser.so")
libtool: link: ( cd ".libs" && rm -f "libkconfig-parser.la" && ln -s "../libkconfig-parser.la" "libkconfig-parser.la" )
make[3]: Leaving directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/libs/parser'
make[2]: Leaving directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/libs/parser'
make[2]: Entering directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/libs'
make[2]: Nothing to be done for `all-am'.
make[2]: Leaving directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/libs'
make[1]: Leaving directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/libs'
Making all in frontends
make[1]: Entering directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/frontends'
Making all in conf
make[2]: Entering directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/frontends/conf'
gcc -DHAVE_CONFIG_H -I. -I../../scripts/.autostuff    -I../../libs/parser   -Wall -Werror -g -O2 -MT conf-conf.o -MD -MP -MF .deps/conf-conf.Tpo -c -o conf-conf.o `test -f 'conf.c' || echo './'`conf.c
mv -f .deps/conf-conf.Tpo .deps/conf-conf.Po
/bin/bash ../../libtool  --tag=CC   --mode=link gcc  -Wall -Werror -g -O2   -o conf conf-conf.o ../../libs/parser/libkconfig-parser.la   
libtool: link: gcc -Wall -Werror -g -O2 -o .libs/conf conf-conf.o  ../../libs/parser/.libs/libkconfig-parser.so
make[2]: Leaving directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/frontends/conf'
make[2]: Entering directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/frontends'
make[2]: Nothing to be done for `all-am'.
make[2]: Leaving directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/frontends'
make[1]: Leaving directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/frontends'
Making all in scripts
make[1]: Entering directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/scripts'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/scripts'
Making all in utils
make[1]: Entering directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/utils'
gcc -DHAVE_CONFIG_H -I. -I../scripts/.autostuff   -I../libs/parser   -Wall -Werror -g -O2 -MT gettext-gettext.o -MD -MP -MF .deps/gettext-gettext.Tpo -c -o gettext-gettext.o `test -f 'gettext.c' || echo './'`gettext.c
mv -f .deps/gettext-gettext.Tpo .deps/gettext-gettext.Po
/bin/bash ../libtool  --tag=CC   --mode=link gcc  -Wall -Werror -g -O2   -o gettext gettext-gettext.o ../libs/parser/libkconfig-parser.la  
libtool: link: gcc -Wall -Werror -g -O2 -o .libs/gettext gettext-gettext.o  ../libs/parser/.libs/libkconfig-parser.so
/bin/sed -e "s/@CONFIG_@/CONFIG_/g"    \
                      tweak.in >tweak
make[1]: Leaving directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/utils'
make[1]: Entering directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends'
make[1]: Nothing to be done for `all-am'.
make[1]: Leaving directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends'
mikes@ubuntu ~/james-walmsley-kconfig-frontends/kconfig-frontends $ sudo make install
[sudo] password for mikes: 
Making install in docs
make[1]: Entering directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/docs'
make[2]: Entering directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/docs'
make[2]: Nothing to be done for `install-exec-am'.
 /bin/mkdir -p '/usr/local/share/doc/kconfig-frontends'
 /usr/bin/install -c -m 644 kconfig-language.txt kconfig.txt '/usr/local/share/doc/kconfig-frontends'
make[2]: Leaving directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/docs'
make[1]: Leaving directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/docs'
Making install in libs
make[1]: Entering directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/libs'
Making install in parser
make[2]: Entering directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/libs/parser'
make  install-am
make[3]: Entering directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/libs/parser'
make[4]: Entering directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/libs/parser'
 /bin/mkdir -p '/usr/local/lib'
 /bin/bash ../../libtool   --mode=install /usr/bin/install -c   libkconfig-parser.la '/usr/local/lib'
libtool: install: /usr/bin/install -c .libs/libkconfig-parser-3.10.0.so /usr/local/lib/libkconfig-parser-3.10.0.so
libtool: install: (cd /usr/local/lib && { ln -s -f libkconfig-parser-3.10.0.so libkconfig-parser.so || { rm -f libkconfig-parser.so && ln -s libkconfig-parser-3.10.0.so libkconfig-parser.so; }; })
libtool: install: /usr/bin/install -c .libs/libkconfig-parser.lai /usr/local/lib/libkconfig-parser.la
libtool: finish: PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/sbin" ldconfig -n /usr/local/lib
----------------------------------------------------------------------
Libraries have been installed in:
   /usr/local/lib

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
   - add LIBDIR to the `LD_LIBRARY_PATH' environment variable
     during execution
   - add LIBDIR to the `LD_RUN_PATH' environment variable
     during linking
   - use the `-Wl,-rpath -Wl,LIBDIR' linker flag
   - have your system administrator add LIBDIR to `/etc/ld.so.conf'

See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------
 /bin/mkdir -p '/usr/local/include/kconfig'
 /usr/bin/install -c -m 644 list.h lkc.h expr.h lkc_proto.h '/usr/local/include/kconfig'
make[4]: Leaving directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/libs/parser'
make[3]: Leaving directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/libs/parser'
make[2]: Leaving directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/libs/parser'
make[2]: Entering directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/libs'
make[3]: Entering directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/libs'
make[3]: Nothing to be done for `install-exec-am'.
make[3]: Nothing to be done for `install-data-am'.
make[3]: Leaving directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/libs'
make[2]: Leaving directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/libs'
make[1]: Leaving directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/libs'
Making install in frontends
make[1]: Entering directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/frontends'
Making install in conf
make[2]: Entering directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/frontends/conf'
make[3]: Entering directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/frontends/conf'
 /bin/mkdir -p '/usr/local/bin'
  /bin/bash ../../libtool   --mode=install /usr/bin/install -c conf '/usr/local/bin/./kconfig-conf'
libtool: install: /usr/bin/install -c .libs/conf /usr/local/bin/./kconfig-conf
make[3]: Nothing to be done for `install-data-am'.
make[3]: Leaving directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/frontends/conf'
make[2]: Leaving directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/frontends/conf'
make[2]: Entering directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/frontends'
make[3]: Entering directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/frontends'
make[3]: Nothing to be done for `install-exec-am'.
make[3]: Nothing to be done for `install-data-am'.
make[3]: Leaving directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/frontends'
make[2]: Leaving directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/frontends'
make[1]: Leaving directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/frontends'
Making install in scripts
make[1]: Entering directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/scripts'
make[2]: Entering directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/scripts'
make[2]: Nothing to be done for `install-exec-am'.
make[2]: Nothing to be done for `install-data-am'.
make[2]: Leaving directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/scripts'
make[1]: Leaving directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/scripts'
Making install in utils
make[1]: Entering directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/utils'
make[2]: Entering directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/utils'
 /bin/mkdir -p '/usr/local/bin'
  /bin/bash ../libtool   --mode=install /usr/bin/install -c gettext '/usr/local/bin/./kconfig-gettext'
libtool: install: /usr/bin/install -c .libs/gettext /usr/local/bin/./kconfig-gettext
 /bin/mkdir -p '/usr/local/bin'
 /usr/bin/install -c tweak '/usr/local/bin/./kconfig-tweak'
 /bin/mkdir -p '/usr/local/bin'
 /usr/bin/install -c diff '/usr/local/bin/./kconfig-diff'
 /usr/bin/install -c merge '/usr/local/bin/./kconfig-merge'
make[2]: Nothing to be done for `install-data-am'.
make[2]: Leaving directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/utils'
make[1]: Leaving directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends/utils'
make[1]: Entering directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends'
make[2]: Entering directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends'
make[2]: Nothing to be done for `install-exec-am'.
make[2]: Nothing to be done for `install-data-am'.
make[2]: Leaving directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends'
make[1]: Leaving directory `/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends'
mikes@ubuntu ~/james-walmsley-kconfig-frontends/kconfig-frontends $ pwd
/home/mikes/james-walmsley-kconfig-frontends/kconfig-frontends
mikes@ubuntu ~/james-walmsley-kconfig-frontends/kconfig-frontends $ cd ..
mikes@ubuntu ~/james-walmsley-kconfig-frontends $ ls
kconfig-frontends
mikes@ubuntu ~/james-walmsley-kconfig-frontends $ cd ..
mikes@ubuntu ~ $ cd bitthunder/
mikes@ubuntu ~/bitthunder $ ls
arch  bsp  doc  drivers  Kconfig  kernel  lib  LICENSE  Makefile  os  README.md  scripts
mikes@ubuntu ~/bitthunder $ make menuconfig
/bin/sh: 1: kconfig-mconf: not found
make: *** [menuconfig] Error 127
mikes-spindance commented 11 years ago

I tried using kconfig-conf instead of kconfig-mconf. What should BT_CONFIG_BSP_DIR be set to? What procedure should set BT_CONFIG_BSP_DIR?

jameswalmsley commented 11 years ago

Hi, thanks for trying this out. I'm away at the moment, but will be back over the weekend. I'll be around to help you get this working then.

Which platform are you using?

mikes-spindance commented 11 years ago

I'm targeting a STM32F4xx with arm-none-eabi-gcc on linuxmint-15-mate-dvd-32bit.iso

Yann E. MORIN helped me out on getting kconfig-mconf:

I needed libncurses5-dev (see below).

I still have the BT_CONFIG_BSP_DIR challenge.

cd
git clone http://ymorin.is-a-geek.org/git/kconfig-frontends
cd kconfig-frontends/
sudo apt-get install gperf
sudo apt-get install flex
sudo apt-get install bison
sudo apt-get install libncurses5-dev
./bootstrap
./configure
make
sudo make install
sudo /sbin/ldconfig -v
jameswalmsley commented 11 years ago

Hi Mike,

So the BSP_DIR variable defines where to build from, this is normally set by a BSP config (within the BitThunder bsp folders) or externally via a user project.

You can take a look at bootthunder which sets this (as an example of an external project): https://github.com/BitThunder/bootthunder

See the folder bsp/Kconfig

In that case it is set to ../bsp/ (which really means 1-up from the bitthunder root, and into the bsp folder).

I'll add a new repository with a blank working example, and I'll create a script that generates a new project. Its a little clunky I guess, but once you get it working it works well.

Currently I haven't written any drivers for that platform, but support for the basic scheduler should be really easy to get going as it should use the normal NVIC and SysTick drivers.

As you've already seen there's not so much documentation on all this, but I'll try to help as you go along.

How did you find bitthunder? If you are interested it would be great to have you as the official STM32 maintainer. I have a few stm32 boards lying around, but don't get much time to actually do stuff with them, its a nice platform.

James

mikes-spindance commented 11 years ago

Thanks, the blank working example would be helpful!

I think I found the project by googling freertos kconfig.

Regarding maintainer, let me successfully build first.

-Mike

On Aug 12, 2013, at 3:53 AM, James Walmsley notifications@github.com wrote:

Hi Mike,

So the BSP_DIR variable defines where to build from, this is normally set by a BSP config (within the BitThunder bsp folders) or externally via a user project.

You can take a look at bootthunder which sets this (as an example of an external project): https://github.com/BitThunder/bootthunder

See the folder bsp/Kconfig

In that case it is set to ../bsp/ (which really means 1-up from the bitthunder root, and into the bsp folder).

I'll add a new repository with a blank working example, and I'll create a script that generates a new project. Its a little clunky I guess, but once you get it working it works well.

Currently I haven't written any drivers for that platform, but support for the basic scheduler should be really easy to get going as it should use the normal NVIC and SysTick drivers.

As you've already seen there's not so much documentation on all this, but I'll try to help as you go along.

How did you find bitthunder? If you are interested it would be great to have you as the official STM32 maintainer. I have a few stm32 boards lying around, but don't get much time to actually do stuff with them, its a nice platform.

James

— Reply to this email directly or view it on GitHub.

jameswalmsley commented 11 years ago

Hi Mike,

I created an example, and also fixed up the STM32 code to actually compile. See:

https://github.com/BitThunder/example-project

In case bitthunder isn't automatically checked out, be sure to do a:

git submodule update --init

James

jameswalmsley commented 11 years ago

Hi Mike,

Don't know if you've had time to have a go with BitThunder, I've added some "basic" documentation and API overview to the website now.

See http://bitthunder.org/docs/home/

James

mikes-spindance commented 11 years ago

Thanks!

Mike Stitt Engineer - SpinDance, Inc. - mikes@spindance.com - m:616.498.6598 - o:616-355-7000

On Aug 19, 2013, at 10:19 AM, James Walmsley notifications@github.com wrote:

Hi Mike,

Don't know if you've had time to have a go with BitThunder, I've added some "basic" documentation and API overview to the website now.

See http://bitthunder.org/docs/home/

James

— Reply to this email directly or view it on GitHub.