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.
1 Commit
1 Branch
0 Tags
22 KiB
 
Tree: 2d4ea53126
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '2d4ea53126'
${ noResults }
go_exedir/README.md

343 B
Raw Blame History

exedir

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

  • The 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.