Meson requires to set the root include dir by setting the INCLUDE env var

[nacho]

@guruDanny67 we should probably fix this problem otherwise the header files that are in the root dir will not be found.

[TingPing]

I haven't tried it personally, but maybe LIB and LIBPATH too?

A test would be:

project('foo', 'c')

cc = meson.get_compiler('c')
cc.find_library('something_in_libpath')

[guruDanny67]

Which projects can I use to test this ?

Thanks

[TingPing]

To test include:

project('foo', 'c')

cc = meson.get_compiler('c')
cc.has_header('libintl.h')

[guruDanny67]

Ok, you mean the gtk stack include dir (i.e. c:\gtk-build\gtk\win32\release\include) and the similar for libpath ?

[TingPing]

Yea.

[guruDanny67]

If I understand correctly (I'm at work now and I can't check deep) if the project use ONLY pkg-config to get the stuff it's ok (because LIBPATH and the include dir are added), while in these simple case we got an error.

We can add the enviroment globally in the script (or before, manually, to test things) or on a per-project basis, like the add_path keyword

[TingPing]

if the project use ONLY pkg-config to get the stuff it's ok (because LIBPATH and the include dir are added), while in these simple case we got an error.

Indeed.

I think it is safe to always set these variables and would avoid potential duplication.

[guruDanny67]

A fast solution will be to set (or add) INCLUDE, LIB and LIBPATH to the gtk ones just before initializing the vs environment (vcvarsall.bat): in this way the data are saved internally and any time we use the build_vs(...) we have it.