Porting your application to multiple distributions is a task that conjures up images of large engineering and support costs, which detract from the real value of the Linux platform. It is the primary goal of the LDN to provide the skills and the tools to vastly reduce those costs by emphasizing portability techniques for cross-distro application development, or full LSB certification.
One of the best ways of enhancing portability is to use the LSB Application Checker to test your application and see how far along your are on the path to LSB compliance. In particular, you can visit the LSB Certification page of the Test Report to see which libraries and interfaces your application is using that prevent LSB compliance. Once these components are identified, there are four recommended strategies for developers to take to work towards LSB compliance. Even if such compliance is not your goal, the very process of moving towards the LSB ensures you will have a much more portable application when all is said and done.
Remove the non-LSB dependencies with these strategies in mind:
> Note: This is a good idea if you are explicitly targeting cross-distro portability, as
openssl has different ABI's across different distributions and different distribution versions)
> Caution: Care should be taken when statically linking libraries as some software licenses, such as the GPL, treat statically linked libraries are part of the main application body, and thus extend the license conditions to the main application.
There are, of course, other more general strategies to use when porting your application:
sizeofwhen getting sizes of objects. This is especially true when going from 32-bit to 64-bit
charis signed or unsigned
floatis the same size as
double<br /><br type=“_moz” />
#ifdef<br /><br type=“_moz” />
-Wstrict-prototypesoption in compiling