Author Topic: Compiling PM app on 2016.  (Read 36481 times)

xynixme

  • Guest
Re: Compiling PM app on 2016.
« Reply #45 on: May 29, 2017, 10:02:10 am »
OpenWatcom.org, the only existing cross compiler for OS/2

I'm pretty sure that, for example, at least one of the Pascal environments, Virtual Pascal, is capable of producing code for more than one OS. FWIW.

IBM VAC++ 3.08 FixPaks: FTP-server service.software.ibm, com, directory /ps/products/visualagecpp/fixes/v30os2/english-us/fixpak8

ak120

  • Guest
Re: Compiling PM app on 2016.
« Reply #46 on: May 29, 2017, 12:47:17 pm »
There's OpenWatcom, OpenWatcom.org, the only existing cross compiler for OS/2 and of course GCC, yum install gcc.
OpenWatcom supports different host OS and some more target OS in one package. For older OS/2 32-bit releases version 1.8 of OpenWatcom C/C++ should be used. Support for other target architectures is almost not existing, only an assembler for Alpha AXP and PowerPC. On the other hand it includes enough libraries to produce simple PM applications.

IBM C compilers are cross-platform as defined in SAA CPI C Level 2. With later products that introduced new C and C++ features it becomes more complicated. But projects based on IBM's class library could be exchanged between VisualAge C++ 3.0 for OS/2 and VisualAge C++ 3.5 for Windows. IBM C/C++ Compilers V3.6 were available for AIX, OS/2 and Windows NT. For compiling 16-bit object code IBM C/2 (or MS C 6.0) is still needed additionally.


Dariusz Piatkowski

  • Hero Member
  • *****
  • Posts: 1317
  • Karma: +26/-0
    • View Profile
Re: Compiling PM app on 2016.
« Reply #47 on: May 29, 2017, 02:23:33 pm »
Hi Rick,

...I had some difficulty installing Visual Age C++ because I had to reboot after various stages.  I haven't done that in an OS for a while and it threw me for a loop. :-)

Once I got it installed I was stunned.  Visual Age C++ is amazing considering its age...

Which version of VAC did you install?

I am asking b/c I have the fully blown 4.0 here (with various fixpacks) and as you said, even though the product is aged now it is still extremely impressive. Considering that it was always resource hungry, now with the faster machines and better hardware capability it really zips along quite nice.

Part of that install, in my case, was the option to select the standard C/C++, which I did, thus installing the 3.6.5 release (or maybe it was a separate install altogether??? lol, it's been a while...).

What I have always wondered about is the choice between the two? Which one is best suited for what types of apps?

RickCHodgin

  • Guest
Re: Compiling PM app on 2016.
« Reply #48 on: May 29, 2017, 04:50:07 pm »
Hi Rick,

...I had some difficulty installing Visual Age C++ because I had to reboot after various stages.  I haven't done that in an OS for a while and it threw me for a loop. :-)

Once I got it installed I was stunned.  Visual Age C++ is amazing considering its age...

Which version of VAC did you install?

I am asking b/c I have the fully blown 4.0 here (with various fixpacks) and as you said, even though the product is aged now it is still extremely impressive. Considering that it was always resource hungry, now with the faster machines and better hardware capability it really zips along quite nice.

Part of that install, in my case, was the option to select the standard C/C++, which I did, thus installing the 3.6.5 release (or maybe it was a separate install altogether??? lol, it's been a while...).

What I have always wondered about is the choice between the two? Which one is best suited for what types of apps?

It was Visual Age for C++ Version 4.0.  I had not had anything previously installed on this machine.  It was a brand new Arca OS installation, and I was going through the install.exe on the CD image I created.

What was confusing me was I had to reboot after a few stages.  I also wonder whether Navigator 4.0 was required since I have newer programs that could support HTML frames.

I am flatly amazed by Visual Age 4.  And I must say, I am also continually impressed by every piece of software I come across by IBM.  I worked at Toyota for three years and when I was given my orientation I was asking them why they used IBM's DB2?  They said it was simple, they deal with 1000s of transactions per second on their manufacturing lines, and they setup the database and did a test.  They had DB2, SQL Server, and several others.  While it was in the middle of the simulation testing environment, the technicians went behind the machines and pulled out the power cord.  They then booted up to see how much damage there was.  The test software had been written to log which writes were identified as "successful" on the server, as was given by a valid return code to the issuing machine used in the test.

IBM's DB2 was the only one that came back up with a 100% retention of data, such that everything that was deemed to be written successful from the application's point of view, was actually in the database with a valid timestamp, etc.

They have used IBM DB2 since that time, and have never had a single problem.  In fact, when I was there, it was the most tolerant part of our entire networking infrastructure.

I give full props and credit to IBM.  Everything I've ever used from them has been grade A++.  From my 1984 IBM PCjr (I got one after the chiclet keyboard, so my experience was a more normal keyboard), to IBM Writing Assistant that came in cartridge form with that computer, through every other piece of software I've used through Warp 4 back in the mid-90s.  And I should add that I mean that in the sense that here in 2017 still looking at the capabilities of that software, its design, etc ... still amazing.

It's an amazing legacy for a company.  And I only wish IBM would've continued development on OS/2 and its follow-ons.  We would all be using either OS/2 today (or some derivative), or we would've all had a much better, much more capable Windows.

In either case, IBM's contribution to our general software world was cut off too soon.  They should've persisted and shown the world what a company bent on doing things correctly in design and implementation was capable of.  They would've notably changed the world and our 2000s would be different because of it.

Thank you,
Rick C. Hodgin
« Last Edit: May 30, 2017, 12:14:35 pm by Rick C. Hodgin »

ak120

  • Guest
Re: Compiling PM app on 2016.
« Reply #49 on: May 29, 2017, 06:26:28 pm »
I am asking b/c I have the fully blown 4.0 here (with various fixpacks) and as you said, even though the product is aged now it is still extremely impressive. Considering that it was always resource hungry, now with the faster machines and better hardware capability it really zips along quite nice.
I don't know what you mean by "various". There's only Fixpak 1 for OS/2:
ftp://public.dhe.ibm.com/ps/products/visualagecpp/fixes/v40os2/english-us/fixpak1/

http://www-01.ibm.com/support/docview.wss?uid=swg24000729

Quote
Part of that install, in my case, was the option to select the standard C/C++, which I did, thus installing the 3.6.5 release (or maybe it was a separate install altogether??? lol, it's been a while...).
It's an extra CD-ROM in the package and needs to be installed separately. Also a different fixpak:
ftp://public.dhe.ibm.com/ps/products/visualagecpp/fixes/v365os2/english-us/fixpak2/
... and some more fixes:
ftp://public.dhe.ibm.com/ps/products/warpzilla/vacpp365fix.zip

ftp://public.dhe.ibm.com/ps/products/warpzilla/vacppoptfix.zip

Quote
What I have always wondered about is the choice between the two? Which one is best suited for what types of apps?
V 3.6 is better suited for projects from VAC 3.0 environment or cross platform projects. Of course there is also a migration feature in the V4.0 workframe. Both support the same level of IOC (IBM Open Class).