GeodeticTransform.asc compilation segfaults on Solaris

[ravenAtSafe]

CS_gxswp always looks at the methodCode after (possibly) swapping the bytes. This is only appropriate when reading.

So on write we end up with a mangled methodCode and therefore garbage transformation params that can cause a segfault (thanks to bad array sizes) when the compiled file is next read (which is done during the compilation).

[baertelchen]

assigning to me; we'll touch that function anyway when implementing RFC 6

[Norm Olsen]

This was corrected at Revision 2486 by adding a parameter to the previous CS_gxswp function which is TRUE is the parent function requesting the swap is a write. To be compatible with the new csIoUtil.cpp module, two additional functions, CS_gxswpRd and CS_gxswpWr were added which simply call the primary CS_gxswp function with the appropriate value for the new parameter.

This developer does not have access to a big endian machine and could not test this change thoroughly. It was tested in a little endian environment and it was verified that this change did not break anything in that environment.