Ambuild - Revision history

BAILOPAN at 17:13, 22 September 2021

2021-09-22T17:13:44Z

BAILOPAN at 04:05, 25 August 2020

2020-08-25T04:05:18Z

BAILOPAN: /* Tup */

2020-08-25T04:04:49Z

‎Tup

BAILOPAN: /* Make, Accuracy */

2020-08-25T04:02:22Z

‎Make, Accuracy

BAILOPAN at 03:50, 25 August 2020

2020-08-25T03:50:58Z

BAILOPAN: /* Requirements */

2020-08-23T07:54:31Z

‎Requirements

BAILOPAN: /* Requirements */

2020-08-23T07:53:52Z

‎Requirements

BAILOPAN: /* Installation */

2020-08-23T07:52:15Z

‎Installation

BAILOPAN: /* Requirements */

2020-08-23T07:50:57Z

‎Requirements

BAILOPAN at 07:29, 16 August 2020

2020-08-16T07:29:16Z

@@ Line 6: / Line 6: @@
 Keep in mind, AMBuild is neither widely used nor has it been used on a wide variety of systems. AlliedModders has used it successfully for small to medium-sized C++ projects on Linux, Mac, and Windows. Our largest project, SourceMod, has 700 C++ files and over 200,000 lines of code. We're happy to receive feedback on GitHub if you use it in your own projects.
-AMBuild 2.2 is the latest release. It supports cross-compiling, multi-architecture builds, and precompiled headers.
+AMBuild 2.2.1 is the latest release. It supports cross-compiling, multi-architecture builds, and precompiled headers.
 =Motivation=
@@ Line 18: / Line 18: @@
 =Requirements=
