There is some cases where its convenient to have it as a lib, but mostly the dll is the way to go, specially if you have a usecase where you want to share the code between several exes.
Dlls impose a bit of extra work in keeping your APIs binary compatible and such.
"You mean to say, if a static library is used by 2 execs in symbain, then both exes will have a copy of the libray, right?
But this will be waste of lot of memory."
But that's exactly what a static library is, and is why there are dynamic libraries.
Your comment about it being a waste of memory implies you have another idea of what a static library is or should be?
Forum posts: 1232
Your knowledge is wrong then.
Symbian do support static libraries, and that is exactly what the "LIB" target is for.
Forum posts: 8
Hi Alh,
You mean to say, if a static library is used by 2 execs in symbain, then both exes will have a copy of the libray, right?
But this will be waste of lot of memory.
Forum posts: 1232
Yes.
Thats how static libs work.
There is some cases where its convenient to have it as a lib, but mostly the dll is the way to go, specially if you have a usecase where you want to share the code between several exes.
Dlls impose a bit of extra work in keeping your APIs binary compatible and such.
Forum posts: 159
"You mean to say, if a static library is used by 2 execs in symbain, then both exes will have a copy of the libray, right?
But this will be waste of lot of memory."
But that's exactly what a static library is, and is why there are dynamic libraries.
Your comment about it being a waste of memory implies you have another idea of what a static library is or should be?