Method and apparatus for internal versioning of objects using a mapfile

• US 5,805,899 A
• Filed: 07/06/1995
• Issued: 09/08/1998
• Est. Priority Date: 07/06/1995
• Status: Expired due to Fees

• Current Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Evans, Rodrick I., Gingell, Robert A.
• Primary Examiner(s): Voeltz, Emanuel Todd
• Assistant Examiner(s): CORCORAN, PETER JOSEPH
• Application Number:
  US08/499,062
• Time in Patent Office: 1,160 Days
• Field of Search: 395/705, 395/653, 395/701, 395/712, 395/710
• US Class Current: 717/170
• CPC Class Codes: G06F 8/54 Link editing before load time
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

A method and apparatus for providing versioning information for a plurality of software objects. When an object is compiled and linked, at build time, the link-editor creates a version definition section and a version symbol section in the object that specify the global symbols defined in various versions of the object. The object can be a shared object, a relocatable object, or a dynamic executable object. When an application software program is linked with the versioned object, at build time, the linker-editor creates a version dependency section in the resulting dynamic executable object that specifies which version of the object is required for execution of the software application program. At runtime, the runtime-linker determines whether all required versions of the object are present before the program is executed. The invention allows the definition of "weak" versions that do not contain new global symbols. The invention also allows the explicit specification of the version of an object to which the software application program should be linked.

Claims

1. A method for providing versioning information in a software program, comprising the steps performed by a data processing system, of:

providing first object code for a first software program;

providing a mapfile, separate from the object code, specifying a version name associated with a version of the first software program, the mapfile further specifying global symbols that form an interface of the version of the first software program; and

linking the first object code, so that an addition is made to the first object code, in accordance with the mapfile, of information identifying the version name of the first software program, to yield a versioned object, the linking step further including the step of adding information to the first object code, in accordance with the mapfile information, the information identifying the global symbols forming the interface of the version.

2. The method of claim 1, further comprising the steps of:

providing second object code for a second software program; and

linking the second object code to the versioned object, wherein the linking step further includes the steps of;

determining a version of the first software program needed by the second software program, and

adding to the second object code, information specifying the version needed by the second software program, to yield a dynamic executable program.

3. The method of claim 2, further comprising the steps of:

prior to executing the dynamic executable program, determining whether the needed version in the dynamic executable program matches the version identified in the versioned object; and

executing the dynamic executable program, wherein the dynamic executable program calls the needed version of the versioned object.

4. The method of claim 2,

wherein the determining step further includes the step of determining a version of the first software program needed by the second software program, by determining which global symbols are needed by the second software program and determining, by checking the information in the versioned object, which versions the needed global symbols are in.

5. The method of claim 2, wherein the information added to the second object code is a version dependency section.

6. The method of claim 1, wherein the information added to the first object code is a version definition section.

7. The method of claim 1, wherein the information added to the first object code is a version symbol section.

8. The method of claim 1, wherein the versioned object is a relocatable object.

9. The method of claim 1, wherein the versioned object is a dynamic executable object.

10. The method of claim 1, wherein the versioned object is a shared object.

11. An apparatus for providing versioning information in a software program, comprising:

a storage medium holding object code for a first software program;

a storage medium holding a mapfile, separate from the object code, specifying a version name associated with a version of the first software program, the mapfile further specifying global symbols that form an interface of the version of the first software program; and

a linker configured to provide additional information in the first object code, in accordance with the mapfile, the additional information defining the version name of the version of the first software program, to yield a versioned object, the linker further configured to add information to the first object code, in accordance with the mapfile information, the information identifying the global symbols forming the interface of the version.

12. The apparatus of claim 11, further comprising:

a storage medium holding second object code for a second software program; and

a linker configured to link the second object code to the versioned object to yield a dynamic executable program, by adding additional information to the second object code specifying the version needed by the second software program.

13. The apparatus of claim 12, further comprising:

a run-time linker configured to provide execution of the dynamic executable program if the run-time linker determines that the needed version specified in the dynamic executable program matches the version defined in the versioned object.

14. The apparatus of claim 11, wherein the versioned object is a relocatable object.

15. The apparatus of claim 11, wherein the versioned object is a dynamic executable object.

16. The apparatus of claim 11, wherein the versioned object is a shared object.

17. A computer program product, comprising:

a computer usable medium having computer readable code embodied therein for causing a determination that a version of an object required by a dynamic executable program is present during execution of the dynamic executable program, the computer program product comprising;

computer readable program code devices configured to cause a computer to effect provision of first object code for a first software program;

computer readable program code devices configured to cause a computer to effect provision of a mapfile, separate from the object code, specifying a version name associated with a version of the first software program, the mapfile further specifying global symbols that form an interface of the version of the first software program; and

computer readable program code devices configured to cause a computer to effect linking the first object code so that an addition is made to the first object code, in accordance with the mapfile, of information identifying the version name of the version of the first software program, to yield a versioned object, and further configured to add information to the first object code, in accordance with the mapfile information, the information identifying the global symbols forming the interface of the version.

18. The computer program product of claim 17, further comprising:

computer readable program code devices configured to cause a computer to effect provision of second object code for a second software program; and

computer readable program code devices configured to cause a computer to effect linking the second object code to the versioned object, by determining a version of the first software program needed by the second software program, and adding to the second object code, information specifying the version needed by the second software program, to yield a dynamic executable program.

19. The computer program product of claim 18, further comprising:

computer readable program code devices configured to cause a computer to effect a determination of whether the version needed by the dynamic executable program to effect execution of program matches the version defined in the versioned object; and

configured to execute the dynamic executable program, wherein the dynamic executable program calls the needed version of the versioned object.