C + + portability and cross-platform development [1]: Compiler

In the Cross-platform development process, many problems are related to the compiler. So let's talk about compiler-related issues first.

★ Compiler Selection

First of all, GCC is a priority to consider support because almost all operating system platforms have GCC available. It's basically a generic compiler. If your code is compiled on a platform of GCC and then gets a B platform to compile with a similar version of GCC, there's no big problem. So GCC is sure to consider support.

Second, consider whether to support local compilers. The local compiler is the compiler of the operating system manufacturer itself. For example, the local compiler relative to Windows is Visual C + +. The local compiler relative to Solaris is Sun's CC. If you are sensitive to performance or want to use advanced features of some local compilers, you may have to consider supporting the local compiler while GCC is supported.

★ Compile Warning

Compilers are friends of programmers, many potential problems (including portability), the compiler can find and give warning, if you usually pay attention to these warning messages, can reduce a lot of trouble. So I strongly recommend that: 1 turn the compiler warning level up; 2 do not easily ignore compiler warning messages.

★ Cross Compiler

Cross-compiler definitions see "Wikipedia". In layman's parlance, it is to compile a binary program running on platform B on platform A. If you're developing an application that runs on Solaris, but you don't have a SPARC machine running Solaris, then the crossover compiler can be useful. In general, GCC is used to make a cross compiler, limited to space, here is not a deep talk. Interested students can see "here".

About the compiler topic, temporarily chat to this, back to talk about "grammar" problem.

Original address: http://program-think.blogspot.com/