Make it a little more clear how steps correspond, and add 'build'
to both workflow names so the intention of the runs is explicit
on the actions page.

This only runs on linux and macOS, but supports the important
`distcheck` target.

We ask homebrew to install libtool and pkg-config on macOS.
These are required for the autotools build, but aclocal
at least seems not to be available in the latest image.

We don't do a general homebrew update since that can take several
minutes, at least doubling the time it takes to runthhe job.
Just using the defaults the image provides is a better tradeoff.

Run cmake build and test steps on the three supported desktop
targets. Default compiler and so on is fine.

Although we define an environment variable to hold the path
to the cmake build directory, we must use the noisier expression
syntax of the github job builder to substitute into each
command line for portability across both unix and windows
shell syntax.

The windows image also requires an explicit build config
switch, `-C Debug` or similar, for ctest to execute even
though CMakeLists.txt doesn't define alternate build
configurations. On linux and macos ctest runs fine without
the extra argument.

These should match http://downloads.xiph.org/releases/ogg/SHA256SUMS

Result of running `make -C doc/libogg update-doc-version`.

Summarize recent changes, and bump the package version and soname.
There have been no interface changes, just bug fixes.

Daniel Engberg authored May 10, 2021 and Ralph Giles committed May 10, 2021

"Install CMake package configiguration module" --> configuration
Signed-off-by: Daniel Engberg <daniel.engberg.lists@pyret.net>
Signed-off-by: Ralph Giles <giles@thaumas.net>

Makes diffs a little more clean.

Ozkan Sezer authored Oct 04, 2020 and Ralph Giles committed Nov 05, 2020

The idea was to trigger maximum optimizations, but to date
compilers only go up to -O3, so this in ambiguous.
Signed-off-by: Ralph Giles <giles@thaumas.net>

Properly export Ogg target when added via `add_subdirectory()`.

newsize is a long, but storage is an int. This means the allocation
could succeed but storage would overflow.

Closes #2300

The link pointed to the wrong structure documentation.
Looks like a cut-and-paste error.

thp-hatch authored May 25, 2020 and Ralph Giles committed May 25, 2020

Signed-off-by: Ralph Giles <giles@thaumas.net>

Gitlab now supports a `default` section on the build description,
which sets defaults which can be overridden by specific jobs.

This encapsulates things a little better and avoid duplicating
runner tags.

Specify an explicit version of the base container image for more
repeatable results. Note that this will need to be bumped periodically.

We've moved hosting to a gitlab instance. Make use of the built-in
integration testing framework to verify commits.

This has parallel jobs to run the autotools and cmake builds.

Note that the autotools job needs cmake because the `distcheck`
target verifies that the generated source package also builds
correctly with cmake, in particular to check that the necessary
files are included.

This description of the build is old and unmaintained. It's not
useful to have untested code in the tree.
Signed-off-by: Thomas Daede <daede003@umn.edu>

This description of the build is very old, unmaintained, and
not integration tested. I don't think it's useful to users,
who can use the supported autotools or cmake builds, or just
add the few source files directly to their own projects.
Signed-off-by: Thomas Daede <daede003@umn.edu>

willson-chen authored Oct 14, 2019 and Tristan Matthews committed Apr 25, 2020

Close the C4244 warning while compiling under windows with cmake+msbuild.
Signed-off-by: Tristan Matthews <tmatth@videolan.org>

This effectively reverts f8ce071e which was
probably broken by 6449883c.

willson-chen authored Aug 24, 2019 and Ralph Giles committed Sep 05, 2019

add `make test` to README.md

On windows platform, building with MinGW can run 'make check' (autoconf)
and 'ctest' or 'make test' (cmake), while building with MSBuild can only
run 'ctest -c Release|Debug'.
Signed-off-by: Ralph Giles <giles@thaumas.net>

These should match http://downloads.xiph.org/releases/ogg/SHA256SUMS

Result of running make -C doc/libogg update-doc-version.

List of significant changes since the last release tag.

Describe how to update documentation versioning. No need for
sed one-liners each time.

Include everything in the cmake directory in the `make dist`
target. Fixes a missing include error in the CMake build
from a release tarball for `CheckSizes.cmake`.
Signed-off-by: Tristan Matthews <tmatth@videolan.org>

Verify that the CMake build works from a release tarball.
This will give coverage for problems with part of the
CMake build description not being included in the
source package. We still consider the `make dist`
output from the GNU autotools build to be canonical.

NB CMakelists was in the repo at the time of the 1.3.3 release,
but didn't make it into the 1.3.3 dist target, so it can't be
said to be available for that release.

willson-chen authored Aug 29, 2019 and Ralph Giles committed Aug 30, 2019

cmake in build dir is recommand by officially.
Signed-off-by: Ralph Giles <giles@thaumas.net>

Eugene Opalev authored Aug 24, 2019 and Ralph Giles committed Aug 30, 2019

Use the correct library filename and only package the dll
if the build produced one.
Signed-off-by: Ralph Giles <giles@thaumas.net>

Eugene Opalev authored Aug 24, 2019 and Ralph Giles committed Aug 30, 2019

The 2015 version of the project files can be opened by newer
versions of Visual Studio, and we want to deprecate the project
files in favour of the CMake build, so it doesn't make sense
to support three different versions.
Signed-off-by: Ralph Giles <giles@thaumas.net>