-Python 2.7 or higher is required. If using Python 3, then 3.3 or higher is required.
+Python 3.3 or higher is required.
 Additionally, pip and setuptools (both Python components) are also required. If your distribution or Python installation does not provide for these, see [https://pip.pypa.io/en/stable/installing/ Installing Pip] for manual instructions.

@@ Line 4: / Line 4: @@
 *'''Flexibility'''. Build scripts are written in Python, so they're very easy to write and provide full programmatic control.
-Keep in mind, AMBuild is neither widely used nor has it been used on a wide variety of systems. AlliedModders has used it successfully for small to medium-sized C++ projects on Linux, Mac, and Windows. Our largest project, SourceMod, has 700 C++ files and over 200,000 lines of code. We're happy to receive feedback (see the bottom of this page) if you use it in your own projects.
+Keep in mind, AMBuild is neither widely used nor has it been used on a wide variety of systems. AlliedModders has used it successfully for small to medium-sized C++ projects on Linux, Mac, and Windows. Our largest project, SourceMod, has 700 C++ files and over 200,000 lines of code. We're happy to receive feedback on GitHub if you use it in your own projects.
 AMBuild 2.2 is the latest release. It supports cross-compiling, multi-architecture builds, and precompiled headers.

← Older revision		Revision as of 04:04, 25 August 2020
Line 150:		Line 150:

	In AMBuild, leaving stale files behind is an error, since they would not be produced by a fresh build.		In AMBuild, leaving stale files behind is an error, since they would not be produced by a fresh build.
−
−	~~==Tup==~~
−	AMBuild is designed to be, essentially, a miniature clone of Tup written entirely in Python. In particular it closely follows concepts in [http://gittup.org/tup/build_system_rules_and_algorithms.pdf the Tup whitepaper]. However there are a few differences that may make one more desirable over the other:
−	* Tup has been around longer than AMBuild 2, and has been more thoroughly tested.
−	* Tup uses complex file system features to optimize updates. Algorithms that are O(n) in AMBuild tend to be O(1) in Tup.
−	* AMBuild only requires a default Python installation to work. Tup, due to being written in C and using very platform specific file system features, may not be as accessible.
−	* Tup has more features for speeding up very large projects. It can do minimal reparsing and it can reduce the number of links in large graphs.
−	* AMBuild is designed to be a front-end in addition to a back-end. It has a simple API and script syntax, and is designed to support multiple output formats. For example, it could conceivably generate Visual Studio or XCode project files.
−
−	~~Since AMBuild is also a frontend, AMBuild may one day eliminate its backend in favor of emitting Tupfiles instead.~~
−
−	AMBuild's IPC implementation is very low-level, and it has not yet been ported beyond Windows, Mac/BSD, or Linux. However it's not difficult to port to Unix-like systems, and if needed a generic (albeit suboptimal) cross-platform implementation could be provided.

@@ Line 147: / Line 147: @@
 AMBuild mitigates these problems by intelligently updating the dependency graph. If a reparse of the build scripts produces identical nodes, it will not consider those nodes as stale.
-Furthermore, when deleting rules, Make will leave their outputs behind. The author is not aware of an easy way to solve this. Leaving old outputs behind is undesirable for a number of reasons. Stale outputs might fool a user or developer tool into thinking the build has succeeded, when in fact it has failed. Stale outputs might be loaded accidentally, i.e. <tt>LD_LIBRARY_PATH</tt> picking up a library that should not exist. Tests that developers forgot to update might pass locally because of a stale output.
+Furthermore, when deleting rules, Make will leave their outputs behind. There is not an easy way to solve this. Leaving old outputs behind is undesirable for a number of reasons. Stale outputs might fool a user or developer tool into thinking the build has succeeded, when in fact it has failed. Stale outputs might be loaded accidentally, i.e. <tt>LD_LIBRARY_PATH</tt> picking up a library that should not exist. Tests that developers forgot to update might pass locally because of a stale output.
 In AMBuild, leaving stale files behind is an error, since they would not be produced by a fresh build.

← Older revision		Revision as of 03:50, 25 August 2020
Line 5:		Line 5:

	Keep in mind, AMBuild is neither widely used nor has it been used on a wide variety of systems. AlliedModders has used it successfully for small to medium-sized C++ projects on Linux, Mac, and Windows. Our largest project, SourceMod, has 700 C++ files and over 200,000 lines of code. We're happy to receive feedback (see the bottom of this page) if you use it in your own projects.		Keep in mind, AMBuild is neither widely used nor has it been used on a wide variety of systems. AlliedModders has used it successfully for small to medium-sized C++ projects on Linux, Mac, and Windows. Our largest project, SourceMod, has 700 C++ files and over 200,000 lines of code. We're happy to receive feedback (see the bottom of this page) if you use it in your own projects.
		+
		+	AMBuild 2.2 is the latest release. It supports cross-compiling, multi-architecture builds, and precompiled headers.

	=Motivation=		=Motivation=

@@ Line 18: / Line 18: @@
 Python 2.7 or higher is required. If using Python 3, then 3.3 or higher is required.
-PIP and Setuptools are also required, these two packages are technically optional in the Python universe and '''''MAY''''' require manual installation. Some Linux (example: Ubuntu/Debian) platforms provide packages to install pip and setuptools while the Windows Python installer bundles a copy of PIP & Setuptools, otherwise, the generic way is via [https://bootstrap.pypa.io/get-pip.py get-pip.py] with no arguments.
+Two Python components, pip and setuptools, are also required. If your distribution does not provide packages for these, see [https://pip.pypa.io/en/stable/installing/ Installing Pip] for manual instructions.
 AMBuild has been tested to work on the following platforms. Although builds of Python for specific architectures were tested, we expect that other architectures will work as well.

@@ Line 40: / Line 40: @@
 </pre>
-Note: Administrator privileges are required to install AMBuild for '''''ALL USERS''''', otherwise, pip will install AMBuild at the user level.
+Note: By default, pip will perform per-user installations. To install globally for all users, you will need to use "sudo" (or run as Administrator on Windows).
 =Tutorial=

@@ Line 21: / Line 21: @@
 AMBuild has been tested to work on the following platforms. Although builds of Python for specific architectures were tested, we expect that other architectures will work as well.
-* Windows 7+ (x86, x86_64)
+* Windows 7+ with x86, x86_64, arm, or arm64 targets.
-* Linux (x86, x86_64, arm)
+* Linux with clang and GCC.
-* OS X (10.9+, x86 and x86_64)
+* OS X 10.9+ with x86 and x86_64 targets.
 It has also been tested to work with the following compilers: