Issue 6015 - Porting Issues Document is a bit out of date
Summary: Porting Issues Document is a bit out of date
Status: CLOSED FIXED
Alias: None
Product: porting
Classification: Code
Component: www (show other issues)
Version: OOo 1.0.0
Hardware: Mac Mac OS X, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: shaunmcdonald131
QA Contact: issues@porting
URL: http://porting.openoffice.org/mac/mac...
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2002-06-20 19:48 UTC by fa
Modified: 2017-05-20 09:13 UTC (History)
4 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description fa 2002-06-20 19:48:36 UTC
First, all references to MacOS X 10.0.x should be changed to MacOS X 10.1.x.  A 
number of things about technical issues have change, but not too much.  The 
Share Library code was changed between when Patrick(?) wrote this document and 
638C to use the dlcompat library for Darwin instead of CoreFoundation APIs for 
loading shared libraries.  Thus, we no longer have the ".framework" extension, 
and no longer package libraries into a framework structure.

Therefore, the last section, entitled "Special packaging requirements for 
shared libraries" should be changed to something like the following:
-------------------
Most Unix platforms use ".so" as the suffix for shared libraries. However, the 
Mac OS X 10.1.x linker expects ".dylib" as the suffix for shared libraries.

Also, the Java call System.loadLibrary expects ".jnilib" as the suffix for 
shared libraries.

As of the OO638C_MacOSX release tag, the standard build recipes will 
automatically create the matching lib*.jnilib files for each lib*.dylib file 
that is linked. However, developers need to be aware that the source code may 
use a hardcoded ".so" in the shared library name. In such cases, developers 
should modify the code to use ".dylib" in the shared library name for Mac OS X 
10.1.x while preserving ".so" for other platforms.
-------------------
Comment 1 lsuarezpotts 2002-06-28 20:50:18 UTC
Hi
I de-staticized the mac pages; ed can update the relevant ones. If the porting guides are not there, then Armin is the man to update them, not I.
Reassigning to Armin.
louis
Comment 2 ed 2002-06-28 21:12:48 UTC
Yes, the porting issues page is in the mac site.  I think I no 
longer link to it and it's only from the links on the main porting 
front page, however, within the port status area at the bottom.  I'll 
reassign this to myself to update that page.  I guess I should file 
another one to clean up the area at the bottom of the main 
porting page since it doesn't really affect the OS X porting issues 
page.
Comment 3 Unknown 2002-07-01 11:36:46 UTC
Hi, 

since I'm not involved in the Mac port but quite involved in a lot of 
other things, I'd be greatful if somebody who is more an insider could 
take care of that. Thanks, Edward. If you need assistance in 
getting the html files or with cvs, you can come back to me. 

armin

ps: and I change the status to 'started'
Comment 4 terryt 2004-05-23 04:26:28 UTC
I believe Kevin Hendricks is currently cleaning up this document.
Comment 5 shaunmcdonald131 2006-11-11 00:55:53 UTC
There should be a wiki page for this, so can we remove this page?

Will need to find the relevant wiki page and link to it from 
http://porting.openoffice.org/mac/developers/index.html
Comment 6 jjmckenzie 2007-02-05 03:11:36 UTC
@smsm1

What is the status of this issue?

@all:

Removed openstep as cc as he is no longer working on OpenOffice.org issues.
Reassigned to smsm1.

James McKenzie
Comment 7 jjmckenzie 2007-02-05 03:12:25 UTC
Reassigned:  openstep is no longer working on OpenOffice.org issues.

James McKenzie
Comment 8 shaunmcdonald131 2007-02-05 09:58:56 UTC
I believe this page is completely out of date, and should just be removed. As I
don't work enough at code level it is difficult to tell.
ericb: Any idea? Should I just remove it?
Comment 9 rvojta 2009-01-26 07:47:19 UTC
I think we can close this issue as FIXED. The page is not out of date now, it
points to Wiki pages, etc. If you want to modify this, please, open new issue.