Quote:>development platform for SCO 3.2v4.2? I am still waiting for the official
>SCO line, but I have been told two things:
Well, you should probably continue to wait, but I've tinkered with this
Quote:>1. If you don't use any new system calls which don't exist under 4.2,
>applications developed under 5 can run on 4.2. I haven't yet clarified
This is true. There are caveats. First, you can't do things like
generate an elf binary and expect it to run under 3.2v4.2. Second,
if your code automatically figures out what is available and what
isn't (ala GNU autoconf or Larry Wall's 'configure') you'll have to
keep it on a leash.
Quote:>whether on ewould need to copy shared libraries onto the 4.2 system, or
>alternatively, have and use 4.2 libraries on the dev system.
I don't think I've seen the OpenServer 5 development system ever use
the shared libraries. If you're generating COFF, you'll always (?)
get statically linked binaries. This is my experience. There may
be some exception, but I sure haven't seen it.
Quote:>2. The development system on Open Server 5 includes compiler flags for
>targetting development to 3.2v4.2.
Again, there's a little bit of a twist here. The compiler flags
control the runtime behaviour of the libraries and the namespace
provided to the proprocessor (i.e. "-a ods30"). They do not control
the namespace availalbe to the linker. If you're religios about
paying attention to (and turning on) warnings, this is OK.
Quote:>Comments please? I'd dearly love to move our development away from the
>senseless limitations of 3.2v4.2.
You have to think about what you're doing, but it's very doable and
not a lot of work. If you do bozo, it's not like it'll fail in some
wierd way - you get an ENOSYS signal and that's that.
However, I see that we have a FAQ brewing here....