To start, real novice with Windows. Downloaded the package; when I CD to the gnucobol directory I get 'configure' is not recognized as an internal command ...
If you've installed a pre-built binary for windows, then open a CMD.EXE windows and navigate to the folder where the GnuCOBOL compiler is installed. Run the "testgc.cmd" script to compile a test the "testfunc.cob" program.
In normal use, run the "set_env.cmd" script to set the GnuCOBOL compiler environment variables and update the path. Then "cd" to the folder where your COBOL source code will reside. You can use the "gcx.cmd" script included in the package to compile a COBOL executable.
You will need to run the "set_env.cmd" script anytime you open a new CMD.EXE shell window to compile or run COBOL programs. It is possible to make all the PATH and environment variable changes permanent, but that causes problems when you need to move the compiler to a differently named folder, or install a newer version of the compiler.
The README.txt file included in the binaries is part of the GnuCOBOL source code package, and refers to building the compiler, which is already done for you.
If you have other questions about getting started with GnuCOBOL, please feel free to ask them in this forum.
Kind regards,
Arnold
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
What 'package' did you download - you can download the whole kit/kaboodle from : https://www.arnoldtrembley.com/GnuCOBOL.htm
see : GnuCOBOL Compiler install binaries - for with BDB / with VBIsam or without both.
NO BUILDING REQUIRED>
Unless you're trying to 'build' it from scratch - in which case - using what ????
Last edit: David Wall 2022-02-25
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
To start, real novice with Windows. Downloaded the package; when I CD to the gnucobol directory I get 'configure' is not recognized as an internal command ...
How do I execute 'configure' ?
Wayne
If you've installed a pre-built binary for windows, then open a CMD.EXE windows and navigate to the folder where the GnuCOBOL compiler is installed. Run the "testgc.cmd" script to compile a test the "testfunc.cob" program.
In normal use, run the "set_env.cmd" script to set the GnuCOBOL compiler environment variables and update the path. Then "cd" to the folder where your COBOL source code will reside. You can use the "gcx.cmd" script included in the package to compile a COBOL executable.
You will need to run the "set_env.cmd" script anytime you open a new CMD.EXE shell window to compile or run COBOL programs. It is possible to make all the PATH and environment variable changes permanent, but that causes problems when you need to move the compiler to a differently named folder, or install a newer version of the compiler.
The README.txt file included in the binaries is part of the GnuCOBOL source code package, and refers to building the compiler, which is already done for you.
If you have other questions about getting started with GnuCOBOL, please feel free to ask them in this forum.
Kind regards,
Arnold
Thanks for the help! This put me on the right track; I had downloaded the wrong package.
mod edit for some reply-to
Last edit: Brian Tiffin 2022-02-26
What 'package' did you download - you can download the whole kit/kaboodle from :
https://www.arnoldtrembley.com/GnuCOBOL.htm
see : GnuCOBOL Compiler install binaries - for with BDB / with VBIsam or without both.
NO BUILDING REQUIRED>
Unless you're trying to 'build' it from scratch - in which case - using what ????
Last edit: David Wall 2022-02-25