Installed SDK on custom directory, but it still includes headers from `/usr/include` , why ? | Vulkan API Discord | Page 1

rigid canopy Jun 14, 2024, 6:04 PM

#

after reboot, terminal sees those variables , those are correct variables I think I followed docs

sage patio Jun 14, 2024, 6:04 PM

#

How are you building the project?

rigid canopy Jun 14, 2024, 6:04 PM

#

with vscode/cmake

sage patio Jun 14, 2024, 6:04 PM

#

post code

#

/usr/include is a default search path for include files, and so if you are using find_package(Vulkan) it may be picking them up from there.

rigid canopy Jun 14, 2024, 6:05 PM

#

cmake_minimum_required(VERSION 3.29)
project(TEST1 VERSION 0.1.0 LANGUAGES C CXX)

find_package(Vulkan REQUIRED)

add_executable(Main "main.cpp")
target_link_libraries(Main PRIVATE Vulkan::Vulkan)```

#

as simple as that

#

then what's the point of include dirs of SDK if it will read from usr/include anyway

sage patio Jun 14, 2024, 6:06 PM

#

im not sure what you mean

rigid canopy Jun 14, 2024, 6:06 PM

#

should I set include variable there in /etc/enviroment too ?

#

I want headers from sdk directory not from /usr/include

sage patio Jun 14, 2024, 6:07 PM

#

Okay, did you clean out your cache before re-runnning cmake?

rigid canopy Jun 14, 2024, 6:07 PM

#

yes 10 times

#

it sees correct paths by the way

#

take a look a sec

sage patio Jun 14, 2024, 6:07 PM

#

and you are sure VULKAN_SDK is set in the environment you are running cmake in?

rigid canopy Jun 14, 2024, 6:08 PM

#

will check that , with $ENV .. a sec

#

message("TEST: " $ENV{VULKAN_SDK})

#

correct ?

sage patio Jun 14, 2024, 6:08 PM

#

yeah

rigid canopy Jun 14, 2024, 6:08 PM

#

sage patio Jun 14, 2024, 6:08 PM

#

well thats good

rigid canopy Jun 14, 2024, 6:08 PM

#

here is print

#

PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/mnt/b1b56d51-33ac-4613-a905-03b004de143d/VulkanSDK/1.3.283.0/x86_64/bin"
VULKAN_SDK="/mnt/b1b56d51-33ac-4613-a905-03b004de143d/VulkanSDK/1.3.283.0/x86_64"
LD_LIBRARY_PATH="/mnt/b1b56d51-33ac-4613-a905-03b004de143d/VulkanSDK/1.3.283.0/x86_64/lib"
VK_LAYER_PATH="/mnt/b1b56d51-33ac-4613-a905-03b004de143d/VulkanSDK/1.3.283.0/x86_64/share/vulkan/explicit_layer.d"
VK_ADD_LAYER_PATH="/mnt/b1b56d51-33ac-4613-a905-03b004de143d/VulkanSDK/1.3.283.0/x86_64/share/vulkan/explicit_layer.d"```

#

here I just don't see INCLUDE dir variable

#

shoudn't it be there ?

sage patio Jun 14, 2024, 6:09 PM

#

FYI you do have /usr/<bin> in your path ahead of the VULKAN_SDK path

sage patio Jun 14, 2024, 6:10 PM

#

