New token libary seems to ignore BUILD_SHARED_LIBS=0 and VTK_VERSIONED_INSTALL=0
This newly added token library seems to ignore the BUILD_SHARED_LIBS=0 and VTK_VERSIONED_INSTALL=0 build settings. When I build & install current master I get:
(truncated)
-rw-r--r--@ 1 sean staff 3462040 7 Oct 13:42 libvtknetcdf.a
-rw-r--r--@ 1 sean staff 76208 7 Oct 13:42 libvtkogg.a
-rw-r--r--@ 1 sean staff 953936 7 Oct 13:42 libvtkpng.a
-rw-r--r--@ 1 sean staff 1158928 7 Oct 13:42 libvtkpugixml.a
-rw-r--r--@ 1 sean staff 2907992 7 Oct 13:42 libvtksqlite.a
-rw-r--r--@ 1 sean staff 4446760 7 Oct 13:42 libvtksys.a
-rw-r--r--@ 1 sean staff 751992 7 Oct 13:42 libvtktheora.a
-rw-r--r--@ 1 sean staff 1678064 7 Oct 13:42 libvtktiff.a
lrwxr-xr-x@ 1 sean staff 21 7 Oct 13:42 libvtktoken.1.dylib -> libvtktoken.9.3.dylib
-rwxr-xr-x@ 1 sean staff 1154856 7 Oct 13:42 libvtktoken.9.3.dylib
lrwxr-xr-x@ 1 sean staff 19 7 Oct 13:42 libvtktoken.dylib -> libvtktoken.1.dylib
-rw-r--r--@ 1 sean staff 794400 7 Oct 13:42 libvtkverdict.a
Notice how every file:
- is a static library (.a)
- has no version number
except the token libraries which got built:
- as dynamic library (.dylib)
- with a version number (9.3)
This has broken our internal builds that test against VTK master.