Projection of build and design-time inputs and outputs between different build environments
Abstract
Methods, systems, apparatuses, and computer program products are described that enable local builds to be substantially equivalent with remote builds. In embodiments, local build and design-time inputs and/or outputs of a local build environment hosted on a local computing device are projected to remote build and design-time inputs and/or outputs of a remote build environment hosted on a remote computing device. In further embodiments, remote build and design-time inputs and/or outputs of the remote build environment are projected to local build and design time inputs and/or outputs of the local build environment. In still further embodiments, first build and design-time inputs and/or outputs of a first build environment hosted on a computing device are projected to second build and design-time inputs and/or outputs of a second build environment hosted on the same computing device.
Claims
exact text as granted — not AI-modifiedWhat is claimed is:
1 . A first computing device, comprising:
at least one processor circuit; and at least one memory that stores program code configured to be executed by the at least one processor circuit, the program code comprising: a build synchronizer configured to project a first build or design-time output generated by a first build environment hosted on the first computing device to a second build or design-time output of a second build environment hosted on a second computing device by automatically generating the second build or design-time output that has a different form and/or a different content than the first build or design-time output, the first build environment being different than the second build environment, the first build or design-time output comprising at least one or more binaries, the build synchronizer being further configured to project the one or more binaries by changing at least one of a format and/or content of an executable file, a name of an executable file, or a manner in which an executable file is digitally signed.
2 . The first computing device of claim 1 , wherein the first build environment is different than the second build environment in at least that the first build environment is executed on a different operating system than the second build environment.
3 . The first computing device of claim 1 , wherein the first build environment is different than the second build environment in at least that the first build environment and the second build environment are executed on different versions of the same operating system.
4 . The first computing device of claim 1 , wherein the build synchronizer is further configured to determine that the second build or design-time output has been modified and to update the first build or design-time output based on the modification to the second build or design-time output.
5 . The first computing device of claim 1 , wherein the build synchronizer is further configured to determine that the first build or design-time output has been modified and to update the second build or design-time output based on the modification to the first build or design-time output.
6 . The first computing device of claim 1 , wherein the first build or design-time output further comprises a log file.
7 . A method for synchronizing a computer-implemented first build environment with a computer-implemented second build environment, the method comprising:
identifying a first build or design-time output of the first build environment, the first build or design-time output comprising at least one or more binaries; and projecting the first build or design-time output to a second build or design-time output of the second build environment by automatically generating the second build or design-time output that has a different form and/or different content than the first build or design-time output, the first build environment being different than the second build environment, the projecting the first build or design-time output comprises changing at least one of a format and/or content of an executable file, a name of an executable file, or a manner in which an executable file is digitally signed.
8 . The method of claim 7 , wherein the first build environment is different than the second build environment in at least that the first build environment is executed on a different operating system than the second build environment.
9 . The method of claim 7 , wherein the first build environment is different than the second build environment in at least that the first build environment and the second build environment are executed on different versions of the same operating system.
10 . The method of claim 7 , wherein the first build environment is hosted on a different computing device than the second build environment.
11 . The method of claim 7 , wherein the first build environment is hosted on the same computing device as the second build environment.
12 . The method of claim 7 , further comprising:
determining that the first build or design-time output was modified; and updating the second build or design-time output based on the modification to the first build or design-time output.
13 . The method of claim 7 , further comprising:
determining that the second build or design-time output was modified; and updating the first build or design-time output based on the modification to the second build or design-time output.
14 . The method of claim 7 , wherein the first build or design-time output further comprises a log file.
15 . A computer program product comprising a computer-readable storage device having computer program logic recorded thereon that when executed by a processor-based computer system causes the process-based system to perform a method, the method comprising:
identifying a first build or design-time output of the first build environment, the first build or design-time output comprising at least one or more binaries; and projecting the first build or design-time output to a second build or design-time output of the second build environment by automatically generating the second build or design-time output that has a different form and/or different content than the first build or design-time output, the first build environment being different than the second build environment, the projecting the first build or design-time output comprises changing at least one of a format and/or content of an executable file, a name of an executable file, or a manner in which an executable file is digitally signed.
16 . The computer program product of claim 15 , wherein the first build environment is different than the second build environment in at least that the first build environment is executed on a different operating system than the second build environment.
17 . The computer program product of claim 15 , wherein the first build environment is different than the second build environment in at least that the first build environment and the second build environment are executed on different versions of the same operating system.
18 . The computer program product of claim 15 , further comprising:
determining that the first build or design-time output was modified; and updating the second build or design-time output based on the modification to the first build or design-time output.
19 . The computer program product of claim 15 , further comprising:
determining that the second build or design-time output was modified; and updating the first build or design-time output based on the modification to the second build or design-time output.
20 . The computer program product of claim 15 , wherein the first build or design-time output further comprises a log file.Join the waitlist — get patent alerts
Track US2017286064A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.