[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [platform-swt-dev] abi and versioning
|
>
> Well if that is the case, then essentially that means that
> there is only a major version number for libswt. What
> happens if a bug fix is applied that does not change the
> ABI (or API for that matter)? Typically this would cause
> just a minor version number to be incremented, so that
> existing applications would not need relinking. If
> necessary, the FreeBSD port can start versioning libswt
> independently of the eclipse project, but I'd rather not
> due that because it means I would have to check each
> version myself for ABI compatibility.
>
> What relation, if any, does the directory name have to the
> library version. For example, the Linux RC1 package has:
>
> eclipse/plugins/org.eclipse.swt.gtk_2.1.0/os/linux/x86/libswt-gtk-2130.so
>
> The "2.1.0" refers to the Eclipse version, not the libswt
> version, right?
>
SWT isn't a library either, it is a DLL. Semantics perhaps, but it doesn't
set a SONAME nor do you ever link (-lswt) with it. I am not sure what
the policy is at OTI for upping the number, but it appears gets upped every
4-6 weeks. SWT itself shares a version number with Eclipse (ie: 2.1) while
the DLL is simply incremented over time. You always use a matched set of
swt.jar and libswt*.so for a given platform, so you don't replace one
without replacing the other.
chris
--
Chris McKillop <cdm@xxxxxxx> "The faster I go, the behinder I get."
Software Engineer, QSSL -- Lewis Carroll --
http://qnx.wox.org/