I did a more thorough investigation of all libraries used and available Conan packages:

Package	State	Proposed Package Reference
glm	Already packaged	glm/0.9.8.5@g-truc/stable
catch2	Already packaged	catch2/2.1.2@bincrafters/stable
GSL	Already packaged	gsl_microsoft/20180102@bincrafters/stable
GLFW	Already packaged	glfw/3.2.1@bincrafters/stable
cmcstl2	Created PR: CaseyCarter/cmcstl2#137	currently cmcstl2/5e8577e@mmha/stable, but should be changed once merged
stb	Tracked by issue: nothings/stb#566, apparently WIP: nothings/stb#555	N/A
gli	Not packaged yet	N/A

We should probably write a Conan recipe for gli, try to upstream it and wait until the work on the stb package is done. In the meantime, both could be just copied into the repository as a workaround.

When all dependencies are packaged, it is probably best to create a new Bintray repository and link all packages in. This simplifies the users work flow because they only need to add one remote at most and the README could be extended like this:

Getting Started

Install gcc >= 6.3, CMake >= 3.10, Conan >= 1.0. On Ubuntu, this works like this:

sudo add-apt-repository ppa:ubuntu-toolchain-r/test
sudo apt update
sudo apt install gcc-8 python3-pip
pip3 --user install conan cmake

Add the DOGE repository to your Conan remotes:

conan remote add doge https://api.bintray.com/conan/doge/conan

Add this to your CMakeLists:

    conan_cmake_run(REQUIRES doge/0.42@doge/stable
                    BASIC_SETUP CMAKE_TARGETS
                    BUILD missing)
    find_package(DOGE REQUIRED)
    target_link_libraries(app PRIVATE DOGE::doge)

Handle external dependencies without forcing the user to manually download everything #7

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions