Menu

How to install gnucobol on windows 11, without using msys2 and mingw.

2025-01-27
2025-02-11
  • celsofigueiredo

    celsofigueiredo - 2025-01-27

    Prezados usúarios do gnucobol.

    Estou querendo instalar e usar o gnucobol, sem precisar instalar o msys2 e o mingw. É possivel isso. Na pagina do Arnold Trembley, tem vários links para download, mas todos precisar instalar tanto o msys2 ou o mingw.
    Eu só quero usar o gnucobol no windows 11 sem instalar o mingw e msys2 é possivel e qual o link para download.

    Dear gnucobol users,

    I want to install and use gnucobol without having to install msys2 and mingw. Is this possible? On Arnold Trembley's page, there are several download links, but all of them require installing either msys2 or mingw.

    I just want to use gnucobol on Windows 11 without installing mingw and msys2. Is this possible and what is the download link?

    Celso

     
  • Arnold Trembley

    Arnold Trembley - 2025-01-27

    Thank you very much for your note.

    You do not need to install either MinGW or MSYS2 to install and use GnuCOBOL on Windows. Those tools are used to build GnuCOBOL, but are not needed to run the GnuCOBOL compiler or your compiled COBOL programs.

    Here are the most common download binaries that you might want to use on Windows 11:

    https://www.arnoldtrembley.com/GC32-BDB-SP1-rename-7z-to-exe.7z

    https://www.arnoldtrembley.com/GC32M-BDB-x64.7z

    Simply download one of these compilers and save to your hard drive. Then rename the file extension from ".7z" to ".exe". The file can then be executed as a self-installing archive. The install will ask you for a path/foldername to install to, and I would suggest using something like "C:\GC32", but you are free to use any drive or foldername you like, as long as the path has no embedded spaces.

    Then search the folder where you installed GnuCOBOL for a file named "STARTHERE.txt". Reading that file will give you some additional notes for setting up the compiler and using it.

    On Windows, the GnuCOBOL compiler and its compiled COBOL programs will run in a CMD.EXE window (including a Windows Terminal CMD.EXE session). You will need to run set_env.cmd to set GnuCOBOL environment variables before compiling or executing COBOL programs. This is covered in the STARTHERE.txt file.

    You must supply your own text editor for editing COBOL source files, but there are several free ones available, including Notepad++, VSCodium, and SPFSE 365.

    I recommend keeping your COBOL source code and compiled programs in a different folder from your GnuCOBOL compiler folder.

    If you need additional help, please feel free to ask questions in this forum. You can also review these recent threads that are related to your question:

    GnuCOBOL quick start for Windows
    https://sourceforge.net/p/gnucobol/discussion/contrib/thread/41432778b6/

    https://sourceforge.net/p/gnucobol/discussion/help/thread/7096452742/

    Kind regards,

    Arnold

     
    👍
    1
  • celsofigueiredo

    celsofigueiredo - 2025-01-29

    Prezado Arnold Trembley .

    Obrigado por suas dicas e informações, sobre como instalar o gnucobol mo windows.
    Já instalei aqui, mas falta começar a testar. Qual desses três editores é melhor para usar o gnucobol: OpenCobolIDE, VSCodium ou Microsoft Visual Studio. Em relação a configuração, eu sou um zero a esquerda. No OpenCobolIDE, consegui configurar mais ou menos. Não sei como configurar o VSCodium e o Microsoft Visual Studio, quais apps devo instalar e configurar, dentro desses dois ultimos. Esses dois links que você passou para mim, é a ultima versão do GnuCOBOL.

    Celso.

    Dear Arnold Trembley.

    Thank you for your tips and information on how to install gnucobol on Windows.

    I have already installed it here, but I still need to start testing it. Which of these three editors is best for using gnucobol: OpenCobolIDE, VSCodium or Microsoft Visual Studio. Regarding the configuration, I am a complete zero. In OpenCobolIDE, I was able to configure it more or less. I don't know how to configure VSCodium and Microsoft Visual Studio, or which apps I should install and configure within the latter two. These two links you sent me are the latest version of GnuCOBOL.

    Celso.

     
    • Simon Sobisch

      Simon Sobisch - 2025-01-29

      OpenCOBOLIDE had its last release 9 years ago, officially out of maintenance since 8 years and is "archived" since 7 years, after reeving multiple open issues (and since then there are only more).
      If you have that in any environment and are fine with it - keep it, but don't expect it to even work on another machine/after an update.

      GixIDE is a totally different approach, but "kind of the same spirit". While its last release is 3 years old, there's at least not deprecation on it and I know that it works (including the debugging) with GnuCOBOL 3.2 as well; it also includes a debugging option.

      vsocde (all binary versions, including VSCodium and the one with proprietary extensions and telemetry by default "MS Visual Studio Code") work quite well with SuperBOL Studio (needs GC32+ for the debugging option). This extension is under good current maintenance and I personally found it working well, with an issue tracker (and this forum) that helps if there are any issues with the setup.

       
  • celsofigueiredo

    celsofigueiredo - 2025-01-29

    Prezado Arnold Trembley.

    Essas versões que você me passou é a GC32+. sim ou não?
    Como eu devo configurar o VSCodium, para usar o GnuCobol?
    No linux Debian 12, desisti de usar o GnuCobol, devido a enorme quantidade de configurações, para usar o GnuCobol por completo.

    Dear Arnold Trembley.

    These versions you sent me are the GC32+, yes or no?
    How should I configure VSCodium to use GnuCobol?
    On Linux Debian 12, I gave up using GnuCobol due to the huge amount of configurations, to use GnuCobol completely.
    Celso.

     
    • Simon Sobisch

      Simon Sobisch - 2025-01-29

      On Debian just do sudo apt install gnucobol and you are ready - no config at all (this gets you 3.1.2, if you want 3.2 without compiling on your own you could do sudo apt remove gnucobol && sudo apt autoremove, then wget "https://cobolworx.com/pages/downloads/gnucobolcw_3.2-4_amd64.deb", followed by sudo apt install ./gnucobolcw_3.2-4_amd64.deb; and if you want to use COBOLworx' debugging extensions additional wget "https://cobolworx.com/pages/downloads/cblgdb_5.4.2_amd64.deb" && sudo apt install ./cblgdb_5.4.2_amd64.deb)

      If you use the 3.2+ package from Arnold/Chuck then you likely want to do some permanent configuration in the user's env vars; if you use OCamlPro's msi installer (GC 3.2+ [currently from last June]) from https://superbol.eu/en/developers/windows-aio-3.2/ then the environment is already adjusted.

      For the VSCodium setup - in the "simple" case installing "superbol" then do some minor config like copybook search folder is enough, see https://open-vsx.org/extension/OCamlPro/SuperBOL for some details and feel free to ask at their issue tracker if something is unclear (works on Debian as well as on Windows [with any 3.2+ binaries configured system-wide]).

       
    • Eugenio Di Lorenzo

      Hi Celso,
      some time ago I started to prepare a document that illustrates the configurations needed to use VSCODE with GnuCOBOL.
      I have not completed the document but it can still be a reference to understand some useful things so I attach it even if it is only a draft.

       
  • Chuck Haatvedt

    Chuck Haatvedt - 2025-01-30

    Celso,

    what is your background of experience with COBOL ?

    Was it by any chance on an IBM mainframe system ?

    if so there are very good Windows clones of the ISPF editor available for free.

    if you are interested here is a link to where you can download SPF/SE 365

    https://github.com/michaelknigge/spf-editor/tree/main/binaries

    the SPFSE365-3454.msi file is the installer for the most recent version of SPF/SE 365.

    If you are familiar with mainframe ISPF you should be right at home with SPF/SE 365.

         Chuck Haatvedt
    
     
  • celsofigueiredo

    celsofigueiredo - 2025-01-30

    Dear Chuck, I am only a Cobol user, I worked almost all my life with mainframe Cobol, (now I am retired) but recently I decided to venture into GnuCobol. Remember, I am just a user; I do not understand anything about configuration (I can't even configure it with a cake recipe). But my current interest is GnuCobol. But I also came across this alphabet soup, as there are many versions. That's why I have difficulty choosing and installing GnuCobol on Windows. I'm even having difficulty configuring VSCodium to use GnuCobol Cobol. Even though my interest now is GnuCobol, I'll try to test this link you sent me. Thanks again for trying to help this GnuCobol user.

     
  • celsofigueiredo

    celsofigueiredo - 2025-01-30

    Prezados usúarios do gnucobol.

    Depois de pesquisar qual editor usar, entre o OpenCobolIDE, VSCodium e Microsoft Visual Studio Code, optei por usar o VSCodium. Mas estou tendo alguns problemas, tipo a identação do Cobol, Não consigo mudar a identação que vem instalada; para usar com cobol. E também não sei por onde dar a função de executar o programa cobol. Só consigo fazer pela linha de comando. Onde consigo um bom manual de configuração do VSCodium.

    Dear gnucobol users,

    After researching which editor to use, between OpenCobolIDE, VSCodium and Microsoft Visual Studio Code, I chose to use VSCodium. But I'm having some problems, such as the Cobol indentation. I can't change the indentation that comes installed; to use with cobol. And I also don't know where to give the function to run the cobol program. I can only do it from the command line. Where can I find a good VSCodium configuration manual?

    Celso

     
  • Anonymous

    Anonymous - 2025-01-30

    Have you checked that superbol link on openvsx I gave before?
    If you have - did you create questions concerning its setup to their issue tracker first?

     
  • celsofigueiredo

    celsofigueiredo - 2025-01-30

    Celso Henrique Figueiredo celsofigueiredo@gmail.com
    16:56 (há 0 minuto)
    para chaat

    Prezado Chuck.
    Esse link que você me passou é para ambiente windows.
    Já parei de mexer com cobol mainframe, desde que me aposentei. Mas de vez em quando eu acesso um ambiente mainframe e fico relembrando.
    Esse link é um ambiente completo para mainframe.
    Para que eu não esqueça o Cobol, eu comecei a usar o GNUCOBOL. Eu já não sou fã dessa sopa de letras do mainframe e agora o GnuCobol, está indo para o mesmo caminho. É como eu disse antes, sou usuário de sistema, seja ele Mainframe ou gnucobol. Não sei nada de instalação e configuração. Mas obrigado por você ter me passado esse link de mainframe. Atualmente estou usando o GnuCobol em ambiente windows 11 e em ambiente linux DEBIAN 12.
    E tudo isso para não esquecer essa maravilhosa linguagem que é COBOL.

    Celso

    Dear Chuck,

    This link you sent me is for a Windows environment. I've stopped working with mainframe COBOL since I retired. But every now and then I access a mainframe environment and I remember it. This link is a complete environment for mainframe. So that I don't forget COBOL, I started using GNUCOBOL. I'm no longer a fan of this mainframe alphabet soup and now GnuCobol is going down the same path. It's like I said before, I'm a system user, be it Mainframe or GnuCobol. I don't know anything about installation and configuration. But thank you for sending me this mainframe link. I'm currently using GnuCobol in a Windows 11 environment and in a Linux DEBIAN 12 environment. And all this so that I don't forget this wonderful language that is COBOL.

    Celso

     
  • celsofigueiredo

    celsofigueiredo - 2025-02-04

    Prezados usuários do GnuCobol
    Eu usei os comandos:
    cobc --info
    cobc --version
    As respostas deram corretas.
    Mas quando fui usar o coamndo:
    cobc -v (cobc --verbose)
    Deu o seguinte erro abaixo:
    cobc (GnuCOBOL) 3.3-dev.0
    Built Jun 24 2024 00:47:54 Packaged Jun 23 2024 22:46:58 UTC
    C version (MinGW) "13.2.0"
    loading standard configuration file 'default.conf'
    cobc: error: no input files

    O que eu fiz de errado.

    Dear GnuCobol users
    I used the commands:
    cobc --info
    cobc --version
    The responses were correct.
    But when I tried to use the command:
    cobc -v (cobc --verbose)
    I got the following error:
    cobc (GnuCOBOL) 3.3-dev.0
    Built Jun 24 2024 00:47:54 Packaged Jun 23 2024 22:46:58 UTC
    C version (MinGW) "13.2.0"
    loading standard configuration file 'default.conf'
    cobc: error: no input files

    What did I do wrong?

     
    • Simon Sobisch

      Simon Sobisch - 2025-02-04

      What did I do wrong?

      Nothing - you just asked the compiler to be verbose about what it is doing, which includes a version output during compiles - but you don't gave it any file to compile.

      You may wanted either cobc -v prog.cob (be verbose during compilation) or cobc -vV (= cobc --verbose --version, give verbose version information)?

       
  • celsofigueiredo

    celsofigueiredo - 2025-02-05

    Prezado Simon Sobisch.

    Obrigado por sua ajuda. Pois eu estava pensando que era algum erro. Por isso eu sou um zero a esquerda para instalar e configurar qualquer tipo de soft ou programas de computador. Mesmo com um manual na mão, eu ainda faço errado. Ainda não consegui saber qual é a melhor versão do GnuCOBOL, para ser instalada no windows 11 e tambem, qual seria o melhor editor para usar o gnucobol, sei que existe tres editores: O OpenCobolIDE (desatualizado) o Visual Studio Code e o Visual Codium. E todos eles, tem a bendita configurção para usar o COBOL. Mesmo com um tutorial na mão , não consigo configurar.

    Dear Simon Sobisch,

    Thank you for your help. I was thinking it was some kind of error. That's why I'm such a no-brainer when it comes to installing and configuring any kind of software or computer programs. Even with a manual in hand, I still do things wrong. I still haven't figured out which version of GnuCOBOL is best to install on Windows 11, and also which would be the best editor to use GnuCOBOL. I know there are three editors: OpenCobolIDE (outdated), Visual Studio Code, and Visual Codium. And all of them have the blessed configuration to use COBOL. Even with a tutorial in hand, I can't configure them.

    Celso.

     
  • Sergio Samayoa

    Sergio Samayoa - 2025-02-11

    IMHO the easiest way to get into GNU COBOL is using WSL (Windows Subsystem for Linux) with Ubuntu 22.04.

    Edit COBOL? VS Code + IBM Z Open Editor.
    Of course such plugin only supports IBM's Enterprise COBOL but is quite good.

    But if you passed most of your time working on IBM Mainframes all the new stuff (VS Code, WSL, etc.) may be overwhelming so perhaps is better for you MVS Turnkey: https://www.prince-webdesign.nl/tk5

    In case you want to run modern z/OS with Hercules:
    https://archive.org/details/software?tab=collection&query=mainframe+zos

     
  • celsofigueiredo

    celsofigueiredo - 2025-02-11

    Prezado Sergio Samayoa.
    Obrigado, por me passar mais esses links, mas já me aposentei do cobol mainframe e agora, no meu tempo livre estou aprendendo uma nova forma de programar em COBOL, usando o GnuCOBOL. No meu tempo de cobol mainframe, eu recebia uma tarefa e a fazia. Hoje alem de programar em GnuCOBOL, tenho que configurar o ambiente e outras coisas que não envolvem cobol (no tempo do mainframe, erá só o cobol) hoje alem do GnuCOBOL, tem que fazer muitas configuraçôes, ESSE É O MEU MAIOR PROBLEMA. Pelo menos já consegui compilar e executar, programas simples em GnuCobol usando o Visual Studio Code e o Visual Codium, tanto em Linux Debian 12 e Windows 11 (ruim windows 11).

    Dear Sergio Samayoa.
    Thank you for sending me these links, but I have already retired from mainframe COBOL and now, in my free time, I am learning a new way of programming in COBOL, using GnuCOBOL. Back when I was working on mainframe COBOL, I would receive a task and do it. Today, in addition to programming in GnuCOBOL, I have to configure the environment and other things that do not involve COBOL (back when I was working on mainframe, it would only be COBOL). Today, in addition to GnuCOBOL, I have to do a lot of configuration. THIS IS MY BIGGEST PROBLEM. At least I have managed to compile and run simple programs in GnuCOBOL using Visual Studio Code and Visual Codium, both on Linux Debian 12 and Windows 11 (bad Windows 11).

    Celso

     

Anonymous
Anonymous

Add attachments
Cancel





Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.