Build Status

JVCL Build status

This document describes the current build status of the JVCL. The dates below are the most recent dates at which a member of the JVCL verified that it builds for a given version of Delphi, C++ Builder and Kylix. If you experience problems while building the JVCL, please ensure you are using a package from a date that it was known to build at.

Target	Date	User	Build	Installation
C++ Builder 5	2007-01-26 20:40 UTC	obones	ok	ok
C++ Builder 5 standard
C++ Builder 6	2007-01-26 20:40 UTC	obones	ok	ok
C++ Builder 6 personal
Delphi 5	2007-01-26 20:40 UTC	obones	ok	ok
Delphi 5 standard
Delphi 6	2007-01-26 20:40 UTC	obones	ok	ok
Delphi 6 personal	2003-12-05 01:00 UTC	ahuser	ok	ok
Delphi 7	2004-06-25 10:30 UTC	ahuser	ok	ok
Delphi 7 personal
Delphi 2005
Borland Developer Studio 2006	2007-01-26 20:40 UTC	obones	ok	ok
Kylix 3

The dates are presented according to the ISO standard (YYYY-MM-DD) and the hours are all adjusted to UTC time as the JVCL members are located everywhere in the world.

Notes:

If a given target above is missing a verification date and you can verify that the target does build and/or install cleanly, please contact the JVCL team and let us know so we can update this page. To contact us, either post a message in the newsgroups at news://forums.talkto.net/jedi.vcl or post a new bug report in our bugtracker at http://jvcl.sf.net/mantis.
This document is only an indication of the status of the JVCL. Even if you take the package that is supposed to build according to this page, it may not. This is because some developers may have added or modified files between the time of the verification and the time of the generation of the package. If this is the case, do not hesitate to mention it to us and please be assured that we will do our best to avoid this situation.
The date and time indicated for the packages themselves are those of the server on which they are hosted. It is believed to be Pacific Standard Time, meaning that you have to add 8 hours to the time to have it in UTC. We will try to check the JVCL status around 08:45 UTC to limit the occurence of the situation described earlier. However, this may not always be possible, depending on the local time for the developers.