boost/build
2
0
Fork 0
mirror of https://github.com/boostorg/build.git synced 2026-02-13 12:22:17 +00:00
Code Issues Projects Releases Wiki Activity
4,866 Commits 2 Branches 134 Tags
94de4748d96e770490cd9f49bb1b0b0e44984250
Commit Graph

4866 Commits

This Branch
This Branch
All Branches
Author SHA1 Message Date
Jurko Gospodnetić
8f72b65456 Boost Build code cleanup - minor stylistic changes. 
[SVN r79622]
 2012-07-20 14:42:18 +00:00
Jurko Gospodnetić
29d94131ee Fixed minor Boost Build error reporting bugs caused by module rules not being directly available using their full names when imported from inside a class rule - an error about rule errors.error or errors.user-error not being defined was getting reported instead of the desired error. This is due to the fact that rule name resolution does not look in the current module in that case but uses the class module instead. 
[SVN r79621]
 2012-07-20 14:39:50 +00:00
Jurko Gospodnetić
89f740660f Boost Jam/Build code cleanup - minor stylistic changes. 
[SVN r79620]
 2012-07-20 14:20:55 +00:00
Jurko Gospodnetić
bae5e920ac Boost Jam code cleanup - removed an old, untested and up to recently definitely non-compiling 'old Borland compiler' code branch in the filent.c module. The compilers in question themselves are Borlands free compiler tools predating the more modern and more standard compliant free 'Visual Studio Express' toolchain so there should be no need for anyone to depend on them any more. 
[SVN r79618]
 2012-07-20 10:57:31 +00:00
Jurko Gospodnetić
ae0e14f947 Fixed a Boost Build bug causing scanner targets to be rebuilt every time if their base target has already been marked as including another target with a newer timestamp. For example, this occurred every time a single action generated both the scanned and the included target and did so slowly enough that the included target got a newer timestamp. Fix originally prepared by Steven Watanabe. 
[SVN r79601]
 2012-07-19 14:32:31 +00:00
Jurko Gospodnetić
a80848695b Corrected the internal Boost Build library_order.py unit test - updated its test run parameter passing to use lists of strings instead of simple strings (was causing assertion failures with the latest internal Boost Build testing framework implementation), minor stylistic changes. 
[SVN r79600]
 2012-07-19 12:30:48 +00:00
Jurko Gospodnetić
0e4d14bfe6 Added a new internal Boost Build test illustrating a bug in the current Boost Build/Jam implementation and causing targets to be rebuilt when not necessary in some cases. 
[SVN r79599]
 2012-07-19 11:53:30 +00:00
Jurko Gospodnetić
cc5e96ab49 Boost Build cleanup - minor stylistic change. 
[SVN r79598]
 2012-07-19 11:37:03 +00:00
Jurko Gospodnetić
e85732818d Corrected internal Boost Build testing framework bug causing it to report detected filesystem changes from a previous instead of the failed test run when the failure was caused by an unexpected exit code, unexpected stderr content, unexpected stdout content or exceeded maximal test duration. 
[SVN r79597]
 2012-07-19 10:16:41 +00:00
Jurko Gospodnetić
e0f7059b26 Removed an unused variable from one of the internal Boost Build tests. 
[SVN r79596]
 2012-07-19 04:39:42 +00:00
Jurko Gospodnetić
3c935afa5f Cleaned up Boost Build's internal 'parallel multi-file actions' tests a bit - removed some dead code and updated description comments. 
[SVN r79595]
 2012-07-19 04:11:50 +00:00
Jurko Gospodnetić
2f64a35846 Boost Build code cleanup - minor stylistic changes (trimmed trailing spaces, corrected a typo in the main module comment). 
[SVN r79594]
 2012-07-19 03:47:31 +00:00
Jurko Gospodnetić
4e711ebd44 Minor stylistic change. 
[SVN r79593]
 2012-07-19 02:58:55 +00:00
Jurko Gospodnetić
681b6609af Boost Jam code cleanup - minor stylistic changes (added missing spaces around some parameters inside brackets in C code). 
[SVN r79587]
 2012-07-18 15:06:44 +00:00
Jurko Gospodnetić
cbb48b5d01 Updated Boost Jam implementation comment related to it adding internal fake INCLUDES relationships between targets built by a single action in order to make sure none of them may get used until their action had successfully completed its work. 
[SVN r79586]
 2012-07-18 14:50:53 +00:00
Jurko Gospodnetić
35883dacc0 Boost Build build bug corrected when compiling using old Borland compilers. This has been in for a long time and has been noticed only as part of a quick code review. It could be there is no need to support this 'old Borland compilers' code branch. 
[SVN r79585]
 2012-07-18 14:27:22 +00:00
Jurko Gospodnetić
58beabb9dc Boost Jam code cleanup - moved code for creating new internal include targets into a single location (rules.c module) instead of having it done in two (rules.c & builtins.c modules). 
[SVN r79584]
 2012-07-18 14:24:19 +00:00
