[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [GnuCOBOL-users] Shipping exe files to others.
From: |
Simon Sobisch |
Subject: |
Re: [GnuCOBOL-users] Shipping exe files to others. |
Date: |
Fri, 24 Feb 2017 19:33:51 +0100 |
User-agent: |
Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1 |
Hi John,
if you ship libcob and its dependencies along with your executable it
should work directly (technical).
Keep in mind to check the license though, for example linking against
and distributing libdb may force you to ship your COBOL code, too (when
the "client" installs this library via Oracle's installer and just adds
"your" libcob and executable this likely isn't a problem).
If your client has a unix machine I'd always suggest to install GnuCOBOL
on the host as this would be a perfect system match - and only
distribute your compiled COBOL binaries (ideally with its sources to
give the client the same freedom that you enjoy with GnuCOBOL, but this
is not enforced by GnuCOBOL's license).
Simon
> Christopher Davenport <address@hidden> wrote:
>
> My binary executables work remotely on the same base architecture. Can't
> speak any more generally.
>
> On Fri, Feb 24, 2017 at 12:16 PM John Culleton (home) <address@hidden> wrote:
>
> > When compiling a program into an exe file for distribution elsewhere must
> > the new user also have Gnu Cobol
> > installed?
>
> > John Culleton