| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| README.md | 2023-12-11 | 6.9 kB | |
| Totals: 1 Item | 6.9 kB | 2 | |
GnuCOBOL nightly builds can be found at the CI build, which is automatically triggered on each build. If there's a failure in the generation of the internal files or building or packaging the sources they will not be seen in the deep links to the last working build below. Note: While the tarballs are passing the internal tests on GNU/Linux, the Windows builds ignore failures when running the internal tests (MinGW/Cygwin, often false-positives) and the VS builds are currently only tested to generate a single module.
Those CI builds include the full source tarball of every recent "working" build (you may click in the build history to see/check messages during build and then on "Artifacts" to get more details/parts than the source tarballs / binary packges).
Note: If you need to use a specific version of a nightly build: please self-host it. The "Artifacts" are automatically deleted after one month of the original build.
Deep links to the latest working builds follow.
GnuCOBOL 3.3 (stable):
Build history - use that URL in the case any of the below don't work
Source tarballs
Documentation only
The following is included in the tarballs above.
Test coverage as HTML
- GnuCOBOL-3.3-dev-coverage.zip (internal testsuite only)
- GnuCOBOL-3.3-dev-coverage-extended.zip (coverage with additional NIST)
Files to compile in non-posix environment
See build_windows/README.txt about how to use it.
ready-to-use-binaries for Win32
Includes GCC 9.2.0, GMP 6.3.0, Berkeley DB 6.0.19 (NC), cJSON 1.7.15, PDCursesMod 4.4.0 with mouse support (wincon, wingui, vt).
Visual Studio builds, packages and depencies
Manually go to the "build jobs" you are interested in (commonly the first "green" one), then the job matching your environment, then visit the "Artifacts".
Warning: Completely untested - other than "builds and can create a single module" (unsupported).
Necessary - not included - build tools are proprietary and hundreds of MB big and compile slow.
Source code (for development/patches/direct updates)
- history/commit log
- web frontend to view files
- command for local checkout:
svn checkout svn://svn.code.sf.net/p/gnucobol/code/branches/gnucobol-3.x gnucobol-devor:
svn checkout https://svn.code.sf.net/p/gnucobol/code/branches/gnucobol-3.x gnucobol-dev
GnuCOBOL 4.0 (testing):
Important notes:
- this version has no backward compatibility to modules created with a previous version; the internal library-number was therefore increased (libcob-5 instead of libcob-4)
- "anything may still change between builds", only use for production if you know what that means.
Source tarballs
Documentation only
The following is included in the tarballs above.
Files to compile in non-posix environment
See build_windows/README.txt about how to use it.
ready-to-use-binaries for Win32
Includes GCC 9.2.0, GMP 6.1.2, Berkeley DB 4.5.20, cJSON 1.7.13, PDCurses for Win32 4.2.0 with mouse support.
Visual Studio builds, packages and depencies
Manually go to the "build jobs" you are interested in (commonly the first "green" one), then the job matching your environment, then visit the "Artifacts".
Warning: Completely untested - other than "builds and can create a single module" (unsupported).
Necessary - not included - build tools are proprietary and hundreds of MB big and compile slow.
Source code (for development/patches/direct updates)
- history/commit log
- web frontend to view files
- command for local checkout:
svn checkout svn://svn.code.sf.net/p/gnucobol/code/trunk gnucobol-early-devor:
svn checkout https://svn.code.sf.net/p/gnucobol/code/trunk gnucobol-early-dev