Skip to content

Conversation

@BenReed161
Copy link
Collaborator

Added documentation for building the switchtec cli using a different version of OpenSSL that current build system may not be expecting Provide solution for issues encountered with custom openssl versions and document the make system in more detail for users.

Added documentation for building the switchtec cli using a different
version of OpenSSL that current build system may not be expecting
Provide solution for issues encountered with custom openssl versions
and document the make system in more detail for users.
@BenReed161 BenReed161 force-pushed the readme-for-openssl-alt-path branch from f444c10 to cd442ae Compare April 8, 2025 20:57
by the current switchtec-cli build system.
Users have observed the below error (or similar shared library errors) when
using OpenSSL commands after compiling the codebase.
Copy link
Collaborator

Choose a reason for hiding this comment

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

I'm a bit confused by this paragraph. Under what circumstances is this error being emitted? Is compiling a custom version of libssl the solution to whatever caused this?

Does switchtec-user depend on a specific version of libssl and commonly used systems have a version that is too old? What versions of libssl are affected? What operating systems are affected?

object file: No such file or directory
~~~
To build the switchtec libraries to an alternate library path use the following
make flag when building:
Copy link
Collaborator

Choose a reason for hiding this comment

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

Based on above, I was expecting some instructions that will build the project with a custom built OpenSSL library. But these are instructions that install the project, except places only the library outputs in a path of the user's choice. This doesn't seem all that advisable seeing the install command will also install the executables in the usual place but the executable won't be able to find the correct libraries it needs to run.

If the point is to put the libraries in a specific spot after compiling, I'd recommend just running make and then copying the libraries to where you want them. But this doesn't seem so widely applicable that I'd put it in the README. It'd likely just confuse users.

@BenReed161 BenReed161 closed this Apr 23, 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.

2 participants