[NTLUG:Discuss] Need some inputs on porting.

[Vaidya, Harshal (Cognizant)]

Hi, 

We are providing a solution to the following requirement:

The current scenario is like this.

 Its a complex application with a lot of GUI and business logic tuned
towards banking. 
 Its Deployed on Solaris 2.8.
 Its completely written in C++.
 It uses third party tools like Roguewave tools for XML processing and
GUI.
 Connects to a standard Oracle database.
 The application has roughly about one million lines of code.

The application is totally at application layer. What I mean by that is,
it does not involve any system level stuff like device drivers and
things alike. It's a complex application built towards providing a
business solution for the banking practise.

The solution needs the following things to be mandatory.

We need to make the entire code compatible to gcc 3.3.

With this I have several questions in mind. Is there anything special
with 3.3? According to me if the entire application is recompiled with
gcc 3.3 over Linux and Solaris our work should be done. All we will need
to do is see whether the compilation on both Solaris and Linux goes
smoothly. Any comments?

Secondly the code now needs to be portable between Solaris 2.8 and
RedHat Enterprise Linux Advanced Server.

I think recompilation over GCC should do it. Comments?

Thirdly, we need to make the code 32 and 64 bit compatible!! The
deployment platforms are Linux and Solaris both.

Now, this is the killer one!!!

How do you think the problem of 32 to 64 bit compatibility should be
addressed?
Of course I am reading up on this over the net. But I just thought that
people who have been through this already would have a lot of things to
talk about. And that's exactly what I want to know.

Moreover what pitfalls should we be aware of in terms of porting from
Solaris and Linux?

If you have anything else to say about this. It is most welcome.

Thanks,
Harshal Vaidya.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: InterScan_Disclaimer.txt
Url: http://ntlug.org/pipermail/discuss/attachments/20030930/761e9533/InterScan_Disclaimer.txt