[openbeosnetteam] Re: R5 compatibility and libnetapi.so

Axel Dörfler wrote:
No, but I have another idea that takes Oliver's problems into account:
Our startup code could know that it's the Haiku startup code - so if you link something for or under Haiku, it can know this, and the networking code could then never use the compatibility layer. If it's the BeOS startup code, it would test if the executable has been linked against libbind.so/libsocket.so, and if that's not the case, it would enable the R5 mode.
The only (additional) disadvantage is that if you'd like to build R5 executables under Haiku, you'll also need the R5 startup code to link against.
How does that sound? Too ugly or just good enough?

This seems very sensible to me. I don't think that anyone wants to go back to R5 - it is getting harder and harder to find hardware that will run on R5; if it weren't for Haiku drivers, I wonder if you could even buy a new box today that would run...

Other related posts: