Cross-building support using dependency information

• US 8,612,946 B2
• Filed: 05/17/2010
• Issued: 12/17/2013
• 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.
• Primary Examiner(s): Dao, Thuy
• Assistant Examiner(s): Nguyen, Mongbao
• Application Number:
  US12/781,615
• Publication Number:
  US 20110283268A1
• Time in Patent Office: 1,310 Days
• Field of Search: None
• 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 method, comprising:

parsing, by a processing device of a build machine, a source code package received for compilation into a binary source code package for installation by a target machine that is separate from the build machine, the parsing to determine a list of dependency packages utilized to compile the source code package;

for each dependency package in the list of dependency packages;

determining, by the processing device, a type of the dependency package, wherein the type comprises one of a package used for a build process of the source code package or a package used by the target machine; and

associating, by the processing device, the dependency package with an architecture of one of the build machine or the target machine based on the determined type of the dependency package, wherein if the type of the dependency package is a library, then the dependency package is associated with the target machine architecture and if the type of the dependency package is a utility, then the dependency package is associated with the build architecture;

downloading, by the processing device, all dependency packages in a binary form of the build architecture format;

downloading, by the processing device, each dependency package that is associated with the architecture of the target machine in a binary form of the target architecture format; and

compiling the source code package into the binary code package for the target machine utilizing the downloaded dependency packages in the binary form of their associated 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, further comprising:

providing the compiled binary code package to the target machine.

8. A build machine, comprising:

a processing device;

a memory coupled to the processing device; and

a build utility executable from the memory by the processing device, the build utility comprising a cross-build plug-in and the build utility 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, wherein the type comprises one of a package used for a build process of the source code package or a package used by the target machine; and

associate the dependency package with an architecture of one of the build machine or the target machine based on the determined type of the dependency package, wherein if the type of the dependency package is a library, then the dependency package is associated with the target machine architecture and if the type of the dependency package is a utility, then the dependency package is associated with the build architecture;

download all dependency packages in a binary form of the build architecture format;

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

compile the source code package into the binary code package for the target machine utilizing the downloaded dependency packages in the binary form of their associated architecture format.

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

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

11. The system of claim 8, 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.

12. The system of claim 11, 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.

13. The system of claim 8, wherein the build utility further to:

provide the compiled binary code package to the target machine.

18. The system of claim 8, wherein the cross-build plug-in of the build utility to perform the determining and the associating for each dependency package.

14. A non-transitory machine-readable storage medium including data that, when accessed by a processing device, cause the processing device to perform operations comprising:

parsing, by the processing device, 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 processing device, a type of the dependency package, wherein the type comprises one of a package used for a build process of the source code package or a package used by the target machine; and

associating, by the processing device, the dependency package with an architecture of one of the build machine or the target machine based on the determined type of the dependency package, wherein if the type of the dependency package is a library, then the dependency package is associated with the target machine architecture and if the type of the dependency package is a utility, then the dependency package is associated with the build architecture;

downloading all dependency packages in a binary form of the build architecture format;

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

compiling the source code package into the binary code package for the target machine utilizing the downloaded dependency packages in the binary form of their associated architecture format.

15. The non-transitory machine-readable storage medium of claim 14, wherein the architecture of the build machine and the architecture of the target machine are not the same.

16. The non-transitory machine-readable storage medium of claim 14, 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.

17. The non-transitory machine-readable storage medium of claim 14, wherein the machine-readable storage medium includes data that, when accessed by a machine, cause the machine to perform further operations comprising:

providing the compiled binary code package to the target machine.

19. The non-transitory machine-readable storage medium of claim 14, wherein the architecture of the target machine is for an embedded processor of a special-purpose device.

20. The non-transitory machine-readable storage medium of claim 16, 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.