Jurko Gospodnetić
1961065003 Boost Build no longer needs to add a fake INCLUDES relationship between targets generated by a single Boost Build action (reapplying revision [79571]). This is already done by Boost Jam internally for a single Boost Jam action and in case when the Boost Build action is actually a rule registering multiple actions - this was not causing any desirable behaviour. 
[SVN r79583]
 2012-07-18 14:08:35 +00:00
Jurko Gospodnetić
ca78bc40b2 Minor stylistic changes made to the Python Boost Build comment updated in the previous commit. 
[SVN r79582]
 2012-07-18 13:26:02 +00:00
Jurko Gospodnetić
714ed09cf4 Updated Boost Build implementation note comment related to why it adds an INCLUDES relation between all sources registered for a single Boost Build action. 
[SVN r79581]
 2012-07-18 13:24:40 +00:00
Jurko Gospodnetić
1b98bbbf74 Boost Build comment cleanup. 
[SVN r79580]
 2012-07-18 12:42:17 +00:00
Jurko Gospodnetić
e6a3faf35d Corrected the internal Boost Build generators_test.py unit test to correctly split its appender 'action' into separate appender1 actions (building only a single target each), and still have them all called correctly together or none at all. Old and too-simplistic solution registered called completely independent actions for each target, causing Boost Jam to build only some of the targets in some cases, unlike what it would have done had they all actually been built by a single action. 
[SVN r79579]
 2012-07-18 12:23:18 +00:00
Jurko Gospodnetić
ddbdcd0c04 Reverting revision [79571] since it broke the generators_test.py Boost Build test. It seems Boost Jam might not have the complete fix implemented to allow us to avoid this Boost Build code. 
[SVN r79573]
 2012-07-17 09:29:02 +00:00
Jurko Gospodnetić
ef8a393163 Boost Build code cleanup - Boost Build no longer needs to add a fake INCLUDES relationship between targets generated by a single action as this is already done by Boost Jam internally. 
[SVN r79571]
 2012-07-17 09:08:10 +00:00
Jurko Gospodnetić
21e5ae661a Boost Build code cleanup - scanner.install no longer taking an extra & never used vtarget parameter. 
NOTE: Defective - breaks the generators_test.py Boost Build test.

[SVN r79570]
 2012-07-17 09:03:38 +00:00
