buildtool-cvs Mailing List for Buildtool (Page 2)
Status: Alpha
Brought to you by:
jmmv
You can subscribe to this list here.
2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(190) |
Jul
(66) |
Aug
(381) |
Sep
(312) |
Oct
(18) |
Nov
|
Dec
(1) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
(28) |
Feb
(52) |
Mar
(65) |
Apr
(2) |
May
(86) |
Jun
(2) |
Jul
(53) |
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
|
2005 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Julio M. M. V. <jm...@us...> - 2004-07-09 21:44:08
|
Module name: buildtool Committed by: jmmv Date: Fri Jul 9 21:44:01 UTC 2004 Modified Files: src/doc: CHANGES.mdoc Log Message: Open section for 0.17 (hmm, yet another alpha?) and note the rewrite of the testsuite and the fix of multiple bugs (not until now, but I'm sure I'll fix more ;). To generate a diff of this commit: cvs rdiff -r1.72 -r1.73 src/doc/CHANGES.mdoc Please note that diffs are not public domain; they are subject to the copyright notices on the relevant files. |
From: Julio M. M. V. <jm...@us...> - 2004-07-09 21:37:50
|
Module name: buildtool Committed by: jmmv Date: Fri Jul 9 21:37:43 UTC 2004 Modified Files: src/doc: PEOPLE.mdoc Log Message: Give credit to Bartosz Fenski, the Debian package maintainer. To generate a diff of this commit: cvs rdiff -r1.9 -r1.10 src/doc/PEOPLE.mdoc Please note that diffs are not public domain; they are subject to the copyright notices on the relevant files. |
From: Julio M. M. V. <jm...@us...> - 2004-07-09 21:37:50
|
Module name: buildtool Committed by: jmmv Date: Fri Jul 9 21:37:43 UTC 2004 Modified Files: src: PEOPLE Log Message: Give credit to Bartosz Fenski, the Debian package maintainer. To generate a diff of this commit: cvs rdiff -r1.15 -r1.16 src/PEOPLE Please note that diffs are not public domain; they are subject to the copyright notices on the relevant files. |
From: Julio M. M. V. <jm...@us...> - 2004-07-09 21:32:30
|
Module name: buildtool Committed by: jmmv Date: Fri Jul 9 21:32:24 UTC 2004 Added Files: src/testsuite/docs: DOC1 DOC2 Docs.bt test.sh Log Message: Add the 'docs' test which verifies that the installation of (build-time) documents works. Yeah, it already helped in catching two more bugs :) To generate a diff of this commit: cvs rdiff -r0 -r1.1 src/testsuite/docs/DOC1 src/testsuite/docs/DOC2 \ src/testsuite/docs/Docs.bt src/testsuite/docs/test.sh Please note that diffs are not public domain; they are subject to the copyright notices on the relevant files. |
From: Julio M. M. V. <jm...@us...> - 2004-07-09 21:32:30
|
Module name: buildtool Committed by: jmmv Date: Fri Jul 9 21:32:24 UTC 2004 Modified Files: src/testsuite: test.sh Log Message: Add the 'docs' test which verifies that the installation of (build-time) documents works. Yeah, it already helped in catching two more bugs :) To generate a diff of this commit: cvs rdiff -r1.3 -r1.4 src/testsuite/test.sh Please note that diffs are not public domain; they are subject to the copyright notices on the relevant files. |
From: Julio M. M. V. <jm...@us...> - 2004-07-09 21:30:40
|
Module name: buildtool Committed by: jmmv Date: Fri Jul 9 21:30:33 UTC 2004 Modified Files: src/bt_config: general.in Log Message: Fix installation of documents when using work directories. It failed for two reasons: first, the chunk in bt_config that creates the post installation hook referred to BT_TOPDIR, while it should be BT_WORKDIR (to know where the build actually is); and second, bt_logic was looking for the documents in the object directory. We can assume that they are in the source tree (these are the sematics of bt_doc), so we use a full path. To generate a diff of this commit: cvs rdiff -r1.102 -r1.103 src/bt_config/general.in Please note that diffs are not public domain; they are subject to the copyright notices on the relevant files. |
From: Julio M. M. V. <jm...@us...> - 2004-07-09 21:30:39
|
Module name: buildtool Committed by: jmmv Date: Fri Jul 9 21:30:33 UTC 2004 Modified Files: src/bt_logic: docs.in Log Message: Fix installation of documents when using work directories. It failed for two reasons: first, the chunk in bt_config that creates the post installation hook referred to BT_TOPDIR, while it should be BT_WORKDIR (to know where the build actually is); and second, bt_logic was looking for the documents in the object directory. We can assume that they are in the source tree (these are the sematics of bt_doc), so we use a full path. To generate a diff of this commit: cvs rdiff -r1.9 -r1.10 src/bt_logic/docs.in Please note that diffs are not public domain; they are subject to the copyright notices on the relevant files. |
From: Julio M. M. V. <jm...@us...> - 2004-07-09 21:19:02
|
Module name: buildtool Committed by: jmmv Date: Fri Jul 9 21:18:56 UTC 2004 Modified Files: src/bt_logic: stages.in Log Message: If there are no targets to build, exit with successful status (0). To generate a diff of this commit: cvs rdiff -r1.18 -r1.19 src/bt_logic/stages.in Please note that diffs are not public domain; they are subject to the copyright notices on the relevant files. |
From: Julio M. M. V. <jm...@us...> - 2004-07-09 21:07:47
|
Module name: buildtool Committed by: jmmv Date: Fri Jul 9 21:07:40 UTC 2004 Modified Files: src/bt_config: general.in Log Message: Fix minor typo in comment. To generate a diff of this commit: cvs rdiff -r1.101 -r1.102 src/bt_config/general.in Please note that diffs are not public domain; they are subject to the copyright notices on the relevant files. |
From: Julio M. M. V. <jm...@us...> - 2004-07-09 21:07:16
|
Module name: buildtool Committed by: jmmv Date: Fri Jul 9 21:07:09 UTC 2004 Modified Files: src/bt_config: general.in Log Message: Remove the bt_logic log file after removing all other files from the top directory (i.e., do it as the last step). This is to ensure that it gets removed; otherwise, the commands executed after its deletion recreate the log file. BTW, first problem found by the new testsuite :) To generate a diff of this commit: cvs rdiff -r1.100 -r1.101 src/bt_config/general.in Please note that diffs are not public domain; they are subject to the copyright notices on the relevant files. |
From: Julio M. M. V. <jm...@us...> - 2004-07-09 17:13:40
|
Module name: buildtool Committed by: jmmv Date: Fri Jul 9 17:13:34 UTC 2004 Modified Files: src/testsuite: test.subr Log Message: Verify that tests don't leave stale files in their directories. If they do, make that test fail. To generate a diff of this commit: cvs rdiff -r1.1 -r1.2 src/testsuite/test.subr Please note that diffs are not public domain; they are subject to the copyright notices on the relevant files. |
From: Julio M. M. V. <jm...@us...> - 2004-07-09 17:00:57
|
Module name: buildtool Committed by: jmmv Date: Fri Jul 9 17:00:51 UTC 2004 Modified Files: src/testsuite: test.sh Log Message: Run check_progs before check_envs (as environments depend on program checks, it's more logic to go from simple things to more complex ones). To generate a diff of this commit: cvs rdiff -r1.2 -r1.3 src/testsuite/test.sh Please note that diffs are not public domain; they are subject to the copyright notices on the relevant files. |
From: Julio M. M. V. <jm...@us...> - 2004-07-09 16:59:19
|
Module name: buildtool Committed by: jmmv Date: Fri Jul 9 16:59:10 UTC 2004 Modified Files: src/testsuite: test.sh Log Message: Add the config_args test, which checks if the customizable features and directories provided by bt_config work. To generate a diff of this commit: cvs rdiff -r1.1 -r1.2 src/testsuite/test.sh Please note that diffs are not public domain; they are subject to the copyright notices on the relevant files. |
From: Julio M. M. V. <jm...@us...> - 2004-07-09 16:59:18
|
Module name: buildtool Committed by: jmmv Date: Fri Jul 9 16:59:10 UTC 2004 Added Files: src/testsuite/config_args: Config.bt test.sh Log Message: Add the config_args test, which checks if the customizable features and directories provided by bt_config work. To generate a diff of this commit: cvs rdiff -r0 -r1.1 src/testsuite/config_args/Config.bt \ src/testsuite/config_args/test.sh Please note that diffs are not public domain; they are subject to the copyright notices on the relevant files. |
From: Julio M. M. V. <jm...@us...> - 2004-07-09 16:47:37
|
Module name: buildtool Committed by: jmmv Date: Fri Jul 9 16:47:31 UTC 2004 Modified Files: src/testsuite/check_envs: test.sh Log Message: Enable developer checks so that compiler flags are tested. To generate a diff of this commit: cvs rdiff -r1.1 -r1.2 src/testsuite/check_envs/test.sh Please note that diffs are not public domain; they are subject to the copyright notices on the relevant files. |
From: Julio M. M. V. <jm...@us...> - 2004-07-09 16:46:30
|
Module name: buildtool Committed by: jmmv Date: Fri Jul 9 16:46:24 UTC 2004 Modified Files: src/testsuite/check_progs: Config.bt Log Message: Run all known bt_check_prog_* tests. To generate a diff of this commit: cvs rdiff -r1.1 -r1.2 src/testsuite/check_progs/Config.bt Please note that diffs are not public domain; they are subject to the copyright notices on the relevant files. |
From: Julio M. M. V. <jm...@us...> - 2004-07-09 11:29:17
|
Module name: buildtool Committed by: jmmv Date: Fri Jul 9 11:29:09 UTC 2004 Modified Files: src: Makefile.in Log Message: The testsuite is now run by test.sh, not dotest.sh. To generate a diff of this commit: cvs rdiff -r1.80 -r1.81 src/Makefile.in Please note that diffs are not public domain; they are subject to the copyright notices on the relevant files. |
From: Julio M. M. V. <jm...@us...> - 2004-07-09 11:26:22
|
Module name: buildtool Committed by: jmmv Date: Fri Jul 9 11:26:14 UTC 2004 Added Files: src/testsuite/static_lib/src: Logic.bt testprog.c Log Message: Replace the old and (completely?) useless testsuite with something more sophisticated. The goal is to have a full suite of (regression) tests that verify as most parts of Buildtool as possible (in the aim of TDD). This way one can add new features and check that they not break previous funcionality. It'll also be easier to check all the features before a new version is released. Up until now, it was a PITA, as I had to manually build and install Buildtool in several platforms, and check different projects that use it, all by hand. You can imagine that this is a very error prone (and boring) process. Each test should be able to execute a set of operations and then verify that the results are correct to what's expected. These steps are handled from the 'test.sh' script inside each subdirectory. By running 'test.sh' from the top directory, all tests are executed and a summary is printed at the very end showing which ones went successfully and which ones failed. This still lacks a lot of work (i.e., many more tests have to be added), but the basic functionality is already there. To generate a diff of this commit: cvs rdiff -r0 -r1.1 src/testsuite/static_lib/src/Logic.bt \ src/testsuite/static_lib/src/testprog.c Please note that diffs are not public domain; they are subject to the copyright notices on the relevant files. |
From: Julio M. M. V. <jm...@us...> - 2004-07-09 11:26:22
|
Module name: buildtool Committed by: jmmv Date: Fri Jul 9 11:26:13 UTC 2004 Added Files: src/testsuite/plain_prog/src: Logic.bt testprog.c Log Message: Replace the old and (completely?) useless testsuite with something more sophisticated. The goal is to have a full suite of (regression) tests that verify as most parts of Buildtool as possible (in the aim of TDD). This way one can add new features and check that they not break previous funcionality. It'll also be easier to check all the features before a new version is released. Up until now, it was a PITA, as I had to manually build and install Buildtool in several platforms, and check different projects that use it, all by hand. You can imagine that this is a very error prone (and boring) process. Each test should be able to execute a set of operations and then verify that the results are correct to what's expected. These steps are handled from the 'test.sh' script inside each subdirectory. By running 'test.sh' from the top directory, all tests are executed and a summary is printed at the very end showing which ones went successfully and which ones failed. This still lacks a lot of work (i.e., many more tests have to be added), but the basic functionality is already there. To generate a diff of this commit: cvs rdiff -r0 -r1.1 src/testsuite/plain_prog/src/Logic.bt \ src/testsuite/plain_prog/src/testprog.c Please note that diffs are not public domain; they are subject to the copyright notices on the relevant files. |
From: Julio M. M. V. <jm...@us...> - 2004-07-09 11:26:22
|
Module name: buildtool Committed by: jmmv Date: Fri Jul 9 11:26:13 UTC 2004 Removed Files: src/testsuite/lib: Logic.bt testlib.c testlib.h testlib_top.h Log Message: Replace the old and (completely?) useless testsuite with something more sophisticated. The goal is to have a full suite of (regression) tests that verify as most parts of Buildtool as possible (in the aim of TDD). This way one can add new features and check that they not break previous funcionality. It'll also be easier to check all the features before a new version is released. Up until now, it was a PITA, as I had to manually build and install Buildtool in several platforms, and check different projects that use it, all by hand. You can imagine that this is a very error prone (and boring) process. Each test should be able to execute a set of operations and then verify that the results are correct to what's expected. These steps are handled from the 'test.sh' script inside each subdirectory. By running 'test.sh' from the top directory, all tests are executed and a summary is printed at the very end showing which ones went successfully and which ones failed. This still lacks a lot of work (i.e., many more tests have to be added), but the basic functionality is already there. To generate a diff of this commit: cvs rdiff -r1.1 -r0 src/testsuite/lib/testlib.h \ src/testsuite/lib/testlib_top.h cvs rdiff -r1.2 -r0 src/testsuite/lib/testlib.c cvs rdiff -r1.5 -r0 src/testsuite/lib/Logic.bt Please note that diffs are not public domain; they are subject to the copyright notices on the relevant files. |
From: Julio M. M. V. <jm...@us...> - 2004-07-09 11:26:22
|
Module name: buildtool Committed by: jmmv Date: Fri Jul 9 11:26:13 UTC 2004 Added Files: src/testsuite/plain_prog: Config.bt FlatLogic.bt SparseLogic.bt test.sh Log Message: Replace the old and (completely?) useless testsuite with something more sophisticated. The goal is to have a full suite of (regression) tests that verify as most parts of Buildtool as possible (in the aim of TDD). This way one can add new features and check that they not break previous funcionality. It'll also be easier to check all the features before a new version is released. Up until now, it was a PITA, as I had to manually build and install Buildtool in several platforms, and check different projects that use it, all by hand. You can imagine that this is a very error prone (and boring) process. Each test should be able to execute a set of operations and then verify that the results are correct to what's expected. These steps are handled from the 'test.sh' script inside each subdirectory. By running 'test.sh' from the top directory, all tests are executed and a summary is printed at the very end showing which ones went successfully and which ones failed. This still lacks a lot of work (i.e., many more tests have to be added), but the basic functionality is already there. To generate a diff of this commit: cvs rdiff -r0 -r1.1 src/testsuite/plain_prog/Config.bt \ src/testsuite/plain_prog/FlatLogic.bt \ src/testsuite/plain_prog/SparseLogic.bt src/testsuite/plain_prog/test.sh Please note that diffs are not public domain; they are subject to the copyright notices on the relevant files. |
From: Julio M. M. V. <jm...@us...> - 2004-07-09 11:26:21
|
Module name: buildtool Committed by: jmmv Date: Fri Jul 9 11:26:14 UTC 2004 Removed Files: src/testsuite/src: Logic.bt testprog.c Log Message: Replace the old and (completely?) useless testsuite with something more sophisticated. The goal is to have a full suite of (regression) tests that verify as most parts of Buildtool as possible (in the aim of TDD). This way one can add new features and check that they not break previous funcionality. It'll also be easier to check all the features before a new version is released. Up until now, it was a PITA, as I had to manually build and install Buildtool in several platforms, and check different projects that use it, all by hand. You can imagine that this is a very error prone (and boring) process. Each test should be able to execute a set of operations and then verify that the results are correct to what's expected. These steps are handled from the 'test.sh' script inside each subdirectory. By running 'test.sh' from the top directory, all tests are executed and a summary is printed at the very end showing which ones went successfully and which ones failed. This still lacks a lot of work (i.e., many more tests have to be added), but the basic functionality is already there. To generate a diff of this commit: cvs rdiff -r1.2 -r0 src/testsuite/src/testprog.c cvs rdiff -r1.8 -r0 src/testsuite/src/Logic.bt Please note that diffs are not public domain; they are subject to the copyright notices on the relevant files. |
From: Julio M. M. V. <jm...@us...> - 2004-07-09 11:26:21
|
Module name: buildtool Committed by: jmmv Date: Fri Jul 9 11:26:14 UTC 2004 Added Files: src/testsuite/static_lib/lib: Logic.bt testlib.c testlib.h Log Message: Replace the old and (completely?) useless testsuite with something more sophisticated. The goal is to have a full suite of (regression) tests that verify as most parts of Buildtool as possible (in the aim of TDD). This way one can add new features and check that they not break previous funcionality. It'll also be easier to check all the features before a new version is released. Up until now, it was a PITA, as I had to manually build and install Buildtool in several platforms, and check different projects that use it, all by hand. You can imagine that this is a very error prone (and boring) process. Each test should be able to execute a set of operations and then verify that the results are correct to what's expected. These steps are handled from the 'test.sh' script inside each subdirectory. By running 'test.sh' from the top directory, all tests are executed and a summary is printed at the very end showing which ones went successfully and which ones failed. This still lacks a lot of work (i.e., many more tests have to be added), but the basic functionality is already there. To generate a diff of this commit: cvs rdiff -r0 -r1.1 src/testsuite/static_lib/lib/Logic.bt \ src/testsuite/static_lib/lib/testlib.c \ src/testsuite/static_lib/lib/testlib.h Please note that diffs are not public domain; they are subject to the copyright notices on the relevant files. |
From: Julio M. M. V. <jm...@us...> - 2004-07-09 11:26:21
|
Module name: buildtool Committed by: jmmv Date: Fri Jul 9 11:26:14 UTC 2004 Added Files: src/testsuite/static_lib: Config.bt FlatLogic.bt SparseLogic.bt test.sh Log Message: Replace the old and (completely?) useless testsuite with something more sophisticated. The goal is to have a full suite of (regression) tests that verify as most parts of Buildtool as possible (in the aim of TDD). This way one can add new features and check that they not break previous funcionality. It'll also be easier to check all the features before a new version is released. Up until now, it was a PITA, as I had to manually build and install Buildtool in several platforms, and check different projects that use it, all by hand. You can imagine that this is a very error prone (and boring) process. Each test should be able to execute a set of operations and then verify that the results are correct to what's expected. These steps are handled from the 'test.sh' script inside each subdirectory. By running 'test.sh' from the top directory, all tests are executed and a summary is printed at the very end showing which ones went successfully and which ones failed. This still lacks a lot of work (i.e., many more tests have to be added), but the basic functionality is already there. To generate a diff of this commit: cvs rdiff -r0 -r1.1 src/testsuite/static_lib/Config.bt \ src/testsuite/static_lib/FlatLogic.bt \ src/testsuite/static_lib/SparseLogic.bt src/testsuite/static_lib/test.sh Please note that diffs are not public domain; they are subject to the copyright notices on the relevant files. |
From: Julio M. M. V. <jm...@us...> - 2004-07-09 11:26:20
|
Module name: buildtool Committed by: jmmv Date: Fri Jul 9 11:26:13 UTC 2004 Added Files: src/testsuite/check_progs/bin: fakeprog Log Message: Replace the old and (completely?) useless testsuite with something more sophisticated. The goal is to have a full suite of (regression) tests that verify as most parts of Buildtool as possible (in the aim of TDD). This way one can add new features and check that they not break previous funcionality. It'll also be easier to check all the features before a new version is released. Up until now, it was a PITA, as I had to manually build and install Buildtool in several platforms, and check different projects that use it, all by hand. You can imagine that this is a very error prone (and boring) process. Each test should be able to execute a set of operations and then verify that the results are correct to what's expected. These steps are handled from the 'test.sh' script inside each subdirectory. By running 'test.sh' from the top directory, all tests are executed and a summary is printed at the very end showing which ones went successfully and which ones failed. This still lacks a lot of work (i.e., many more tests have to be added), but the basic functionality is already there. To generate a diff of this commit: cvs rdiff -r0 -r1.1 src/testsuite/check_progs/bin/fakeprog Please note that diffs are not public domain; they are subject to the copyright notices on the relevant files. |