[ Home | Contents | Search | Next | Previous | Up ]
Date: 12/1/99
Time: 10:28:02 PM
Remote Name: 127.0.0.1
How do I use other than 1 byte alignment compiler oprtion with OWL?
This seems to be a fairly common problem faced by people.
As it turns-out, the Borland OWL libraries, are compiled/bound on a 1 byte boundary,
so any interface to them *must* accept this, and work with it.
The easiest method for doing that is to place the boundary restriction on the entire
project.
Of course, all of the Builder VCL related libraries are on quad-word (4 byte) boundaries,
so if you are interfacing with them, you must use their boundary alignment.
Real Problems(tm) arise when you want to mix OWL and VCL in a project,
and even more so when they are both required in the same source module.
To achieve any sort of success with this, you need to use the #pragma's
to change the alignment based on the interface you are working with...
Or you can rebuild the OWL libraries with quad word aligment.
See the makefile in \source\owl\ for information on how to rebuild OWL
with a different byte alignment.