Re: [Tiny-cobol-users] Up and running.

[John R. C. <jo...@we...>]

On Thursday 04 August 2005 11:44 am, David Essex wrote:
> John R. Culleton wrote:
>  > Well I have TC up and running and have recompiled some of my
>  > recent OpenCobol efforts. The ncurses bit works as expected.
>  >
>  > I find that TC is less forgiving than either OpenCobol or some
>  > commercial complers I have used about things like legacy names
>  > and blank lines, at least in fixed (-F) format. I suppose I can
>  > make all the blank lines into comments with an asterisk in
>  > column 7. And I find I have to comment things like AUTHOR,
>  > INSTALLATION etc. But one must take the bitter with the sweet.
>
> You should not have to place asterisk in column 7 for statements like
> AUTHOR, INSTALLATION, or blanks lines.
>
> What kind of problems have you encountered, and could give an example.
>
> BTW, if like to work with fixed format, you can set it as the default
> using the TC compiler resource file 'htcbolrc'.
>
> # Specify COBOL program default input format
> # free format  -> PGM_FORMAT_FREE
> # fixed format -> PGM_FORMAT_FIXED
> # (compiler default=free format)
> #PGM_FORMAT_FREE
> PGM_FORMAT_FIXED
>
>  > I have a general question even at this early stage. If I wish to
>  > move programs to another Linux system what must I take along beyond
>  > the program itself? I presume Berkeley DB is essential. How much
>  > more? Is it required to do a complete install similar to the
>  > devlopment machine?
>
> Once compiled, a TC compiled program is just another binary executable.
> And as with other binaries, is dependent on which shared libraries were
> used to compile/link the source.
>
> Example:
> $ldd test19a
> libhtcobol.so.0 => /usr/local/lib/libhtcobol.so.0 (0x40014000)
> libdb.so.3 => /lib/libdb.so.3 (0x4001a000)
> libdl.so.2 => /lib/libdl.so.2 (0x40053000)
> libm.so.6 => /lib/libm.so.6 (0x40056000)
> libc.so.6 => /lib/libc.so.6 (0x40072000)
> ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
>
>
> If the other Linux system is only used to run the COBOL programs, then
> only the TC run-time (if compiled as a shared library) and the run-time
> config file 'htrtconf'.
> The location of the run-time config file is set when TC is configured
> (ex: /usr/local/share/htcobol), but can be also set using the
> 'TCOB_RTCONFIG_PATH' environment variable.
>
> Example:
> export TCOB_RTCONFIG_PATH=/usr/share/htcobol
> export TCOB_OPTIONS_PATH=/usr/share/htcobol
>
> Hope this helps.

It helps a great deal! I had fun going through the htcobolrc
file and setting things to my preference---program listings and
everything! 

I set the link options to link to a static library to ensure
greater portability. So to transport such a binary I need the
binary, the htcobolrc file, a path to the htcobolrc file, and
what else? 

TIA

-- 
John Culleton