Why are our shared libs called e.g. ecpg.so and not libecpg.so ?
This seems strange to me, and it also complicates the link, 
since now I cannot say -lecpg and decide whether to link static or shared
with the corresponding linker flag (-bnso or -brtl on AIX)

Andreas 

Fri, 16 Jul 1999 17:19:17 +0200
Zeugswetter Andreas IZ5 <Andreas.Zeugswetter@telecom.at>
shared lib names
> Why are our shared libs called e.g. ecpg.so and not libecpg.so ?

Uh, they aren't on at least some platforms. Here is the lib directory
on my linux box:

global1.bki.source            libpq++.so.3.0
global1.description           libpq.a
libecpg.a                     libpq.so
libecpg.so                    libpq.so.2
libecpg.so.3                  libpq.so.2.0
libecpg.so.3.0.0              libpsqlodbc.a
libpgtcl.a                    libpsqlodbc.so
libpgtcl.so                   libpsqlodbc.so.0
libpgtcl.so.2                 libpsqlodbc.so.0.25
libpgtcl.so.2.0               local1_template1.bki.source
libpq++.a                     local1_template1.description
libpq++.so                    pg_geqo.sample
libpq++.so.2                  pg_hba.conf.sample
libpq++.so.2.0                plpgsql.so
libpq++.so.3                  pltcl.so

??

                 - Thomas

-- 
Thomas Lockhart				lockhart@alumni.caltech.edu
South Pasadena, California

Fri, 16 Jul 1999 15:34:09 +0000
Thomas Lockhart <lockhart@alumni.caltech.edu>
Re: [HACKERS] shared lib names