how couple controlling gcc but -l nor hardcoding route library does follow libname.so controlling convention?

i have common library i wish couple an executable opposing controlling gcc. common library nonstandard name form libname.so, i common -l option. (it happens also python extension, 'lib' prefix.)

i am means pass route library record directly couple management line, nonetheless causes library route hardcoded executable.

for example:

g++ -o build/bin/myapp build/bin/_mylib.so

is there proceed couple library but causing route hardcoded executable?