o-----------------------------------------------------------------------------o
| Version 0.11.0 ( 29 june 2006)
o-----------------------------------------------------------------------------o
- Make the list of the root bones a vector. So the root bones can be acceded
in C wrapper.
- Add some missing function to access to private variables.
- Add cal3d_converter to the default distribution with manual page and file format
description (tools subdirectory is therefore removed)
- The destructor of CalModel is now virtual.
- Made CalModel noncopyable to prevent shallow pointer copying bugs.
- Use a RefCounted base class and RefPtr smart pointers to hold RefCounted objects.
- Make CalModel destructor nonvirtual
- Improve bounding boxes calculation performance.
- Update the C wrapper.
- Add some function to rotate around axis during the loading.
- When a cycle animation is played, ensure that the last post equals the first pose.
- Extended callback mechanism to pass user data directly instead of making
the callback query for it. This means the callback executable does not have
to link with cal3d.lib and makes many things simpler in CS context.
Also worked around a bug (feature?) in the mixer which thinks that
m_AnimDuration is always 0 for AnimActions. Now the callback uses the
internal time counter of the animation, which is probably more consistent
anyway.
- VC6 and automake fixes. Removed old variables from src/cal3d/Makefile.am.
- 64bit compatibility fixes.
- Patch for reading correctly raw texture on a Big endian cpu (for Mac).
- Fixed bug in updating current anim time when time factor is set to negative.
- Correction in max exporters.
- Update the glew (The OpenGL Extension Wrangler Library).
- Made the refcounted classes derive from RefCounted, and manage
their lifetimes with RefPtr smart pointers.
- Put TinyXML into the cal3d namespace so it doesn't conflict with other
libraries linking with their own TinyXML.
- Fixed bug in updating current anim time when time factor is set to negative,
which resuilted in anim times like -32 instead of between 0 and 2 seconds,
for example. This threw the bone extrapolations way off and made the model
look like garbage until the anim time got back in the right zone. (Keith Fulton)
- GNU/Linux compilation / packaging fixes (-DCAL_16BIT_INDICES is included if
relevant in the .pc)
- Upgraded the guide
o-----------------------------------------------------------------------------o
| Version 0.10.0 ( 12 january 2005)
o-----------------------------------------------------------------------------o
- CalModel::setAbstractMixer and CalAbstractMixer to enable third
party mixers.
- Symbolic names for coreMaterial, coreMesh, coreAnimations loaded
by coremodel.{h,cpp}
- Add functions to control force of the spring system
- CalHardwareModel : a object to store and to compute information
needed to do hardware vertex skinning.
- Add a time factor to allow reverse time of sync animation.
- Most of the math functions are now inline.
- Add an option to stop a action animation at the end.
- Add functions to rescale a core model,
but this can be done only before creating the CalModel.
- Fix in the XML loader
- Add a function to compute the global bounding box of the model.
- Rename calculateBoundingBox to calculateBoundingBoxes.
- Add reference counting. Core* objects can be
now shared between several coremodel correctly.
- Modify the XML file format to be XML valid
- Added animation callbacks.
- Added Maya exporter.
- create/destroy functions removed.
- Add a "stride" argument to getVertices(), getNormals() ...
pkglint --only "https instead of http" -r -F
With manual adjustments afterwards since pkglint 19.4.4 fixed a few
indentations in unrelated lines.
This mainly affects projects hosted at SourceForce, as well as
freedesktop.org, CTAN and GNU.
Problems found with existing digests:
Package fotoxx distfile fotoxx-14.03.1.tar.gz
ac2033f87de2c23941261f7c50160cddf872c110 [recorded]
118e98a8cc0414676b3c4d37b8df407c28a1407c [calculated]
Package ploticus-examples distfile ploticus-2.00/plnode200.tar.gz
34274a03d0c41fae5690633663e3d4114b9d7a6d [recorded]
da39a3ee5e6b4b0d3255bfef95601890afd80709 [calculated]
Problems found locating distfiles:
Package AfterShotPro: missing distfile AfterShotPro-1.1.0.30/AfterShotPro_i386.deb
Package pgraf: missing distfile pgraf-20010131.tar.gz
Package qvplay: missing distfile qvplay-0.95.tar.gz
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.
This changes the buildlink3.mk files to use an include guard for the
recursive include. The use of BUILDLINK_DEPTH, BUILDLINK_DEPENDS,
BUILDLINK_PACKAGES and BUILDLINK_ORDER is handled by a single new
variable BUILDLINK_TREE. Each buildlink3.mk file adds a pair of
enter/exit marker, which can be used to reconstruct the tree and
to determine first level includes. Avoiding := for large variables
(BUILDLINK_ORDER) speeds up parse time as += has linear complexity.
The include guard reduces system time by avoiding reading files over and
over again. For complex packages this reduces both %user and %sys time to
half of the former time.
since they always need a C compiler, even when the source code is
completely in C++.
For some other packages, stated in the comment that a C compiler is
really not needed.
and add a new helper target and script, "show-buildlink3", that outputs
a listing of the buildlink3.mk files included as well as the depth at
which they are included.
For example, "make show-buildlink3" in fonts/Xft2 displays:
zlib
fontconfig
iconv
zlib
freetype2
expat
freetype2
Xrender
renderproto
RECOMMENDED is removed. It becomes ABI_DEPENDS.
BUILDLINK_RECOMMENDED.foo becomes BUILDLINK_ABI_DEPENDS.foo.
BUILDLINK_DEPENDS.foo becomes BUILDLINK_API_DEPENDS.foo.
BUILDLINK_DEPENDS does not change.
IGNORE_RECOMMENDED (which defaulted to "no") becomes USE_ABI_DEPENDS
which defaults to "yes".
Added to obsolete.mk checking for IGNORE_RECOMMENDED.
I did not manually go through and fix any aesthetic tab/spacing issues.
I have tested the above patch on DragonFly building and packaging
subversion and pkglint and their many dependencies.
I have also tested USE_ABI_DEPENDS=no on my NetBSD workstation (where I
have used IGNORE_RECOMMENDED for a long time). I have been an active user
of IGNORE_RECOMMENDED since it was available.
As suggested, I removed the documentation sentences suggesting bumping for
"security" issues.
As discussed on tech-pkg.
I will commit to revbump, pkglint, pkg_install, createbuildlink separately.
Note that if you use wip, it will fail! I will commit to pkgsrc-wip
later (within day).
USE_TOOLS and any of "autoconf", "autoconf213", "automake" or
"automake14". Also, we don't need to call the auto* tools via
${ACLOCAL}, ${AUTOCONF}, etc., since the tools framework takes care
to symlink the correct tool to the correct name, so we can just use
aclocal, autoconf, etc.
in the process. (More information on tech-pkg.)
Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and
installing .la files.
Bump PKGREVISION (only) of all packages depending directly on the above
via a buildlink3 include.
All library names listed by *.la files no longer need to be listed
in the PLIST, e.g., instead of:
lib/libfoo.a
lib/libfoo.la
lib/libfoo.so
lib/libfoo.so.0
lib/libfoo.so.0.1
one simply needs:
lib/libfoo.la
and bsd.pkg.mk will automatically ensure that the additional library
names are listed in the installed package +CONTENTS file.
Also make LIBTOOLIZE_PLIST default to "yes".
by moving the inclusion of buildlink3.mk files outside of the protected
region. This bug would be seen by users that have set PREFER_PKGSRC
or PREFER_NATIVE to non-default values.
BUILDLINK_PACKAGES should be ordered so that for any package in the
list, that package doesn't depend on any packages to the left of it
in the list. This ordering property is used to check for builtin
packages in the correct order. The problem was that including a
buildlink3.mk file for <pkg> correctly ensured that <pkg> was removed
from BUILDLINK_PACKAGES and appended to the end. However, since the
inclusion of any other buildlink3.mk files within that buildlink3.mk
was in a region that was protected against multiple inclusion, those
dependencies weren't also moved to the end of BUILDLINK_PACKAGES.
