Implementing my own Command

rajesh1978 · 07-11-2010, 11:46 AM

In fact I know to set the path environmental variable . But I was diverted by the comments that I get as answer.

It in deed wanted to know as Linux is an open source if I want to add one command like ls,cd etc then where to put the executable or lib.

how the executable ls or cd is working the same way I want to put my own command.

mobinskariya · 07-11-2010, 11:50 AM

so what you should do is add the path /usr/Hoge/Test to the bash environment variable $PATH. use the following command to modify the $PATH variable

Code:

PATH=/usr/Hoge/Test:$PATH

Now you should be able to execute the binary by typing

Code:

executablefile

Sergei Steshenko · 07-11-2010, 12:04 PM

Quote:

Originally Posted by rajesh1978

In fact I know to set the path environmental variable . But I was diverted by the comments that I get as answer.

It in deed wanted to know as Linux is an open source if I want to add one command like ls,cd etc then where to put the executable or lib.

how the executable ls or cd is working the same way I want to put my own command.

'ls' is works the way it works just because its directory can be found in $PATH.

The library part is different; it's a non-issue if you statically link; for DLLs read 'man ldconfig' and perform WEB search on LD_LIBRARY_PATH, LD_RUN_PATH environment variables. Also, you might think about a shell wrapper for your executable, this is, for example, how 'firefox' is typically called/implemented.

pr_deltoid · 07-11-2010, 12:12 PM

Going by what I've read you don't have to do anything but put your program in a directory that is in PATH. Just make sure the name of your program doesn't conflict with any others. Don't overwrite an important program with the same name.

Code:

echo $PATH

The directories are separated by colons.

rajesh1978 · 07-11-2010, 12:19 PM

Thanks to all of you, for your guidance. I will work on your suggestions

grail · 07-11-2010, 07:24 PM

Or just see Steve's post that mentions where typical programs for all users live. I would add that when using a test item that another common practice can be to place it in the /usr/local/bin until you wish to go main stream, then I typically go with /usr/bin (I try to leave /bin to system application installs)

MTK358 · 07-11-2010, 07:57 PM

$HOME/bin is a good place for user-created commands. Just make sure it's in $PATH (in most distros it's already there).