Instead if specifying each one with -l, is there an easy way for me to link to all libraries in a specific directory? for example, all of the custom libraries for this API are put in a specific directory.. I need them all when linking to it..
Right now, I'm just specifying each one individually, but that gets long...
Thanks!
Seems from googling, the only way is to specify all of them?
*.a doesn't work?
You don't need to use "-lfoo" to link libfoo.a, you can just say libfoo.a. Which means you can also say *.a
Code:cc -o prog prog.o ../somepath/*.a
Code://try //{ if (a) do { f( b); } while(1); else do { f(!b); } while(1); //}
Works great! didn't know you didn't need -lfoo Thank you!
Last edited by dayalsoap; 06-16-2011 at 05:48 PM.
It doesn't quite mean the same to some linkers, though. If you specify a lib file directly, it will just link it in completely. If you specify it with -l, it will just link in those parts you actually use.
All the buzzt!
CornedBee
"There is not now, nor has there ever been, nor will there ever be, any programming language in which it is the least bit difficult to write bad code."
- Flon's Law
If you want, you can use a little bit of magic:
That assumes the libraries are in the current directory, if not:Code:gcc *.c -o program $(ls lib*.a | sed 's/lib/-l/' | sed 's/\.a//')
Code:gcc *.c -o program -L/path/to/libraries $(ls /path/to/libraries | grep '\.a$' | sed 's/lib/-l/' | sed 's/\.a//')
dwk
Seek and ye shall find. quaere et invenies.
"Simplicity does not precede complexity, but follows it." -- Alan Perlis
"Testing can only prove the presence of bugs, not their absence." -- Edsger Dijkstra
"The only real mistake is the one from which we learn nothing." -- John Powell
Other boards: DaniWeb, TPS
Unofficial Wiki FAQ: cpwiki.sf.net
My website: http://dwks.theprogrammingsite.com/
Projects: codeform, xuni, atlantis, nort, etc.
It also wouldn't be difficult, in a shell script, to parse a list of files and produce a command line with lib<name>.a converted into -l<name>.Originally Posted by CornedBee
Linking against all libraries in a directory might get entertaining (a self-inflicted version of DLL hell) as some directories contain multiple versions of libraries, each version exporting functions (or other symbols) with the same name.
Lists of libraries needed by a program don't normally change with the wind, so I would personally advocate editing a makefile with a specific list of needed libraries over some trick to link against all libraries in a directory.
And don't forget that Unix linkers usually need libraries to be in dependency order on the command line, i.e. if library A depends on B, then -lA must be before -lB on the command line.
All the buzzt!
"There is not now, nor has there ever been, nor will there ever be, any programming language in which it is the least bit difficult to write bad code."
- Flon's Law
Instead of trying to be smart with wildcards and scripting, I'd rather write a pkg_config file. That way I can be explicit on the exact files and ordering and I can also distribute the file if I distribute the libraries.
