jimi
/
go_exedir
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
Exercise in determining from whence we came.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
2 Commits
1 Branch
0 Tags
22 KiB
 
Branch: master
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'master'
${ noResults }
go_exedir/README.md

623 B
Raw Permalink Blame History

exedir

Examples of methods for determining the directory path where our executable resides.

  • The github.com/kardianos/osext package is used for reference. The other methods will require that the executable is located within the OS search path.

  • The first alternative utilizes exec.LookPath to find the executable within the OS search path. This method depends on the os, os/exec, and path packages.

  • The next method defines a local function to look for the file named in args[0] in the directories listed in the PATH environment variable. This method depends on the os and strings packages.