Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

autoconf etc. #2082

Closed
themaddoctor opened this issue Mar 31, 2024 · 1 comment
Closed

autoconf etc. #2082

themaddoctor opened this issue Mar 31, 2024 · 1 comment

Comments

@themaddoctor
Copy link

Hi,

Could you please make it possible to compile aom and libavif without cmake?
Or, alternatively, could you tell me how to build libarchive so that it passes its tests, and how to get cmake to recognize the system libuv, and any other errors that come up trying to upgrade cmake?

Thank you.

@y-guyon
Copy link
Collaborator

y-guyon commented Apr 2, 2024

Thank you for your interest in libavif.

Could you please make it possible to compile aom and libavif without cmake?

I will only speak about libavif here, as aom is another project.
We believe CMake is a widespread enough build system and maintaining multiple build systems is not one of our priorities for the moment.
Could you share more details about your use case where you cannot use CMake please?

could you tell me how to build libarchive so that it passes its tests

Sure, here is how to build libavif:
https://github.com/AOMediaCodec/libavif#command-lines

See the part about building all tests too:
https://github.com/AOMediaCodec/libavif#tests

The Continuous Integration tests run by GitHub workflows also contain bash command lines. Feel free to take a look:

- name: Prepare libavif (cmake)
run: >
mkdir build && cd build
cmake .. -G Ninja
-DCMAKE_BUILD_TYPE=${{ matrix.build-type }} -DBUILD_SHARED_LIBS=OFF
-DAVIF_CODEC_AOM=LOCAL -DAVIF_CODEC_DAV1D=LOCAL
-DAVIF_CODEC_RAV1E=LOCAL -DAVIF_CODEC_SVT=LOCAL
-DAVIF_CODEC_LIBGAV1=LOCAL -DAVIF_LIBYUV=LOCAL
-DAVIF_LIBSHARPYUV=LOCAL
-DAVIF_BUILD_EXAMPLES=ON -DAVIF_BUILD_APPS=ON
-DAVIF_BUILD_TESTS=ON -DAVIF_ENABLE_GTEST=ON -DAVIF_LOCAL_GTEST=ON
-DAVIF_ENABLE_EXPERIMENTAL_YCGCO_R=ON
-DAVIF_ENABLE_EXPERIMENTAL_GAIN_MAP=ON
-DAVIF_ENABLE_EXPERIMENTAL_AVIR=ON
-DAVIF_ENABLE_WERROR=ON
- name: Build libavif (ninja)
working-directory: ./build
run: ninja
- name: Run AVIF Tests
working-directory: ./build
run: ctest -j $(getconf _NPROCESSORS_ONLN) --output-on-failure

how to get cmake to recognize the system libuv

(assuming you are talking about building libavif and linking to the system-installed libyuv)
This should be the default behavior, corresponding to the CMake flag -DAVIF_LIBYUV=SYSTEM. What is your build environment (OS etc.)?

any other errors that come up trying to upgrade cmake

Not sure what you meant here.

@vrabaud vrabaud closed this as not planned Won't fix, can't repro, duplicate, stale Apr 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants