[Info-vax] Making Open Source Tools Work for VMS

[Arne Vajhøj]

On 11/22/2021 6:28 AM, Phillip Helbig (undress to reply) wrote:
> In article <j018pcF1dl2U1 at mid.individual.net>, Jon Schneider
> <jon at jschneider.tenreversed> writes:
>> I would really like to see a developers' guide Wiki for OpenVMS for
>> those of us, and I think there are quite a few, who have been writing
>> software for decades yet don't have a feel for doing so under (Open)VMS.
> 
> It would be nice if there were some sort of standard BUILD.COM which
> would do everything (perhaps with parameters to determine whether one
> wants to use supplied .EXE, link supplied .OBJ, or compile from supplied
> sources).  When finished, it can print out the required symbol
> definition (which one would presumably place with others), command to
> add the HELP to some library (ideally one would have a separate HELP
> library for such third-party products), and so on.

Yes.

I have been thinking about that - it would be very nice with a standard
for that.

My thoughts are:

foobar-1_2_3-src.zip with source

foobar-1_2_3-bin-vax.zip, foobar-1_2_3-bin-axp.zip, 
foobar-1_2_3-bin-i64.zip and foobar-1_2_3-bin-x64.zip with obj and exe

all zip contains path foobar-1_2_3/bla/bla

build.com builds from source

link.com link obj (are called from build.com)

setup_logicals.com that define logicals and has a p1 so one can specify 
"/system" and a p2 "yes" to specify that hlp$library_n to be defined

setup_symbols.com that define symbols and define verbs

Arne