libigl / libigl/libigl

vcpkg libigl won't compile seamlessly with the vcpkg imgui integration

Open
#2,389 2 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

compilation
Dominant language
C++
Stars
5.1k
Forks
1.2k
Avg merge
7h 33m
Merged PRs (30d)
8

Description

Describe your issue

If you install libigl via vcpkg with imgui + opengl and also install imgui with glfw-binding, it can't find backends/imgui_impl_glfw.h.

vcpkg just installs this in the regular include path and doesn't need to be in the "backends" folder.

libigl should probably do it the vcpkg way and just use #include <imgui_impl_glfw.h> and include the backends folder directly for test projects.

Checklist
  • I have read the bug report page
  • CMake issue: I have tried with a fresh clone/empty build directory
Platform
  • Windows
  • macOS Intel
  • macOS Arm (e.g., M1, M2)
  • Linux

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating libigl's imgui/OpenGL integration includes and the test projects that use them, then compare them with the headers installed by vcpkg. Verify that a vcpkg installation of libigl with imgui, OpenGL, and the GLFW binding compiles successfully, including the test projects.

Written by the indexing model from the issue text.

Assessment

Tech stack
cmake, cpp
Domain
build-system
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.