Topic: Order of library search
I have noticed that the order in which libraries are listed seems to be critically important.
I am referring to when this is done by naming "libxxxxxx.a" libraries in the 'Linker' field, under Project Options>Project Flags.
I have not investigated whether it makes any difference what order they are entered when invoked by the alternative method, of adding the "xxxxxx.a" files (the "lib..." filename prefix being permissible but unnecessary), in the Project Options panel.
The example I am using, from which I have discovered this, is as follows.
When I enter the following in the Linker field, the BUILD fails with a long list of not-found subroutines:
[ -luser32 -lgdi32 -lopengl32 -liowin -ldis ]
When I enter the following in the Linker field, the BUILD succeeds:
[ -liowin -ldis -luser32 -lgdi32 -lopengl32 ]
I have not checked whether this behaviour is covered by the SF2.1 help files. Someone please tell me to RTFM if necessary!
If it is not in the manual, then any guidance on how best to select the library entry sequence would be helpful. Also, Jeff, is this behaviour as intended?
Could anyone who knows also please also tell us whether it matters in which order we add library "xxxxx.a" files to the project outline, when using this method of having SF2.1 search them.
---
John