rigid canopy ```json PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/...

There isn't one - cmake uses the VULKAN_SDK in how it searches for paths.

#

the source code is here https://github.com/Kitware/CMake/blob/master/Modules/FindVulkan.cmake

#

can you post your full cmake configure log?

rigid canopy Jun 14, 2024, 6:11 PM

#

yes I have /mnt/b1b56d51-33ac-4613-a905-03b004de143d/VulkanSDK/1.3.283.0/x86_64/bin bin here so when I'm doing find_package() it will search include dirs from what's written in FindVulkan.cmake right ?

#

where can I find that log ?

#

will post ofc

sage patio Jun 14, 2024, 6:12 PM

#

yes, in a general sense (it doesn't use /bin directly in the FindVulkan.cmake, it just uses VULKAN_SDK/include)

#

uhhhh generally in your build folder

rigid canopy Jun 14, 2024, 6:12 PM

#

ninja_log ?

#

#

this is build dir

rigid canopy Jun 14, 2024, 6:13 PM

#

sage patio yes, in a general sense (it doesn't use /bin directly in the FindVulkan.cmake, i...

if it uses VULKAN_SDK/include then something wrong here cuz VULKAN_SDK is pointing to mounted partition correctly where I have SDK

sage patio Jun 14, 2024, 6:14 PM

#

It'll be in the CMakeFiles then

rigid canopy Jun 14, 2024, 6:14 PM

#

#

which one ?

sage patio Jun 14, 2024, 6:14 PM

#

ninja_log isn't useful, thats after you configured cmake. CMakeCache.txt would be useful

rigid canopy Jun 14, 2024, 6:15 PM

#

📎 CMakeCache.txt

#

this is from build dir

#

and I cleaned that really many times

sage patio Jun 14, 2024, 6:15 PM

#

well your cache says you have the right include path

//Path to a file.
Vulkan_INCLUDE_DIR:PATH=/mnt/b1b56d51-33ac-4613-a905-03b004de143d/VulkanSDK/1.3.283.0/x86_64/include

rigid canopy Jun 14, 2024, 6:16 PM

#

correct , I knew that by printing that variable after find_package populates vartiables

#

what's the issue ? 😦

#

sage patio Jun 14, 2024, 6:16 PM

#

okay I do not see the log from cmake where I thought I would.

rigid canopy Jun 14, 2024, 6:16 PM

#

included from /usr/include

sage patio Jun 14, 2024, 6:17 PM

#

Oh how are you "getting" to vulkan.h? Just hitting f12?

rigid canopy Jun 14, 2024, 6:17 PM

#

ctrl mouse click

#

or I'm just opening in explorer the header included

sage patio Jun 14, 2024, 6:17 PM

#

you might be getting what "intellisense" is using rather than what the compiler is getting

#

if you delete your cache and reconfigure, the 'log' is printed to the vscode console. can you copy that?

rigid canopy Jun 14, 2024, 6:18 PM

#

another very strange thing what happens here , maybe that will be hint on what's going on

#

it sees vulkan includes even without clean project

#

not need to ask for vulkan

south saddle Jun 14, 2024, 6:18 PM

#

are you using the vs code cmake plugin?

rigid canopy Jun 14, 2024, 6:19 PM

#

yes

#

#

#

maybe switch to release version ?

south saddle Jun 14, 2024, 6:19 PM

#

Do you have a "c_cpp_properties.json" in your project?

#

That might override the include directories

rigid canopy Jun 14, 2024, 6:20 PM

#

no I don't

#

south saddle Jun 14, 2024, 6:20 PM

#

also check for a settings.json

#

they're usually in the (sometimes hidden) .vscode folder

rigid canopy Jun 14, 2024, 6:20 PM

#

I don't havethem too , I don't have .vscode dir there at all

fast walrus Jun 14, 2024, 6:20 PM

#

intelisense is provided by a separate plugin, that plugin did not use the cmake plugin to detect the paths

rigid canopy Jun 14, 2024, 6:21 PM

#

#include <vulkan/vulkan.h> is possbile without find_package(Vulkan REQUIRED)

#

how ?

sage patio Jun 14, 2024, 6:21 PM

#

I see that compile_commands.json was generated, which is a good sign

rigid canopy Jun 14, 2024, 6:21 PM

#

think that is intellisense ?

sage patio Jun 14, 2024, 6:21 PM

#

rigid canopy `#include <vulkan/vulkan.h>` is possbile without `find_package(Vulkan REQUIRED)`

because its in /usr/include, a default search path

#

I think so - I sometimes am bit by intellisense and cmake not matching

fast walrus Jun 14, 2024, 6:22 PM

#

compile_commands.json is a clangd file so it would only work with clangd intelisense not the standard cpp intelisense from microsoft

rigid canopy Jun 14, 2024, 6:22 PM

#

sage patio I think so - I sometimes am bit by intellisense and cmake not matching

I woudn't be able to include vulkan like that yesterday

#

you can't just #include <vulkan/vulkan.h>

#

in empty project, but now I can ..

sage patio Jun 14, 2024, 6:22 PM

#

fast walrus compile_commands.json is a clangd file so it would only work with clangd intelis...

really? damn

fast walrus Jun 14, 2024, 6:22 PM

#

I mean afaik 😂

