How do I build OpenSceneGraph dependencies on Windows using osg-3rdparty-cmake?

Download the CMake scripts and source code for each library, then use CMake GUI to configure and generate a Visual Studio solution. Build the ALL_BUILD and INSTALL targets for debug and release to populate the 3rdParty folder with organized libraries.

Can I use osg-3rdparty-cmake on Linux or macOS?

The CMake scripts should work cross-platform, but prebuilt binaries are only for Windows. You'll need to compile everything from source, which might be more complex than using native package managers for dependencies.

How to update a library version in osg-3rdparty-cmake?

Manually download the new source code for the library and update the source path in CMake. Check the versions.md file for compatibility, as the project doesn't automate version updates.

What's the difference between osg-3rdparty-cmake and using vcpkg for OpenSceneGraph?

osg-3rdparty-cmake is tailored for OSG dependencies with structured output and Windows prebuilts, while vcpkg is a general package manager with broader library support and automation. For OSG-specific builds on Windows, osg-3rdparty-cmake can be more straightforward.

How to add a new dependency not listed in osg-3rdparty-cmake?

You would need to create custom CMake scripts or integrate another build system, as osg-3rdparty-cmake only supports the predefined set of libraries. This limits flexibility for projects requiring additional components.

Is osg-3rdparty-cmake suitable for continuous integration pipelines?

It can be used in CI with CMake, but the manual source downloads add complexity. For automated builds, consider scripting the download steps or using alternatives with better dependency management.

Open-Awesome

osg-3rdparty-cmake

UnlicenseCMakev1.0

CMake scripts for building OpenSceneGraph third-party libraries from source.

GitHub

199 stars109 forks0 contributors

What is osg-3rdparty-cmake?

osg-3rdparty-cmake is a collection of CMake scripts designed to build third-party libraries needed for OpenSceneGraph, a high-performance 3D graphics toolkit. It automates the compilation of dependencies like zlib, libpng, and libjpeg from source, ensuring they are correctly configured for use with OpenSceneGraph projects. This solves the problem of manually building and integrating these libraries, which can be error-prone and time-consuming.

Target Audience

Developers working with OpenSceneGraph who need to build its dependencies from source, particularly those using Visual Studio on Windows. It is also useful for system integrators or build engineers setting up OpenSceneGraph environments.

Value Proposition

Developers choose osg-3rdparty-cmake because it provides a standardized, CMake-based method to build OpenSceneGraph dependencies, reducing configuration errors and saving time. Its support for prebuilt binaries and flexible source management makes it a practical alternative to manual compilation or platform-specific build scripts.

Overview

CMake scripts for building OpenSceneGraph third party libraries.

Use Cases

Best For

Building OpenSceneGraph dependencies from source on Windows
Setting up a consistent development environment for OpenSceneGraph projects
Automating the compilation of third-party graphics libraries
Integrating libraries like zlib, libpng, and libjpeg with CMake
Generating Visual Studio solutions for OpenSceneGraph third-party libraries
Managing dependencies for cross-platform 3D graphics applications

Not Ideal For

Projects on Linux or macOS that rely on system package managers like apt or Homebrew for dependencies
Developers who want fully automated dependency resolution without manual source downloads, such as those using vcpkg or Conan
Teams working with non-OpenSceneGraph graphics libraries, as this tool is specifically tailored for OSG's dependency set

Pros & Cons

Pros

CMake Integration

Uses CMake to generate platform-specific project files, reducing configuration errors and ensuring compatibility with OpenSceneGraph, as outlined in the instructions.

Prebuilt Library Support

Offers precompiled binary archives for Visual Studio 2017 and 2019, speeding up setup by avoiding source compilation for common Windows toolchains.

Organized Output Structure

Automatically organizes built libraries and headers into a standardized 3rdParty folder with platform subdirectories, simplifying integration into OpenSceneGraph projects.

Flexible Source Management

Allows selective building by specifying custom source locations for each dependency, enabling builds from different versions or patches as per user needs.

Cons

Limited Prebuilt Platform Support

Prebuilt binaries are only available for Windows with specific Visual Studio versions, requiring full manual compilation for other platforms or compilers.

Manual Dependency Sourcing

Users must download each library's source code separately from external sites, adding steps and potential for errors in the build process.

Fixed Dependency List

Only supports a predefined set of libraries; if OpenSceneGraph requires additional dependencies, they must be handled outside this system.

Frequently Asked Questions

Related Projects

suitesparse-metis-for-windows

CMake scripts for painless usage of SuiteSparse+METIS from Visual Studio and the rest of Windows/Linux/OSX IDEs supported by CMake

Stars467

Forks222

Last commit2 years ago

cmake-language-server

CMake LSP Implementation

Stars405

Forks41

Last commit1 year ago

autovala

A program that automatically generates CMake and Meson configuration files for your Vala project

Stars105

Forks15

Last commit7 years ago

cmake-lint

Check for coding style issues in CMake files

Stars104