[build][CMake] GFLW not linked when raylib declared as dependency for `vcpkg`

[batabutter]

Issue description

I created a standard build config using CMake and vcpkg using manifest mode, glfw was unable to link properly. It seems as so for some reason, glfw gets dropped during the creation of raylib-targets.cmake.

When using,

find_package(raylib CONFIG REQUIRED)
target_link_libraries(out PRIVATE raylib)

glfw does not get added into the linkage stage after calling cmake --build build, even though your system requires that external linkage, and it should propagate. I was able to fix this issue simply by adding

find_package(raylib CONFIG REQUIRED)
find_package(glfw3 CONFIG REQUIRED)
target_link_libraries(out PRIVATE raylib glfw)

This suggests something might be wrong with how glfw is specified to link during the creation of raylib-targets.cmake.

Environment

Platform: Linux
OS: Ubuntu
OpenGL: 4.5

Issue Screenshot

Code Example

Basic starter code:

#include <raylib.h>

const int SCREEN_WIDTH = 800;
const int SCREEN_HEIGHT = 800;
const int TARGET_FPS = 60;

int main() {

  InitWindow(SCREEN_WIDTH, SCREEN_HEIGHT, "QuadTree Visualizer");
  SetTargetFPS(TARGET_FPS);

  while(!WindowShouldClose()) {

    BeginDrawing();
    
    
    EndDrawing();
  }

  CloseWindow();

  return 0;
}

My Original CMakeLists.txt:

cmake_minimum_required(VERSION 3.28)

project(QuadTreeVisualizer)

set(CMAKE_CXX_STANDARD 23)
set(CMAKE_CXX_STANDARD_REQUIRED ON)
set(CMAKE_CXX_SCAN_FOR_MODULES ON)
set(CMAKE_EXPORT_COMPILE_COMMANDS ON)

find_package(raylib CONFIG REQUIRED)

add_executable(out src/main.cpp)

target_sources(out
  PRIVATE
  FILE_SET 
    utils TYPE CXX_MODULES 
    BASE_DIRS 
      utils
    FILES 
      utils/quadtree.cppm   
)

target_link_libraries(out PRIVATE raylib)

[raysan5]

@batabutter Are you using latest raylib from GitHubmaster branch?

[raysan5]

@Peter0x44 @manuel5975p @VictorHM @JohnnyCena123, @ninadsachania, @arodriguez22, @pamarcos, @SajendraN, @heliumsneakers, @nukelash, @RobLoach Please, could you take a look to this issue?

[batabutter]

@batabutter Are you using latest raylib from GitHubmaster branch?

Yes. I am using raylib 6.0. The linked repo is the latest.
https://vcpkg.io/en/package/raylib.html

[Peter0x44]

@batabutter Are you using latest raylib from GitHubmaster branch?

Yes. I am using raylib 6.0. The linked repo is the latest. https://vcpkg.io/en/package/raylib.html

He means the latest commit from the master branch. Not 6.0. 6.0 was unfortunately released with a broken cmake setup.

[Peter0x44]

Though the way it's broken shouldn't cause linker errors. So it could be something else.

[batabutter]

@batabutter Are you using latest raylib from GitHubmaster branch?

Yes. I am using raylib 6.0. The linked repo is the latest. https://vcpkg.io/en/package/raylib.html

He means the latest commit from the master branch. Not 6.0. 6.0 was unfortunately released with a broken cmake setup.

Looking at the listed available versions on vcpkg, it seems like the latest release is the only one that's available, which is not up to date with the latest commit. I tried searching through previous issues and didn't find anyone mentioning this, however if this bug no longer persists in the most recent version of this repo, we can go ahead and close the issue.

[raysan5]

@batabutter please, can you try latest raylib from master branch?

[raysan5]

Feel free to reopen if you test on latest raylib 6.1-dev from github master branch and issue persists