On Mon, Jan 25, 2010 at 8:10 PM, Martin Paljak <[email protected]> wrote: > On Jan 25, 2010, at 18:06 , Alon Bar-Lev wrote: >> On Mon, Jan 25, 2010 at 9:07 AM, Andreas Jellinghaus <[email protected]> >> wrote: >>> Am Sonntag 24 Januar 2010 21:45:07 schrieb Alon Bar-Lev: >>>> If it is imported from other place, why not just link against it? >>> >>> what do you exactly propose? >>> create a second noinst_ lib in common/ and link it in opensc/ the same >>> way we include libcompat.a? fine with me. >> >> No... if the code was copied out of some other project, link against >> that project... > Not everything is "projectized" (incl simclist). There's a good reason sqlite > provides a sqlite.c you just put into your project and voila, you get the > sqlite functionality. It does have some drawbacks but at the same time it > avoids library-messs for users and provides ease of use (in this case, to > developers)
At my machine: $ pkg-config --libs sqlite3 -lsqlite3 /usr/lib64/libsqlite3.so -> libsqlite3.so.0.8.6 /usr/lib64/libsqlite3.so.0 -> libsqlite3.so.0.8.6 /usr/lib64/libsqlite3.so.0.8.6 _______________________________________________ opensc-devel mailing list [email protected] http://www.opensc-project.org/mailman/listinfo/opensc-devel
