Next | Query returned 36 messages, browsing 31 to 40 | previous

History of commit frequency

CVS Commit History:


   2005-05-22 22:08:52 by Johnny C. Lam | Files touched by this commit (1035)
Log message:
Remove USE_GNU_TOOLS and replace with the correct USE_TOOLS definitions:

	USE_GNU_TOOLS	-> USE_TOOLS
	awk		-> gawk
	m4		-> gm4
	make		-> gmake
	sed		-> gsed
	yacc		-> bison
   2005-04-11 23:48:17 by Todd Vierling | Files touched by this commit (3539)
Log message:
Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.
   2005-02-23 23:24:35 by Alistair G. Crooks | Files touched by this commit (505)
Log message:
Add RMD160 digests.
   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-16 03:12:15 by Juan Romero Pardines | Files touched by this commit (6) | Imported package
Log message:
Initial import of libjit-0.0.2.

The libjit library implements Just-In-Time compilation functionality. Unlike 
other JIT's, this one is designed to be independent of any particular virtual 
machine bytecode format or language. The hope is that Free Software projects 
can get a leg-up on proprietry VM vendors by using this library rather than 
spending large amounts of time writing their own JIT from scratch.

This JIT is also designed to be portable to multiple archictures. If you run 
libjit on a machine for which a native code generator is not yet available, 
then libjit will fall back to interpreting the code. This way, you don't need 
to write your own interpreter for your bytecode format if you don't want to.


Next | Query returned 36 messages, browsing 31 to 40 | previous