| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
From https://github.com/ingydotnet/yaml-libyaml-pm/issues/24
|
|
|
|
|
|
|
|
|
| |
Also reworked all the dockerfiles to be cleaner and consistent:
* Fixed some indentation
* Removed vim dependencies
* Collapsed RUN steps for less build layers
* Renamed dockerfiles/ to shorter and more adaptable docker/
|
|
|
|
|
|
|
|
| |
Without this change building a dll with the mingw-w64 toolchain is
impossible. All tests from make test-all succeed on native linux
(Gentoo amd64 glibc default/linux/amd64/17.1/desktop gcc-7.2.0)
Signed-off-by: Marty E. Plummer <hanetzer@protonmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In the Makefile.am, switched out the fetch (which can have auth problems
in certain envs) with a simple branch per @perlpunk++'s suggestion.
With the new test branches, travis had a problem in that it only clones
one branch and we need the other branch refs to be available. Fixed this
by fetching the other branch refs. I also cleaned up the travis YAML
file.
The Ubuntu 14.04 docker image (used by semaphoreci) had an older git,
without the worktree command, so I made it install the latest git from a
ppa.
Renamed tests/run-tests.sh to tests/run-all-tests.sh for tab completion
conflict reasons.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
with the intent that `make test-suite` will use it as a branch.
This commit makes the libyaml and yaml-test-suite repos completely
independent. The only thing in master is a Makefile rule for
`make run-test-suite`.
The run-test-suite branch takes care of everything else.
This will keep the master branch history clean from any yaml-test-suite
activity, while keeping everything up to date.
Pinning will just work for whatever commit of master you run the tests
from. The pinning work will all be done in the `run-test-suite` branch.
|
| |
|
|
|
|
|
| |
yaml-test-suite/data commit:
daf799e 2017-12-23 "Regenerated data from master 1eacbab"
|
|
|
|
| |
Seems to be the case on HP-UX
|
|
|
|
| |
See also issue #68
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
No recursive make anymore
Remove MY_LD_LIBRARY_PATH and friends
This is now done by the wrapper script
Remove LIBYAML_DIR variable
not needed anymore
Merge ReadMe.md files to one
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
New build options
-----------------
* Add option BUILD_TESTING by default ON
See https://cmake.org/cmake/help/v2.8.12/cmake.html#module:CTest
* Simplify library type selection using standard option BUILD_SHARED_LIBS
See https://cmake.org/cmake/help/v3.0/variable/BUILD_SHARED_LIBS.html
yamlConfig.cmake
----------------
* Generate and install yamlConfig.cmake, yamlConfigVersion.cmake and yamlTargets.cmake
* Bump CMake version and explicitly associate include dirs with targets
See https://cmake.org/cmake/help/v3.0/manual/cmake-buildsystem.7.html#include-directories-and-usage-requirements
* Ensure building against libyaml using "find_package(yaml)" uses expected compile options: Set HAVE_CONFIG_H
as private compile option, YAML_DECLARE_STATIC as public
Testing
-------
* Build all examples from "tests" directory
CMake Best practices
--------------------
* configure "config.h" based on version info found in CMakeLists.txt
* Ensure buildsystem re-generation listing sources (best-practice)
It is not recommended to use GLOB to collect a list of source files from
the source tree. If no CMakeLists.txt file changes when a source is added
or removed then the generated build system cannot know when to ask CMake
to regenerate.
See https://cmake.org/cmake/help/v3.8/command/file.html
Compilation warnings
--------------------
* Set _CRT_SECURE_NO_WARNINGS if building using VisualStudio
This will avoid warnings like this one:
```
C:\projects\libyaml\tests\run-emitter.c(268): warning C4996: 'fopen':
This function or variable may be unsafe. Consider using fopen_s instead.
To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for
details.
```
Continuous Integration
----------------------
* travis: Install CMake >= 3.x using scikit-ci-addons
* Add comments to appveyor.yml and run-tests.sh
|
| |
|
|
|
|
|
|
|
| |
Google's OSS Fuzz project found input for libyaml that was capable of
triggering an uninitialized value crash.
Patch provided by Alex Gaynor
|
|
|
| |
addresses issue #52
|
| |
|
|
|
|
|
| |
This way as the test suite grows, new tests won't disturb/break our
testing.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We can add various development activities to this alternate Makefile.
If you do this first:
```
ln {.,GNU}makefile
```
then you can use the new targets and the old ones without specifying the
`.makefile` in make commands and without worrying about bootstrap.
ie Before this, to use Makefile targets, you needed to run `./bootstrap`
and `./configure` first. This file will proxy all common Makefile
targets, first making sure that the Makefile exists.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The Dockerfiles needed to set LD_LIBRARY_PATH.
For some bizarre reason I needed to build the parser and emitter twice.
Since I plan to redo the building of these binaries later, this is OK
for now, since all tests on all CICDs will pass.
The docker stuff was needed by the semaphoreci system.
|
|
|
|
|
|
|
|
|
|
| |
Before the `make test-suite` command would clone yaml/libyaml-test which
would in tuen clone yaml/libyaml-parser-emitter. Now they are part of
the repository since they are not really useful outside the repository.
They still clone the data branch of yaml/yaml-test-suite. That is where
all the actual test data resides. That belongs outside the repo because
it is intended for all yaml frameworks.
|
|
|
|
|
|
|
|
| |
This allows us to run the same Travis testing locally.
Examples:
./tests/run-tests.sh
|
| |
|
|
|
|
|
| |
This should cover the remainder of the warnings found on the Travis CI
OSX builder.
|
|
|
|
|
|
|
| |
There were several places in our test deconstructor where we were
passing plain char[]s to functions expecting (yaml_char_t *)s. Since we
will soon be forcing warnings to become errors, it makes sense to clean
these up.
|
|
|
|
|
| |
Let's start warning on everything and we'll clean the warnings up as we
go along.
|
| |
|
|
|
|
| |
This runs `make test` and `make test-suite`.
|
|
|
|
|
|
|
|
|
|
|
| |
Add `test-suite` rule to Makefile. This test clones the libyaml-test
repo (which then clones the libyaml-parser and libyaml-emitter repos)
and calls `make test` in it. That in turn clone yaml/yaml-test suite.
Normally the subtests will clone the latest libyaml, but this test
passes the current libyaml via an environment variable.
Also add `test-all` to run this together with normal `make test` rule.
|
|
|
|
| |
This should catch the problems Ingy saw locally
|
|
|
|
|
| |
There were several warnings generated by formatting errors in the tests,
this corrects the format strings and silences the warnings.
|
|
|
|
|
|
|
|
| |
autoconf deprecated INCLUDE around version 2.69. No other automake file
in the project uses INCLUDE (instead they use AM_CPPFLAGS) and this
warning prevents the bootstrap-configure-make process from working on
OSX for me. Updating the variable name in the include/Makefile.am fixes
this and allows me to move along with development on OSX.
|
| |
|
|
|
|
|
| |
Previously we pointed at BitBucket, but we're using GitHub now, so we
should update that.
|
| |
|
|
|
| |
From the yaml spec
|
| |
|
| |
|
|
|
|
|
| |
As opposed to having a single Dockerfile with support for only one
distro.
|
|
|
|
| |
Uses ubuntu 16.04. `make test` is not yet working.
|
| |
|
|
|
| |
https://en.wiktionary.org/wiki/preceed
|
| |
|
| |
|
| |
|
|
|
|
|
| |
See also
https://github.com/ruby/psych/commit/66fb7fb77533d0606748940288858794752d95cb
|
| |
|
|
|
|
| |
Support "\/" for JSON compatability.
|