Skip to content

Preparation for SEAR 0.6.0 #10

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

Open
emmasdb wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Preparation for SEAR 0.6.0 #10

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1abe481
Preparation for SEAR 0.6.0
emmasdb Feb 13, 2026
2734e7f
Included link to cmake
emmasdb Feb 13, 2026
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
6 changes: 3 additions & 3 deletions development/build.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,9 +14,9 @@ This page covers dependencies and the process of building SEAR from source.
SEAR requires several things included with [zOpen](https://zopen.community/#/):

- make (the one IBM provides will cause the process to fail)
- cmake
- OpenSSL from zOpen (necessary because of the certificate support)
- zoslib from zOpen
- [cmake](https://github.com/zopencommunity/cmakeport)
- [OpenSSL from zOpen](https://github.com/zopencommunity/opensslport)
- [zoslib from zOpen](https://github.com/zopencommunity/zoslibport)

This list will expand in the future as more language interfaces get added.

Expand Down
12 changes: 8 additions & 4 deletions development/build_whl.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,13 +12,17 @@ This page covers how to build the Python wheel yourself, rather than getting it
The following software is needed to build:

- z/OS 2.5 or later
- OpenXL C/C++ 2.1 (needed to get clang on z/OS)
- Python 3.12, 3.13, or 3.14
- [IBM OpenXL C/C++ 2.1](https://www.ibm.com/products/xl-cpp-compiler-zos) or later (1.1 won't work)
- [Python](https://www.ibm.com/products/open-enterprise-python-zos) 3.12, 3.13, or 3.14
- setuptools and build packages
- OpenSSL from zOpen
- zoslib from zOpen
- [OpenSSL from zOpen](https://github.com/zopencommunity/opensslport)
- [zoslib from zOpen](https://github.com/zopencommunity/zoslibport)
- git (to clone the repository)

### Environment variables

There are 2 different ways of informing the build process where zoslib and openssl are located. The first is if you have done a full zOpen install, then you can use the ZOPEN_ROOTFS environment variable. If you have installed openssl and zoslib individually, i.e. in your home directory, then you can specify OPENSSL_ROOT and ZOSLIB_ROOT. If ZOPEN_ROOTFS is not specified then both OPENSSL_ROOT and ZOSLIB_ROOT must be set.

## Initiating the build process

First you will need to clone down the source code with git
Expand Down