i think i tried this and got errors. it said you cant use using in procedure when expecting an executable.
my compile line would look like this..
g++-shared-omyptr.dlltestabc.c-Wl,--out-implib,myptr.lib
RESET
cd~/cobjapi-SWING/examples_simple
pwd# Try to remove dialog.o, if it existsif[-f"dialog.o"];thenrmdialog.o
if[$?-ne0];thenecho"Failed to remove dialog.o, but continuing script."fielseecho"dialog.o does not exist, skipping removal."fi# Try to remove dialog.o, if it existsif[-f"dialog.cbsql"];thenrmdialog.cbsql
if[$?-ne0];thenecho"Failed to remove dialog.o, but continuing script."fielseecho"dialog.o does not exist, skipping removal."fiecho'gixpp'
gixpp-e-S-idialog.cbl-odialog.cbsql
echo'gixsql'
gixsqldialog.cbldialog.cbsql-S-I.
echo'cobc'
cobc-x-v-fixeddialog.cbsqlcobjapi.ojapilib.oimageio.ofileselect.o\-I.-L"c:\msys64\mingw64\bin"-L"c:\msys64\mingw64\lib"-L"c:\msys64\opt\gixsql\lib"-L.-lws2_32\-ljapi\-lgixsql\-lstdc++\-lcob\-lmyptr
so is this telling me i need a DLL to use using in the procedure section instead of my
script the way it is above ? I could maybe transform it to output a DLL if that would help.
I got the calling from cobol to C down a little (need to practice more) but am wondering how to go in the reverse direction. So I ask because it doesn't seem to work in Ron's guide.
Is there anyway to make this work that is concise like Ron's guide [the bug fix and change to the guide if that is what is going on]?
There is NO HURRY. I am just trying to get notes in place to handle this when it comes up.
That should work, as long as you don't compile the specific program to an executable (-x may only be used for the single compilation of the main object file and binary).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That should work, as long as you don't compile the specific program to an executable (-x may only be used for the single compilation of the main object file and binary).
< above taken from Ron Norman's guide >
i think i tried this and got errors. it said you cant use using in procedure when expecting an executable.
my compile line would look like this..
so is this telling me i need a DLL to use using in the procedure section instead of my
script the way it is above ? I could maybe transform it to output a DLL if that would help.
this bug is also filed- [bugs:#641]
I got the calling from cobol to C down a little (need to practice more) but am wondering how to go in the reverse direction. So I ask because it doesn't seem to work in Ron's guide.
Is there anyway to make this work that is concise like Ron's guide [the bug fix and change to the guide if that is what is going on]?
There is NO HURRY. I am just trying to get notes in place to handle this when it comes up.
thanks,
jim
Related
Bugs:
#641Last edit: Simon Sobisch 2025-01-03
That should work, as long as you don't compile the specific program to an executable (
-x
may only be used for the single compilation of the main object file and binary).okay very cool.
THANKS :-)
Sent with Proton Mail secure email.
On Friday, January 3rd, 2025 at 1:10 PM, Simon Sobisch sf-mensch@users.sourceforge.net wrote: