Issue 26465 - SDK patches required for linux sparc
Summary: SDK patches required for linux sparc
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: porting
Classification: Code
Component: code (show other issues)
Version: current
Hardware: Sun Linux, all
: P3 Trivial (vote)
Target Milestone: AOO Later
Assignee: sparcmoz
QA Contact: issues@porting
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-03-14 22:46 UTC by sparcmoz
Modified: 2006-04-29 09:26 UTC (History)
3 users (show)

See Also:
Issue Type: TASK
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description sparcmoz 2004-03-14 22:46:38 UTC 
Response to: [porting-dev] need to build SDK? (Bernd Eilers)

From: Bernd Eilers <gonzo@bernd-eilers.net>
Date: Thu, 11 Mar 2004 19:34:24 +0100
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Subject: [porting-dev] Re: need to build SDK?


ReHi !

Bernd Eilers wrote:
> 
> Hi there!
> 
> Jim Watson wrote:
> 
>> Does this mean there are parts in module odk that may need platform 
>> specific
>> changes?
> 
> 
> It´s not likely that you would need any platform specific changes in 
> module ODK. If you plan to be using the ODK on a not yet supported 
> platform it´s more likely that you would need to make platform specific 
> changes to the sal and bridges modules on which the ODK module depends 
> on, instead.
> [... stuff deleted ...]

Well sorry but I was a little bit too quick with that answer.
Now I had a  deeper look into the odk module and found that there are a 
few parts that indeed need platform specific changes:

First there will be a script created for the SDK user that set´s up 
environment variables for the SDK user. This is of course platform 
specific as it contains things like the name of the C++ compiler 
executable for example.

For Unix platforms you would need to adapt the file odk/configure.pl and 
add things needed for your unix platform for windows there are .bat files.

Than there is the "OfficeBean" which enables the user to embed a 
OfficeOffice.org java component into his/her java application. This 
depends on platform specific code that is needed to get a "native" 
window handle from the java runtime. This code is in 
odk\source\bean\native\unix and odk\source\bean\native\windows.

Kind Regards,
Bernd Eilers
Comment 1 sparcmoz 2004-03-14 22:47:38 UTC 
affects linux sparc only
Comment 2 sparcmoz 2004-03-14 22:49:20 UTC 
This issue is to track linux sparc work on SDK but as mentioned the patches may
affect unix generally.
Comment 3 sparcmoz 2004-04-18 02:49:07 UTC 
retarget
Comment 4 stx123 2005-01-20 09:45:19 UTC 
Hi Jim, as Martin pointed out on the releases list we are coming
closer to 2.0 Beta.
http://www.openoffice.org/servlets/ReadMsg?list=releases&msgNo=8258

Is your work making progress and would be ready for 2.0
as the target milestone indicates?

Thanks, Stefan
Comment 5 sparcmoz 2005-01-20 10:16:43 UTC 
Hi Stefan, thanks for the reminder. Linux Sparc SDK is retargeted for later.
Comment 6 stx123 2005-01-20 10:24:20 UTC 
Hi, no problem; you might want to have a look at other issues assigned to you.
I really miss the IZ whine mails :-)
Greetings, Stefan
Comment 7 sparcmoz 2006-04-29 09:25:38 UTC 
I have tested several SDK examples on GNU/Linux SPARC and there are no platform
specific issues, only issues now relate to gcj as there is no java on SPARC.
There will be separate issues about gcj so this issue can be closed.
Comment 8 sparcmoz 2006-04-29 09:26:09 UTC 
closed