On question #1, what version of GnuCOBOL did you copy into Windows 10? Was it a 32-bit MinGW build (three flavors depending on ISAM support)? or was it 64-bit MinGW build? A CygWIN build? A Microsoft Visual Studio build using MS C++ as the C compiler?
I am more familiar with MinGW 32 bit builds, which normally run in a CMD.EXE shell. You could manually add a shortcut to your start menu/programs list that starts up a CMD.EXE shell and points to the folder containing the MinGW GnuCOBOL compiler.
If you install OpenCobolIDE, that should add the OCIDE GUI to your programs list.
Unfortunately, the final version of OCIDE 4.7.6 only includes the older 32-bit MinGW GnuCOBOL 2.0 Release Candidate 2, although you could install a new GnuCOBOL compiler (like GnuCOBOL 3.0 RC1) and change the OCIDE preferences to compile with a different GnuCOBOL compiler.
On question #2, if you want to export a GnuCOBOL compiled COBOL program to a different Windows PC, you would need to install all the required GnuCOBOL runtime support libraries.
When
I built a simple test using Eliza.cbl, I was able to create a minimal
install folder with the following files:
Directory
of C:\eliza-run
10/24/2017
11:23 PM <DIR> .
10/24/2017
11:23 PM <DIR> ..
10/24/2017
11:23 PM 35,880 eliza.cbl
10/02/2017
01:17 AM 78,196 eliza.exe
10/12/2017
07:42 PM 51,336 eliza-P-Lucida-Console-10.pdf
09/09/2017
05:43 PM 404,398 libcob-4.dll
05/29/2017
03:00 PM 118,444 libgcc_s_dw2-1.dll
09/07/2017
09:14 PM 484,270 libgmp-10.dll
08/31/2013
07:39 PM 1,023,944 libiconv-2.dll
04/30/2014
06:33 AM 124,498 libintl-8.dll
09/07/2017
09:19 PM 126,583 pdcurses.dll
10/24/2017
11:22 PM 1,696 README.txt
I
simply tested until I no longer had any errors for missing library
routines, which were copied from the C:\GnuCOBOL\bin folder. If I
were to do this for a larger package, I would need to include
“cobcrun.exe” from the GnuCOBOL\bin folder (for .dll main programs) and
either “libvbisam-1.dll” or “libdb-6.2.dll” from the
C:\GnuCOBOL\bin folder, for either VBISAM or Berkeley DataBase
support for Indexed Sequential files.
http://www.arnoldtrembley.com/
From: "gnucobol-users-request@xxxxxxx" <gnucobol-users-request@xxxxxxx>
To: gnucobol-users@xxxxxxx
Sent: Saturday, June 2, 2018 11:00 AM
Subject: GnuCOBOL-users Digest, Vol 8, Issue 1
Send GnuCOBOL-users mailing list submissions to
To subscribe or unsubscribe via the World Wide Web, visit
or, via email, send a message with subject or body 'help' to
You can reach the person managing the list at
When replying, please edit your Subject line so it is more specific
than "Re: Contents of GnuCOBOL-users digest..."
Today's Topics:
1. Install on MSWindows 10 (John Culleton)
----------------------------------------------------------------------
Message: 1
Date: Fri, 1 Jun 2018 11:54:55 -0700
From: "John Culleton" <sales@xxxxxxxxxxxxxxxx>
To: <gnucobol-users@xxxxxxx>
Subject: Install on MSWindows 10
Message-ID: <fd6b92e76b2245729ef0da01b045dd27@xxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset="us-ascii"
Mswin is my least favorite OS. However for a particular application I need
to be able to send a GNU-COBOLexecutable to end users who use that OS.
I went through all the steps t o copy GNU-COBOL onto MSWindoes-10. But it
does not show up as an available program on MSWin 10. t
Would some kind sole suffest way to get it to show up o the list of
available programs?
Second question. Does my user's computer need to have Gnu-COBOL installed
before they can run an executable GNU-COBOL ?
All replies appreciated.
John Culleton
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gnu.org/archive/html/gnucobol-users/attachments/20180601/377e9510/attachment.html>
------------------------------
Subject: Digest Footer
_______________________________________________
GnuCOBOL-users mailing list
------------------------------
End of GnuCOBOL-users Digest, Vol 8, Issue 1
********************************************
