Skip to content

Additions to Porting.md #6

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
MikeFultonDev merged 2 commits into from
May 25, 2022
Merged

Additions to Porting.md #6

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
06baf66
Additions to Porting.md
jshimoda9323 May 25, 2022
22e682a
Updates to address comments on PR 6
jshimoda9323 May 25, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions docs/Guides/Porting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -63,6 +63,10 @@ In the example above, assume the only installed version of `m4` is `${HOME}/zot/
- `. ./env`
to set up the environment for `m4`. If the `.env` file does not exist, the build will fail.

The `.env` files for each tool can be retrieved by running the `portcrtenv.sh` script that is provided either from the respective tool's repository, or the `utils` repository in the `env/` directory. The `portcrtenv.sh` script can be run manually but it is also driven by the `build.sh` script to generate the `.env` file for tools built into the `prod/` directory (see more on `portcrtenv.sh` below).

To generate the `.env` within `/target/dir` run the script like so: `portcrtenv.sh /target/dir`

### Requirements to use build.sh

For a software package to be built with `build.sh`, it needs to provide the following:
Expand All @@ -84,5 +88,13 @@ accordingly if you prefer. See (https://github.com/ZOSOpenTools/autoconfport/blo
There are several additional environment variables that can be specified to provide finer-grained control of the build process.
For details see: (https://github.com/ZOSOpenTools/utils/blob/main/bin/build.sh).

### Running build.sh

Run `build.sh` from the root directory of the git repo you would like to build. For example, m4:
Copy link
Copy Markdown
Collaborator

@MikeFultonDev MikeFultonDev May 25, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice... example helps

```
cd ${HOME}/zot/dev/m4
. setenv.sh
${HOME}/zot/dev/utils/bin/build.sh
```