Jurko Gospodnetić
c16ae1c68a Boost Jam/Build cleanup - minor stylistic changes (comment updates; line wrapping; removed some dead/unused function declarations, parameters & code; declared variables as const; reordered some #include directives alphabetically, removed some unnecessary ones and added several missing ones discovered by the reordering). 
[SVN r79569]
 2012-07-17 08:56:49 +00:00
Jurko Gospodnetić
145ce56f80 Windows Boost Jam implementation now uses finer resolution than 1 second when creating timestamps based on the current system time. Since these are never (and should never be!) compared to file system timestamps - this causes no conflicts with file system timestamps still using 1 second resolution at best. 
Related stylistic changes:
  - filetime_to_timestamp() function renamed to timestamp_from_filetime() and moved to the timestamp.c module.
  - filetime_to_seconds() function moved back to the execnt.c module as a static function as it only used from there after the timestamp_from_filetime() reimplementation in revision [79494].
  - filent.h header now empty and removed.

[SVN r79511]
 2012-07-14 18:55:06 +00:00
Jurko Gospodnetić
c2858c8b5d Boost Jam code cleanup - extracted code for getting a timestamp for the current system time to timestamp_current(). 
[SVN r79507]
 2012-07-14 17:28:50 +00:00
Jurko Gospodnetić
e548f836d9 Boost Jam's internal timestamp data structure now holds a member for nanosecond information. This information is still always set to 0 but, if set, is used when needed. Updated Boost Jam's header cache file format to hold the new extended timestamp information (bumped format version up to 5). 
[SVN r79506]
 2012-07-14 17:17:09 +00:00
Jurko Gospodnetić
f18abd8674 Boost Jam now reports its timestamps using a bit more complete format (still ISO-8601 compliant) to include nanosecond information. The new format is 'YYYY-MM-DD HH:MM:SS.ZZZZZZZZZ +0000'. Currently the nanosecond part value is always 0. 
[SVN r79502]
 2012-07-14 16:36:56 +00:00
Jurko Gospodnetić
3736a64fd6 Boost Jam code cleanup - wrapped up timestamp values inside a timstamp structure instead of using a raw time_t value as another preparation step towards implementing support for timestamps with resolution finer than 1 second. All timestamp manipulation now done using the new timestamp_XXX() API. 
File timestamps displayed with -d+3 debug output now presented in UTC (+0000) timezone.

Other related minor stylistic changes:
  - timestamp_from_target() renamed to timestamp_from_path()
  - timestamp_from_target() parameter order switched
  - comment updates
  - added some const function parameter modifiers
  - some header #include directives reordered alphabetically

[SVN r79501]
 2012-07-14 16:11:16 +00:00
Jurko Gospodnetić
8202d97670 Boost Jam code cleanup - extracted Windows specific FILETIME structure conversion functions from execnt.c to a lowel level filent.c Windows specific module so they may be reused in both. Renamed the functions to make their purpose clearer. 
[SVN r79497]
 2012-07-14 13:23:45 +00:00
Jurko Gospodnetić
eb8c859a26 Boost Jam execnt.c module code cleanup. No longer attempts to perform some operations like closing alert windows or reading their output (before the code depended on some operations not doing anything if given invalid handles or process ids). No longer needs to find out the process id from a process handle (since it actually already had these process ids all along), thus avoiding hacks needed to support this on Windows versions prior to Windows XP SP1 (where there was no GetProcessId() Windows API). Minor stylistic changes. 
[SVN r79496]
 2012-07-14 13:10:00 +00:00
Jurko Gospodnetić
fe47abe424 Boost Jam code cleanup - removed a redundant #include directive. 
[SVN r79495]
 2012-07-14 11:49:52 +00:00
Jurko Gospodnetić
8e716991c8 Corrected Boost Jam's Windows FILETIME to POSIX time_t conversion. New implementation lifted shamelessly from the CPython implementation. The old implementation did not work correctly in all cases depending on the user's regional (timezone & daylight saving time) settings as well as the TZ environment variable (affects some C runtime library routines). It also used the double type to represent some interim values during its calculation - sometimes causing off-by-one rounding errors. 
[SVN r79494]
 2012-07-14 11:42:58 +00:00
Jurko Gospodnetić
743cc7ed4b Boost Jam code cleanup - minor stylistic code changes & comment updates. 
[SVN r79493]
 2012-07-14 11:35:29 +00:00
Jurko Gospodnetić
0a656de095 Boost Jam code cleanup - cleaned up the timestamp.c module identifiers and better commented its functions. 
[SVN r79489]
 2012-07-13 23:14:40 +00:00
Jurko Gospodnetić
fb8fb8317e Boost Jam code cleanup - minor stylistic code changes & comment updates. 
[SVN r79488]
 2012-07-13 23:11:45 +00:00
Jurko Gospodnetić
d7cf40907c Reverted accidental commit in revision 79486. 
[SVN r79487]
 2012-07-13 23:09:58 +00:00
Jurko Gospodnetić
ada97b6599 Boost Jam code cleanup - minor stylistic code changes & comment updates. 
[SVN r79486]
 2012-07-13 22:48:58 +00:00
Jurko Gospodnetić
b9fa41fecd Boost Jam code cleanup - minor stylistic changes. 
[SVN r79483]
 2012-07-13 20:15:00 +00:00
Jurko Gospodnetić
678fe54e15 Updated Boost Build tests to run the collect_debug_info.py test only when running the tests non-interactively, i.e. when collecting the test results in an xml output file. When running the tests interactively and observing the results on the console there is no need for this always-failing test to spoil the 'all tests passed' result - the user will generally know everything about his system and can still run this test directly if he wishes to see what it would have returned. 
[SVN r79478]
 2012-07-13 19:17:04 +00:00
Jurko Gospodnetić
53576e4073 Boost Build testing system code cleanup. Mainly stylistic changes + stopped using old deprecated string module functions in the test_all.py module. 
[SVN r79476]
 2012-07-13 19:03:54 +00:00
Jurko Gospodnetić
8bc155d307 Boost Build testing system cleanup - separated the concept of the 'time when a test run finished' from 'highest timestamp assigned by a test run'. This is a tiny preparation step towards making Boost Build support timestamp resolutions finer than 1 second. 
[SVN r79475]
 2012-07-13 18:43:18 +00:00
Jurko Gospodnetić
740cb760de Minor stylistic internal Boost Build testing system changes. 
[SVN r79474]
 2012-07-13 18:30:09 +00:00
Jurko Gospodnetić
09e4708742 Boost Build cleanup - removed an extra Python module import from the internal core_at_file.py Boost Build test. 
[SVN r79473]
 2012-07-13 18:20:34 +00:00
Jurko Gospodnetić
f0a27a9473 Minor stylistic changes. 
[SVN r79472]
 2012-07-13 16:42:25 +00:00
Steven Watanabe
8c067504b8 Make annoying unconditional hcache message only appear with DEBUG_HEADER. 
[SVN r79464]
 2012-07-13 01:53:46 +00:00
Jurko Gospodnetić
8bef878ab5 Boost Jam cleanup - minor stylistic changes. 
[SVN r79450]
 2012-07-12 13:36:31 +00:00
Jurko Gospodnetić
9905deabee Fixed a Boost Jam error reporting bug where it would report the error as originating from an incorrect file & line in case the error occurred after parsing the final token in some file. It usually reported it as the file including the file in question or, if the file is the main project build script not included from anywhere, then it reported the error as originating from file '(builtin)' and line -1. Added a related internal Boost Build unit test (core_source_line_tracking.py). 
[SVN r79449]
 2012-07-12 13:21:46 +00:00