- 11 3月, 2021 1 次提交
-
-
由 mamingshuai 提交于
-
- 09 9月, 2020 1 次提交
-
-
由 wenjun 提交于
-
- 30 10月, 2019 3 次提交
-
-
由 mvandervoord 提交于
-
由 mvandervoord 提交于
Sigh. had to NOT disable these warnings by default because the gcc on our test rig doesn't understand it
-
由 mvandervoord 提交于
While we're fixing warnings / errors, disable this (otherwise helpful) error because we are purposefully making this example file fail for this.
-
- 25 10月, 2019 1 次提交
-
-
由 mvandervoord 提交于
-
- 21 10月, 2019 1 次提交
-
-
由 Mark VanderVoord 提交于
-
- 18 9月, 2019 4 次提交
-
-
由 Michael Brockus 提交于
Put source in an array, cleaned up script and fixed comment.
-
由 Michael Brockus 提交于
Removed newlines and fixed comment.
-
由 Michael Brockus 提交于
Added foreach loop to avoid DRY, Put source files in map structors, fixed comment.
-
由 Michael Brockus 提交于
Moved example dir variable into source meson.build script, fixed comment.
-
- 06 7月, 2019 3 次提交
-
-
由 Michael Brockus 提交于
-
由 Mark VanderVoord 提交于
-
由 Michael Brockus 提交于
-
- 04 7月, 2019 4 次提交
-
-
由 Michael Brockus 提交于
-
由 Michael Brockus 提交于
-
由 Michael Brockus 提交于
-
由 Michael Brockus 提交于
-
- 26 1月, 2019 2 次提交
-
-
由 teaguecl 提交于
This test case had an error in both examples: test_FindFunction_WhichIsBroken_ShouldReturnZeroIfItemIsNotInList_WhichWorksEvenInOurBrokenCode It was supposed to be a list of values that are NOT in the list, and none of them should be found. It incorrectly included '1'
-
由 teaguecl 提交于
This test case had an error: test_FindFunction_WhichIsBroken_ShouldReturnZeroIfItemIsNotInList_WhichWorksEvenInOurBrokenCode It was supposed to be a list of values that are NOT in the list, and none of them should be found. It incorrectly included '1' which is a value in the list. The compile option -Wno-misleading-indentation was also added to remove a compiler warning produced by gcc 7.3.0
-
- 25 1月, 2019 1 次提交
-
-
由 Fabian Zahn 提交于
-
- 29 11月, 2018 1 次提交
-
-
由 John Lindgren 提交于
-
- 02 11月, 2018 1 次提交
-
-
由 Mark VanderVoord 提交于
-
- 27 10月, 2018 1 次提交
-
-
由 Fabian Zahn 提交于
-
- 10 9月, 2018 5 次提交
-
-
由 Kyle Krueger 提交于
-
由 Kyle Krueger 提交于
This reverts commit 5d2ef070.
-
由 Kyle Krueger 提交于
-
由 Kyle Krueger 提交于
-
由 Kyle Krueger 提交于
-
- 10 9月, 2017 1 次提交
-
-
由 balaksh 提交于
-
- 09 9月, 2017 1 次提交
-
-
由 Mark VanderVoord 提交于
-
- 02 8月, 2017 1 次提交
-
-
由 Aviv Palivoda 提交于
The user can specify UNITY_OUTPUT_CHAR_HEADER_DECLARATION and UNITY_OUTPUT_FLUSH_HEADER_DECLARATION when he would like to declare UNITY_OUTPUT_CHAT or UNITY_OUTPUT_FLUSH respectivly
-
- 26 6月, 2017 1 次提交
-
-
由 Mark VanderVoord 提交于
- Fixed some style issues.
-
- 29 3月, 2017 1 次提交
-
-
由 Mark VanderVoord 提交于
-
- 28 3月, 2017 2 次提交
-
-
由 Mark VanderVoord 提交于
-
由 Mark VanderVoord 提交于
Starting to enforce our coding style. The first step is that we’ve pulled in Rubocop to check out Ruby syntax. There is likely a bit of customization to do yet AND there is definitely that backlog of todo’s that we just told it to ignore.
-
- 23 1月, 2017 1 次提交
-
-
由 jsalling 提交于
If, longer term, the Travis-CI support for 32-bit is inconsistent the lines that failed are: - make -s DEBUG=-m32 - cd ../example_3 && rake Add target 'ci' for building examples with -Werror
-
- 19 1月, 2017 1 次提交
-
-
由 jsalling 提交于
Altered the rake build so that it passes. The example_3 shows off some failing tests, so the rake build has to ignore those. Update .gitignore file with executables from examples
-
- 18 1月, 2017 2 次提交