3

I dont think my question here was answered here already. So here it is, I have a static library that I maintain and update periodically. I also update the version number correctly. Now my application which uses this library must link to exactly the same version of the library and not to the older or newer ones. One thing I tried was to use predefined macros in the libraries header file and check it in my application. It worked, but in that way you can only ensure the correct header files. Is there any technique so that the linking will fail if it is the wrong library?? I hope the question is somewhat clear.

Hari

Hari
  • 97
  • 1
  • 8
  • Don't forget to accept the answer you consider most useful. That's the checkmark that you see under the answer score. You should do that for all your questions where you've received one or more helpful answers (one selection per question). – Jonathan Leffler Dec 21 '10 at 08:09

2 Answers2

3

All you need is a unique symbol related to the version number for example:

int version_1_1_5=0;

in the library and some use of it in the application, for example:

extern int version_1_1_5; //decl
int *p = &version_1_1_5;  // use
Yttrill
  • 4,725
  • 1
  • 20
  • 29
  • The difficulty here is ensuring that the user always references the version variable. The header might do something like: `static const int *lib_version = &lib_version_1_1_5;` so that each object file that includes the header references the library version it was compiled with. – Jonathan Leffler Dec 20 '10 at 08:17
0

I'm not sure that I'd recommend it, but...

The header could include:

#define LIB_VERSION_SUFFIX _3_17

#define LIB_PASTER(x, y)    x ## y
#define LIB_EVALUATOR(x, y) LIB_PASTER(x, y)
#define LIB_FUNCTION(x)     LIB_EVALUATOR(x, LIB_VERSION_SUFFIX)

#define lib_functionA LIB_FUNCTION(lib_functionA)

extern int lib_functionA(const char *, int);

Etc.

The user of the code writes in terms of the undecorated function names (lib_functionA), while the header ensures that the correct version suffix is appended.

You do not necessarily have to modify every function; you do need to ensure that some function that will always be used is adorned with the version number. If there is an initialization function (lib_init(), perhaps), then use that. You could do it to a variable; the hard part then is ensuring that the variable is referenced in each program.

Note that it is more usual to ensure that the interface to a library remains unchanged across versions so that programs can be linked with any version without needing compilation.

Jonathan Leffler
  • 730,956
  • 141
  • 904
  • 1,278
  • thanks everyone. Jonathan, the method you mentioned seems to be the better one. Thanks very much Jonathan. – Hari Dec 21 '10 at 07:45