| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
A bunch of these files were committed with Windows line encodings.
Strip all those ^M gremlins out as people working on Windows can
use git's autocrlf setting to convert back and forth as needed.
|
|
|
|
|
| |
We still enable them by default, but we'll probably flip them off
in the next major release series.
|
|
|
|
| |
This fixes #382.
|
| |
|
| |
|
|
|
|
|
| |
If the message doesn't contain any format flags (e.g. %s), don't force
the caller to pass in a dummy arg to make the compiler happy.
|
|
|
|
|
|
|
|
|
|
| |
This header provides a single define: GDTEST_TOP_DIR. Move it to the
build CPPFLAGS instead since it's a path var and that's the recommended
way of handling these (by autotools standards), and it simplifies the
build overall. It also harmonizes the autotool & cmake build paths.
We localize this define to the gdtest/ subdir as we don't want any of
the other tests using the path. We have gdtest helpers instead.
|
| |
|
| |
|
| |
|
|
|
|
| |
windows
|
|
|
|
|
|
| |
This makes it a bit cleaner when dealing with optional tests as we
use the LIST(APPEND...) command everywhere instead of sometimes SET
and sometimes LIST.
|
|
|
|
|
|
|
|
|
|
|
| |
A lot of tests want to read images/fonts that exist in tests/ for reading.
Rather than construct these paths by hand in every single test file, add a
few helper functions to quickly access them.
The helper functions are slightly slower (due to the repeated calls to the
strcat func), but they aren't terribly slow, especially relative to image
loading that these tests perform. They also make writing/maintaining the
tests a lot easier which is more important here.
|
| |
|
|
|
|
|
|
|
|
|
| |
Many of the tests open files in local paths for writing which leaves a
variety of temp files in the tests subdirs. This ends up failing in a
few scenarios like out of tree builds or cmake builds.
Add a few helper functions to the common gdtest module to quickly get
handles to temp files for the tests to leverage.
|
|
|
|
|
|
|
|
|
| |
Since we have random files we want to read & check, turn the two
read programs into general tools. Then we have shell scripts to
run against the right inputs.
Most of the changes here are just shuffling variable names so we
can add to check_PROGRAMS independently of TESTS.
|
|
|
|
|
| |
This matches what we've done with cmake files, and it makes managing
the subdirs much easier.
|
|
|
|
|
|
|
|
|
| |
This makes the test code a lot easier to manage rather than copying &
pasting the same boiler plate multiple times.
Also take the opportunity to add a common prefix to each test name so
we don't get collisions between subdirs if a test happens to use the
same exact name.
|
| |
|
|
|
|
|
| |
This makes it easier to keep track of things. The single toplevel list
can make it hard to notice when something is stale.
|
|
|
|
|
|
|
|
|
|
| |
gdnametest uses string funcs, so pull in string.h. It also can't pull
in test_config.h directly as it breaks when building out of tree. Use
the -I paths to find it.
bug00111 uses unlink(), so pull in unistd.h
URL: https://bugs.gentoo.org/540376
|
| |
|
| |
|
|
|
|
|
|
|
| |
failure messages.
Improve error reporting and diagnostics in gdimagefile test.
Fix 'max' definition conflict on some compilers.
|
|
These are convenience functions which load or save image data to a
file. They are roughly equivalent to opening a file handle with
fopen() and calling gdImageCreateFrom*() or gdImage*() on the FILE
pointer. However, these functions identify the input or output format
from the filename suffix and call the appropriate read or write
function accordingly.
gdSupportsFileType() can be used to test if a specific file format
is supported.
Most scripting interfaces already do something like this but now
there's support for doing it from C as well.
This change also adds test cases for the code and naturaldocs
documentation.
|