south saddle Jun 14, 2024, 6:23 PM

#

If you can include in a new empty project, you probably have a global include path settings (file) setup

rigid canopy Jun 14, 2024, 6:24 PM

#

which I didn't craete, in other words something happened and now I can't get to default state 😦 ...

sage patio Jun 14, 2024, 6:24 PM

#

fast walrus I mean afaik 😂

No, this documentation indicates intellisense can use compile_commands.json

#

https://code.visualstudio.com/docs/cpp/configure-intellisense#_project-level-intellisense-configuration

fast walrus Jun 14, 2024, 6:24 PM

#

ohhhhh

south saddle Jun 14, 2024, 6:25 PM

#

Can you check the C_Cpp.default.includePath setting in vscode?

rigid canopy Jun 14, 2024, 6:25 PM

#

ofc , a sec

south saddle Jun 14, 2024, 6:25 PM

#

you migth have setup include paths for your user

fast walrus Jun 14, 2024, 6:26 PM

#

@rigid canopy

A custom configuration provider is another extension in VS Code that can potentially provide more accurate C++ IntelliSense configuration than the C/C++ extension.

To add an extension as a configuration provider, either select the extension through the configuration Quick Pick, add it to configuration UI by editing the Configuration provider field under Advanced Settings, or add the configurationProvider field to your c_cpp_properties.json file. For example, for the CMake extension, the path to add would be ms-vscode.cmake-tools.

rigid canopy Jun 14, 2024, 6:26 PM

#

#

nope

south saddle Jun 14, 2024, 6:27 PM

#

And C_Cpp.default.systemIncludePath ?

rigid canopy Jun 14, 2024, 6:28 PM

#

#

nope

#

cmake_minimum_required(VERSION 3.29)
project(TEST2 VERSION 0.1.0 LANGUAGES C CXX)

add_executable(TEST2 main.cpp)
``` clean project new directory

#

#

😄

#

but not funny .. it's easier to set off the rocket I guess

#

I have cockroach entry somewhere that refuses to wipe itself from list

#

I didn't included anything .. really

#

that started after I added variables

#

and I'm also able to create VkInstance

#

    VkInstance i{};

sage patio Jun 14, 2024, 6:34 PM

#

what

rigid canopy Jun 14, 2024, 6:34 PM

#

afaik I need a libs for that ... no ?

sage patio Jun 14, 2024, 6:34 PM

#

no

#

all you did was declare a pointer

#

creating an instance requires calling vkCreateInstance, otherwise its not different than Foo* foo {};

rigid canopy Jun 14, 2024, 6:35 PM

#

hmm ok got that .. anyway thanks for help . will dig further dunno what's the binary evil is going on here 🙂

#

    VkApplicationInfo AppInfo{};
    AppInfo.apiVersion = VK_API_VERSION_1_3;```

#

that isn't pointer but possbile too

sage patio Jun 14, 2024, 6:37 PM

#

yeah, VkApplicationInfo is just a struct

#

and VkInstance is a 'dispatchable handle' which akin to a uint64_t value (but it is a pointer, just to an opaque type)

#

When you say "create an instance" you are meaning "creating a Vulkan Instance Object" which requires calling Vulkan API calls which perform the necessary internal logic to create an instance. You get access to that instance from the VkInstance handle that is returned from vkCreateInstance (well, out parameter). Hence why you can't just create an instance with VkInstance instance{};

rigid canopy Jun 14, 2024, 6:40 PM

#

yes I was not be able to pass this ```cpp
VkInstance I;

int main(int, char**)
{

VkInstance i{};
VkApplicationInfo AppInfo{};
AppInfo.sType = VK_STRUCTURE_TYPE_APPLICATION_INFO;
AppInfo.apiVersion = VK_API_VERSION_1_3;

VkInstanceCreateInfo InstanceC{};
InstanceC.sType = VK_STRUCTURE_TYPE_INSTANCE_CREATE_INFO;
InstanceC.pApplicationInfo = &AppInfo;


auto x = vkCreateInstance(&InstanceC, nullptr, &I);
if (x != VK_SUCCESS)
{
    
}

}``` I just panicing maybe it also links the libs some hidden way 🙂

#

but looks like it only includes from somewhere ...

#Installed SDK on custom directory, but it still includes headers from `/usr/include` , why ?