On Sun, 31 Oct 2010 03:51:38 +0200, Dave Plater
Does this mean that it isn't necessary to include the .so.0 link in the rpm?
It isn't strictly needed but it won't hurt to do so. To check just cd into a directory containing the library file and as root do 'ldconfig -n .' and you'll see it created the symlink.
I've seen quite a few packages with it included.
Yes, it seems that only very few people know that. Plus most packages use libtool for handling libraries and it doesn't special case linux when it comes to installation.
Their SConstruct and SConscripts layouts are quite different from openCOLLADA so unfortunately I couldn't use their ideas. I can't go messing up the collada windows and mac builds when I have their trust.
If done right, it shouldn't mess with windows or mac builds in any way as the needed changes are Linux specific. So given that it seems like scons does differentiate by OS the change should be doable. But it definitely will need solid scons and python knowledge.
I still don't quite understand the libtool versioning, current is obviously the major version number incremented when the api changes, the age.revision part is the confusing part
I found the description of the libtool versioning in libtool.info rather precise. From what you write I guess you did read info '(libtool.info.gz)Libtool' versioning which part don't you understand? I agree it is a more difficult to understand as it is a more powerful system then simply using the version number of the project. The latter doesn't show in any way that the libraries developers do watch ABI compatibility and change soname majors when they do incompatible ABI changes (like changing the number and/or types of function parameters or changing the size of structs).
but your use of major.minor.patch is clearer. Would the patch number indicate a change between releases?
It's a matter of definition. It seems most developers do think about project/package versioning but do not think about library versioning or ABI compatibility.
Does cmake have a library versioning system?
I have no idea as I've never really used anything other than classic make.
I will attack the scons built in library versioning and soname matter when I've sorted out blender.
Do try and to get some scons help somewhere. There should be mailing lists, usenet groups or web forums where you can get the suport you need for that task.
Unfortunately blenders ui generation is quite different to the norm which makes it difficult for me to use gdb.
Looks like you've decided to tackle a serious beast :) Well, as a german saying goes 'much enemy, much honour' ;-) I whish you luck. Philipp -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org