2004-10-13 19:51:32 by Todd Vierling | Files touched by this commit (1) |
Log message:
Use INSTALL_LIB. (No functional change.)
|
2004-10-03 02:13:34 by Todd Vierling | Files touched by this commit (908) |
Log message:
Libtool fix for PR pkg/26633, and other issues. Update libtool to 1.5.10
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.
|
2004-09-22 10:10:08 by Johnny C. Lam | Files touched by this commit (703) |
Log message:
Mechanical changes to package PLISTs to make use of LIBTOOLIZE_PLIST.
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".
|
2004-05-22 12:04:21 by Thomas Klausner | Files touched by this commit (6) |
Log message:
Unused.
|
2004-03-29 07:43:36 by Johnny C. Lam | Files touched by this commit (24) |
Log message:
Match the template builtin.mk file in bsd.builtin.mk, and make the two
packages that use builtin.mk files (graphics/xpm and pkgtools/x11-links)
use the new format correctly.
|
2004-03-29 03:19:28 by Todd Vierling | Files touched by this commit (1) |
Log message:
Oops, forgot to bump PKGREVISION.
|
2004-03-29 03:18:41 by Todd Vierling | Files touched by this commit (3) |
Log message:
Obey CFLAGS/CPPFLAGS. Link the binaries with the .o's, not the .lo's
(libtool assumes that .lo means PIC, which is wrong for an end binary;
breaks on Interix where PIC in an end binary is broken)
|
2004-03-10 18:57:15 by Johnny C. Lam | Files touched by this commit (46) | |
Log message:
Split out the code that deals with checking whether the software is
built-in or not into a separate builtin.mk file. The code to deal
checking for built-in software is much simpler to deal with in pkgsrc.
The buildlink3.mk file for a package will be of the usual format
regardless of the package, which makes it simpler for packagers to
update a package.
The builtin.mk file for a package must define a single yes/no variable
USE_BUILTIN.<pkg> that is used by bsd.buildlink3.mk to decide whether
to use the built-in software or to use the pkgsrc software.
|
2004-02-18 17:35:27 by Johnny C. Lam | Files touched by this commit (20) |
Log message:
Reorder some lines so that BUILDLINK_USE_BUILTIN.<pkg> set in the
environment overrides all other settings.
|
2004-02-18 14:33:41 by Johnny C. Lam | Files touched by this commit (19) |
Log message:
Include "../../mk/compiler.mk" to get the value of CC_VERSION before
testing it.
|