This month's Index
Subject: Re: Port to VMS; how to get changes into the main code stream?
Re: Port to VMS; how to get changes into the main code stream?
From: Dave McCaldon <davem_at_intersystems.com>
Date: Thu, 25 Feb 2010 10:30:53 -0500
On Feb 25, 2010, at 9:15 AM, Jose Baars wrote:
> I'm at the moment testing libssh2 on VMS. I have most examples
Great, this is something I'd been looking into, but never gotten to. Are you building libssh2 as a shared library (or whatever it's called on VMS), or linking it into the resulting EXE?
> As make/config tools are not widely available on VMS, I made
I believe GNU make is available on VMS, but it's going to be an extra step to install, so yes, a simple (DCL?) script is probably best.
> I can only test against 1 of the tcp/ip stacks available on VMS, although
I have access to a several VMS systems for testing, although I don't know what TCP stacks they have. I believe most of them are fairly recent versions of OpenVMS which I think has a "standard" TCP stack -- that's probably what you have.
> I still have to look in to what zlib I should use, and when testing
zlib is apparently available for VMS:
curl/libcurl uses it and is also available on VMS:
> Could my changes eventually be included in the main stream,
I'd look at how Windows is supported; there's a win32 subdirectory that contains the project files and some Windows specific header files. If there are specific issues in the common code, then wrap them in an #if defined(__VMS)/#endif block, I guess if it requires more involved code changes, that might need to be abstracted out somehow. I'd suggest creating a vms subdirectory and putting everything in there. One you have all of that, then submit as a git patch.