I have following question about code banking. There's some small tests, that uses one big library. So, how can I put this library to different code banks? Ofc, I can include this tests right in library project, but are there any other solutions?
"Unless you have an object module that is larger than the size of one of your banks, I cannot see how there can be a problem." Hmm...May be I dont understand something. Im new to keil/c51. When I include library to project, I get the following: <BANK1> "...name.LIB" <BANK2> "....obj" and so. If library is large enough, and it cannot fit in one bank, linker throws an error.
ps. My solution: I split the tests, so linker cut unused code from library.
"linker cut unused code from library"
That is exactly how the linker should process library files.
"That is exactly how the linker should process library files." Ofc, and I used this to solve the problem, but I want more complex tests, when used library code is >64k.
I now understand what you're asking.
You should be able to specify the inclusion of a library file, without having to specify an explicit bank for that library.
The default for the runtime libraries is no specific bank, so the control of such things must be there.
My project(s) tended to only a minimal amount of library functions, so I have not seen what you are saying.
Is that done by specifying the <default> bank under properties for the group containing the library?
If push-comes-to-shove you could consider using the LIB tool and split your libraries into smaller units.