Commit c5c11bd5 authored by rdubner's avatar rdubner
Browse files

Move the msys2 folder to camelian-packages. Change names

In particular, sfix is now cobcd-sfix, cobst is now cobcd-st, and cprint.py
has become cobcd.py.  The result is that the files deployed to implement the
Camelian/Symas debugging extensions are now all named cobcd*
parent ca34bf02
# Camelian.Systems GnuCOBOL Source Level Debugging Support
This repository contains the development and testing materials for this
package.
It is purposely a private repository with access limited to the
Camelian.Systems team.
These are the source files for building the tools that make up the Symas/Camelian debugging extensions for GnuCOBOL.
You'll need to have Version 3.x-dev, or later, of GnuCOBOL installed to actually make things work.
Building the source, and installing the binaries and scripts into /usr/local, operates as you'd generally expect:
make
sudo make install
Using the extensions is generally a case of using the cobcd script where you'd ordinarily use the cobc program:
Instead of
cobc -x hello.cbl
you instead enter
cobcd -x hello.cbl
After that, you can debug the resulting binary with
gdb ./hello
The extensions' functionality is provided by the information in these folders:
cobcd-st/
cobcd-sfix/
python/
include/
.legacy/ is code that I used along the way, but is currently not involved in production or development, and most likely is thoroughly broken.
bin/ contains utility scripts used during development and deployment
vsdistrib/ contains the .vsix file that provides a Visual Studio Code extension that knows how to use the Symas/Camelian to do source-level debugging of COBOL code in the VSC IDE.
optfde01/ contains a simple program that can be compiled and debugged after you have done the 'make install' The optfde01/.vscode/ subdirectory contains the launch.json and tasks.json files that you'll clone into your own projects.
Feel free to contact me with any questions or problems.
2020-05-07
Bob Dubner
Symas/Camelian
rdubner@symas.com
#!/bin/bash
# FileVersion 2.5
# This script, nominally named cobcd, packages up the process of compiling
# a single COBOL source module and processing it so that gdb can be used for
# source-level debugging of that module. Found in the root folder of the
......
......@@ -34,7 +34,7 @@
#include <fstream>
#include <vector>
#include "../version.h"
#include "../include/version.h"
class FILENAME
{
......
......@@ -72,15 +72,19 @@
<PropertyGroup Label="UserMacros" />
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'">
<LinkIncremental>true</LinkIncremental>
<TargetName>cobcd-sfix</TargetName>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">
<LinkIncremental>true</LinkIncremental>
<TargetName>cobcd-sfix</TargetName>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Release|Win32'">
<LinkIncremental>false</LinkIncremental>
<TargetName>cobcd-sfix</TargetName>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Release|x64'">
<LinkIncremental>false</LinkIncremental>
<TargetName>cobcd-sfix</TargetName>
</PropertyGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'">
<ClCompile>
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment