Package Details: criterion 2.3.2-1

Git Clone URL: https://aur.archlinux.org/criterion.git (read-only)
Package Base: criterion
Description: A KISS, non-intrusive unit testing framework for C and C++
Upstream URL: http://github.com/Snaipe/criterion.git
Licenses: MIT
Submitter: Snaipe
Maintainer: Snaipe
Last Packager: Snaipe
Votes: 3
Popularity: 0.005460
First Submitted: 2015-09-22 11:32
Last Updated: 2017-12-02 18:12

Required by (0)

Sources (1)

Latest Comments

1 2 Next › Last »

dellamorte commented on 2017-12-02 21:48

I want to write a short review of criterion, thats why i need good documentation for refernecing. Thanks, and keep up the good work!

Ethyling commented on 2017-12-02 20:46

@Snaipe Thanks !

Snaipe commented on 2017-12-02 18:21

dellamorte: Ah I can see where the confusion stems from. The bleeding branch has not bumped the version, so the docs that are built are marked 2.3.2, but they aren't release documents.

You can see that the URL you posted is, in fact, the `lastest` docs. For 2.3.0 docs, use https://media.readthedocs.org/pdf/criterion/v2.3.0/criterion.pdf instead.

The new assertion API is not part of any release at the moment, so criterion/new/assert.h wouldn't exist.

dellamorte commented on 2017-12-02 18:18

Thanks! Actually API references in described pdf are different from those in actual build. Readthedocs is ok. Also, which assertion API is newer?

a) cr_assert_eq(Actual, Expected, FormatString, ...)
b) cr_assert(eq(Tag, Actual, Expected), Format, ...)

Pdf documentation (https://media.readthedocs.org/pdf/criterion/latest/criterion.pdf) is tagged as for 2.3.2 but i can't compile simple code like this one:

#include <criterion/criterion.h>
#include <criterion/new/assert.h>

Test(sample,test){
cr_assert(eq(i8,1,1),"Fail");
}

Error is:

test2.c:2:10: fatal error: criterion/new/assert.h: No such file or directory
#include <criterion/new/assert.h>
^~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated

Snaipe commented on 2017-12-02 18:13

Ethyling: Fixed.

Snaipe commented on 2017-12-02 17:51

Oh, okay, it seems that the install rule is installing an external dependency at the wrong place. This is a bug in Criterion's build system, but fixable in the PKGBUILD without re-releasing anything, so I'll do just that and fix the CMakeLists.txt for future releases.

Ethyling commented on 2017-12-02 17:35

Hi, thanks for the fix, I can now build the package with makepkg.
Otherwise I got an error when I try to install it using pacman -U :

:: Proceed with installation? [Y/n]
error: failed to commit transaction (conflicting files)
criterion: /tmp/criterion/src/criterion/build/external/include/boxfort.h exists in filesystem
criterion: /tmp/criterion/src/criterion/build/external/lib/libboxfort.a exists in filesystem
Errors occurred, no packages were upgraded.

Could you please look at this ? Or maybe I'm missing some details ?

Snaipe commented on 2017-12-02 17:07

@dellamorte: Due to a bug in the sphynx configuration for the 2.3.1 and 2.3.2 releases, the docs were not generated on readthedocs.

I would recommend reading the 2.3.0 documentation instead, as no major changes underwent between these releases.

Snaipe commented on 2017-12-02 16:55

@Ethyling: Done! Thanks for reporting this.

dellamorte commented on 2017-12-02 13:47

Hi! API in 2.3.2-1 differs from documentation for the same version. Please provide documentation or update package. Great software anyway!