Skip to content

Conversation

tsh-hashimoto
Copy link
Contributor

Until now, there was a problem of conflicting commands when trying to use Open COBOL ESQL and Open COBOL ESQL 4J in the same environment.
(renaming /usr/bin/ocesql, or ./configure option can avoid this problem, but it is a bit tedious)

So I tried to change Open COBOL ESQL 4J command from ocesql to ocesql4j.

Here are the main changes.
For Linux:

  • ocesql/Makefile.am: change bin_PROGRAMS (ocesql -> ocesql4j).
  • tests/: some updates.

For Windows:

  • win/ocesql4j.vcxproj: change ProjectName.
  • win/ocesql4j.sln: rename from ocesql.sln.
  • win/install.ps1: ocesql.exe -> ocesql4j.exe.
  • windows-build.yml: some updates.

@tsh-hashimoto tsh-hashimoto force-pushed the change-command branch 2 times, most recently from 8a8475d to 78e832c Compare November 25, 2024 13:16
@tsh-hashimoto
Copy link
Contributor Author

I have just changed the name of the executable that is to be generated (bin_PROGRAMS), the source code in ocesql/ has not changed the file names or variables to ocesql4j.
(Perhaps this may need to be changed as well......)

@tsh-hashimoto
Copy link
Contributor Author

now pending...

yutaro-sakamoto added a commit to yutaro-sakamoto/Open-COBOL-ESQL-4j that referenced this pull request May 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant