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

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

On Friday 05 August 2005 02:48 am, David Essex wrote:
> John R. Culleton wrote:
>  > 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?
>
> The 'htcobolrc' file is only used by TC at compile time to create a
> binary from a COBOL source.
> So I'm confused as to what you mean by 'such a binary'.
> Are you trying to move the TC compiler and run-time, or just the TC
> compiled COBOL programs.
>
> If you are only moving the TC compiled programs, since you are using a
> static TC run-time, all you need are the COBOL program binary(s) and the
> run-time config file 'htrtconf'.
>
First my goal is to move as little as possible, to give the
user an application that will run on any Linux system without
much fuss and feathers. 

Given that goal, is the compiled static binary and the control
file sufficient? Does Berkeley DB need to be moved also or is
that included in the static compiled binary?

Also I need a little help with the htcobolrc file compile
options. Here are the options:
# Specify the compiler default action
# P     - preprocess
# PC    - preprocess,compile
# PCA   - preprocess,compile,assemble
# PCAL  - preprocess,compile,assemble,link to executable
# PCAX  - preprocess,compile,assemble,link to executable
# PCAS  - Preprocess, compile, assemble, link to static library
# PCAM  - Preprocess, compile, assemble, link to shared library
# (compiler default=PCAL)
COMPILE_DEFAULT: PCAL
#COMPILE_DEFAULT: PCAS
#COMPILE_DEFAULT: PCAM
#

Assuming that I want everything rolled into one binary, is the
correct choice PCAS or PCAX?

Also, what is the difference between PCAL and PCAX? They have
identical definitions above. 






> Optional if different from default:
> export TCOB_RTCONFIG_PATH=/usr/local/share/htcobol
>
> On the other hand if you are trying to move (install) the TC compiler
> and run-time, it is best to build it and install it on the system where
> it will be used.
>
> ./configure ...
> make
> Change 'htcobolrc' and 'htrtconf' files as required.
> su ...
> make install
> exit
>
> Note that the Linux linker will use shared libraries by default, if
> available. To avoid this problem compile, and install, only the static
> version of the TC run-time .
>
>
>
>
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> _______________________________________________
> Tin...@li...
> https://lists.sourceforge.net/lists/listinfo/tiny-cobol-users

-- 
John Culleton
Books with answers to marketing and publishing questions:
http://wexfordpress.com/tex/shortlist.pdf

Book coaches, consultants and packagers:
http://wexfordpress.com/tex/packagers.pdf