=========================== 0.8.11 ========================
2008-06-02 Tor Lillqvist <tml@novell.com>
Bug 536165 - Make libIDL correctly parse cl's pre-processor output
* lexer.l: Further change needed when using MSVC's cl.exe as the
preprocessor. Patch by Marcelo Vanzin.
2008-05-19 Tor Lillqvist <tml@novell.com>
Bug 522697 - Patch: make libIDL work with Microsoft's compilers
Patch by Marcelo Vanzin, applied with modifications.
* configure.in: Define Automake confitional OS_WIN32.
* Makefile.am: Use --export-symbols libIDL.def on Windows.
* Makefile.msc.in: Significant changes. Build a DLL with the same
name as libtool does. Use pkg-config.
* util.c: Make it work also in the !HAVE_CPP_STDIN && !HAVE_SYMLINK case.
* util.h: Make __IDL_tmp_filename const.
* include/libIDL/IDL.h.in: Rework the dllimport logic. Use
LIBIDL_VAR to decorate imported variables, similar to
GLIB_VAR. Unlike Marcelo's patch, I decided not to decorate
functions. Maybe later I can be convinced it would be a good idea,
but for now just use the .def file to export them and let them be
imported automatically.
* README.win32
* libIDL.def: Update.
2008-03-18 Christian Persch <chpe@gnome.org>
* configure.in: Update glib version req. Bug #517088, patch by
Mart Raudsepp.
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).
file's sole purpose was to provide a dependency on pkg-config and set
some environment variables. Instead, turn pkg-config into a "tool"
in the tools framework, where the pkg-config wrapper automatically
adds PKG_CONFIG_LIBDIR to the environment before invoking the real
pkg-config.
For all package Makefiles that included pkg-config/buildlink3.mk, remove
that inclusion and replace it with USE_TOOLS+=pkg-config.
* use modern automake rather than 1.4 (James Henstridge)
* Fix a couple of warnings from sparse (Kjartan Maraas)
* Fix parsing of 'const octet' (Jules Colding)
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.
