Linker options
-
Is there an option to tell the linker to look for functions in all libraries in the library path. It is a pain to have to specify each library I want to use when there are over 100.
-
Is there an option to tell the linker to look for functions in all libraries in the library path. It is a pain to have to specify each library I want to use when there are over 100.
Not that I'm aware of. Its generally straightforward to sort out. Don't worry about trying to guess which libs you need. After a while you'll learn which libs you need. But if you don't know which libs you need repeat the following procedure:- 1) Link as normal. 2) if no errors, then finished (duh!) 3) Look at the first link error. Identify the function name that is not resolved. Look it up in MSDN. The entry in MSDN will tell you which lib you need (if its a COM object it may not, then you'll need to hunt around a bit). 3a) if the function name is not in MSDN check that it isn't a 3rd party lib you have forgotten to list. 4) Now relink. The reason for not worrying about the remaining errors is that many of them may be for the same lib as the first error. 5) Repeat from (3) until no errors. After a while you'll be able to realise which function come from which lib and you'll be able to do more functions/libs in stage 3 than I've suggested above. None of that was rocket science, and it isn't really that hard. Cheers Stephen Stephen Kellett -- C++/Java/Win NT/Unix variants Memory leaks/corruptions/performance/system problems. UK based. Problems with RSI/WRULD? Contact me for advice.