Results 1 to 2 of 2
Hello,
I'm new to the forum so forgive my mistakes please.
I recently installed BusyBox 1.17.3, i'm trying to add a new applet to BusyBox, i read some articles about ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 11-30-2010 #1Just Joined!
- Join Date
- Nov 2010
- Posts
- 4
BusyBox doesn't recognize new applet
Hello,
I'm new to the forum so forgive my mistakes please.
I recently installed BusyBox 1.17.3, i'm trying to add a new applet to BusyBox, i read some articles about adding a new applets to BusyBox and tried to follow them.
I created a new "Hello World" program called eladtest.c and placed it in the misc library in BusyBox.
int eladtest_main( int argc, char *argv[] )
{
printf("Hello World\n");
return 0;
}
I then updated the Config.src and Config.in files in the same directory and the Kbuild and Kbuild.src files.
Config:
----------
config ELADTEST
bool "eladtest"
default y
help
test busy box to understand funcionality.
Kbuild:
----------
lib-$(CONFIG_ELADTEST) += eladtest.o
iv'e updated the files applets.src.h and usage.h in the library /include.
usage.src.h:
-----------------
lib-$(CONFIG_ELADTEST) += eladtest.o
applets.src.h
------------------
IF_ELADTEST(APPLET(eladtest, _BB_DIR_USR_BIN, _BB_SUID_DROP))
after this is done, iv'e typed: sudo make defconfig
I then typed sudo make menuconfig and i saw my new applet there and checked it.
I did sudo make and sudo make install.
I thought all was going good but when im trying to do BusyBox eladtest it tells me that there isn't such applet.
the wierd thing is that if i go to the library BusyBox/_installs/usr/bin and type ./eladtest it works and print "Helllo World" to the screen.
Thanks and sorry again for the mistakes.
- 12-10-2010 #2Linux Guru
- Join Date
- Apr 2009
- Location
- I can be found either 40 miles west of Chicago, or in a galaxy far, far away.
- Posts
- 10,232
If you still have the old version of Busybox in your path, then it is trying to run that version, which won't have your eladtest applet. Go the tine BusyBox bin directory where you ran eladtest directly and try running ./Busybox eladtest - don't forget the ./ in front of Busybox.
Sometimes, real fast is almost as good as real time.
Just remember, Semper Gumbi - always be flexible!


Reply With Quote
