Mechanism for Cross-Building Support Using Dependency Information

• US 20110283268A1
• Filed: 05/17/2010
• Published: 11/17/2011
• Est. Priority Date: 05/17/2010
• Status: Active Grant

• Current Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Original Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Inventors: Salter, Mark O.
• Granted Patent: US 8,612,946 B2
• Time in Patent Office: Days
• US Class Current: 717/140
• CPC Class Codes: G06F 8/433 Dependency analysis; Data or control flow analysis
• CPC Class Codes: G06F 8/61 Installation

Abstract

A mechanism for cross-building support using dependency information is disclosed. A method of the invention includes parsing a source code package received for compilation into a binary source code package for a target machine, the parsing to determine a list of dependency packages needed to compile the source code package, for each dependency package in the list of dependency packages determining a type of the dependency package and associating an architecture of at least one of a build machine compiling the source code package or the target machine with the dependency package based on a determined type of the dependency package, downloading each dependency package in the list of dependency packages in a binary form of the build architecture format, and downloading each dependency package that is associated with the target machine in a binary form of the target architecture format.

Claims

1. A computer-implemented method, comprising:

parsing, by a build machine, a source code package received for compilation into a binary source code package for a target machine, the parsing to determine a list of dependency packages needed to compile the source code package;

for each dependency package in the list of dependency packages;

determining, by the build machine, a type of the dependency package; and

associating, by the build machine, an architecture of at least one of the build machine or the target machine with the dependency package based on a determined type of the dependency package;

downloading, by the build machine, each dependency package in the list of dependency packages in a binary form of the build architecture format; and

downloading, by the build machine, each dependency package that is associated with the target machine in a binary form of the target architecture format.

2. The method of claim 1, wherein a cross-build plug-in of a build utility of the build machine performs the determining and associating for each dependency package.

3. The method of claim 1, wherein the architecture of the build machine and the architecture of the target machine are not the same.

4. The method of claim 3, wherein the architecture of the target machine is for an embedded processor of a special-purpose device.

5. The method of claim 1, wherein determining the type of the dependency package further comprises accessing a package repository communicably coupled to the build machine that stores the dependency packages in order to determine the type of each dependency package.

6. The method of claim 5, wherein accessing the package repository to determine the type further comprising accessing a summary file of the package repository to examine a list of files and description for each dependency package that identifies the type of the dependency package.

7. The method of claim 1, wherein if the type of the dependency package is a library, then associating the dependency package with the target machine architecture and if the type of the dependency package is a utility, then associated the dependency package with the build architecture.

8. The method of claim 1, further comprising:

compiling the source code package into the binary code package for the target machine utilizing the downloaded dependency packages in their binary forms of their associated architecture formats; and

providing the compiled binary code package to the target machine.

9. A build machine, comprising:

a processor;

a memory coupled to the processor; and

a build utility enabled by the processor and the memory and including a cross-build plug-in, the build utility operable to;

parse a source code package received for compilation into a binary source code package for a target machine, the parsing to determine a list of dependency packages needed to compile the source code package;

for each dependency package in the list of dependency packages;

determine a type of the dependency package; and

associate an architecture of at least one of the build machine or the target machine with the dependency package based on a determined type of the dependency package;

download each dependency package in the list of dependency packages in a binary form of the build architecture format; and

download each dependency package that is associated with the target machine in a binary form of the target architecture format.

10. The system of claim 9, wherein the architecture of the build machine and the architecture of the target machine are not the same.

11. The system of claim 10, wherein the architecture of the target machine is for an embedded processor of a special-purpose device.

12. The system of claim 9, wherein determining the type of the dependency package further comprises accessing a package repository communicably coupled to the build machine that stores the dependency packages in order to determine the type of each dependency package.

13. The system of claim 12, wherein accessing the package repository to determine the type further comprising accessing a summary file of the package repository to examine a list of files and description for each dependency package that identifies the type of the dependency package.

14. The system of claim 9, wherein if the type of the dependency package is a library, then associating the dependency package with the target machine architecture and if the type of the dependency package is a utility, then associated the dependency package with the build architecture.

15. The system of claim 9, wherein the build utility further configured to:

compile the source code package into the binary code package for the target machine utilizing the downloaded dependency packages in their binary forms of their associated architecture formats; and

provide the compiled binary code package to the target machine.

16. An article of manufacture comprising a machine-readable storage medium including data that, when accessed by a machine, cause the machine to perform operations comprising:

parsing a source code package received for compilation into a binary source code package for a target machine, the parsing to determine a list of dependency packages needed to compile the source code package;

for each dependency package in the list of dependency packages;

determining a type of the dependency package; and

associating an architecture of at least one of a build machine compiling the source code package or the target machine with the dependency package based on a determined type of the dependency package;

downloading each dependency package in the list of dependency packages in a binary form of the build architecture format; and

downloading each dependency package that is associated with the target machine in a binary form of the target architecture format.

17. The article of manufacture of claim 16, wherein the architecture of the build machine and the architecture of the target machine are not the same.

18. The article of manufacture of claim 16, wherein determining the type of the dependency package further comprises accessing a package repository communicably coupled to the build machine that stores the dependency packages in order to determine the type of each dependency package.

19. The article of manufacture of claim 16, wherein if the type of the dependency package is a library, then associating the dependency package with the target machine architecture and if the type of the dependency package is a utility, then associated the dependency package with the build architecture.

20. The article of manufacture of claim 16, wherein the machine-readable storage medium includes data that, when accessed by a machine, cause the machine to perform further operations comprising:

compiling the source code package into the binary code package for the target machine utilizing the downloaded dependency packages in their binary forms of their associated architecture formats; and

providing the compiled binary code package to the target machine.