[vcpkg] create pkg-config files

[isanych]

When I was building non vcpkg Qt using vcpkg dependencies, I was struggling until I created pkg-config files for vcpkg libs, so I decided to automate this process. Change should not affect cmake usage of vcpkg, but help to use vcpkg created libs as non cmake dependencies. As a side effect port version could be used in cmake files, one place less to change during version change process.

vcpkg_pkgconfig cmake function generates pkgconfig file, next cmake variables added:
PORT_FULL_VERSION - Version from CONTROL file
PORT_VERSION - PORT_FULL_VERSION without vcpkg version suffix
PORT_CMAKE_VERSION - cmake compatible version, 4 version components max, numbers only
PORT_DESCRIPTION - Description from CONTROL file
PORT_HOMEPAGE - Homepage from CONTROL file
PORT_DEPENDENCIES - list of port dependencies

Closes #7162

[MVoz]

)) windows?

[isanych]

)) windows?

I'm not sure if pkgconfig files are needed on windows, removing 3 lines here -

vcpkg/scripts/cmake/vcpkg_pkgconfig.cmake

Line 49 in 8a79337

if(CMAKE_HOST_WIN32)

will create them on windows too

[MVoz]

I'm not sure if pkgconfig files are needed on windows

meson works tight with pkgconfig

[isanych]

I'm not sure if pkgconfig files are needed on windows

meson works tight with pkgconfig

ok, removed windows check - should work on windows too now

[MVoz]

@isanych Игорь, верните, пока vcpkg для виндовс не работает с pkgconfig. я спросил про запас, так сказать на будущее
но вот для примера проект по сборке GTK
https://github.com/wingtk/gvsbuild

там плотно meson + pkgconfig связаны

[cbezault]

Closes #7162

[PhoebeHui]

@isanych, Is work still being done for this PR? Could you please resolve the conflicts?

[isanych]

@PhoebeHui, ok I'll give it another go - last time build server was failing without obvious reason for me - so I'm just using own branch, but it would be nice to have less differences with upstream

[isanych]

/azp run

[azure-pipelines]

Commenter does not have sufficient privileges for PR 7129 in repo microsoft/vcpkg

[PhoebeHui]

@isanych, I test the changes locally, and it failed with following failure, it looks a vcpkg bug in this change:

PS F:\vcpkg\7129\vcpkg> ./vcpkg install libmediainfo
Your feedback is important to improve Vcpkg! Please take 3 minutes to complete our survey by running: vcpkg contact --survey
Computing installation plan...
The following packages will be built and installed:

• curl[core,non-http,ssl,sspi,winssl]:x86-windows
  libmediainfo[core]:x86-windows
• libzen[core]:x86-windows
• zlib[core]:x86-windows
  Additional packages (*) will be modified to complete this operation.
  Starting package 1/4: zlib:x86-windows
  Building package zlib[core]:x86-windows...
  CMake Error at scripts/ports.cmake:47 (message):
  Unsupported target triplet. Triplet file does not exist:
  F:vcpkg7129vcpkgtripletsx86-windows.cmake

[isanych]

@PhoebeHui, thank you - I see the issue, I'm passing description (beside other variables) to cmake - blosc has backticks there which was causing shell attempt to execute sting between them - so I've removed dangerous characters, but went too far there as I've done that for all cmake variables - will do it for description field only

[cbezault]

If you truly want a full-rebuild modifying the vcpkg_fixup_cmake_targets.cmake file will do it. See 4dd67c2.

[isanych]

@cbezault full rebuild helped thank you
@PhoebeHui issues which supposed to be gone are gone now, from latest failures I could only reproduce llvm on windows and parallelstl , but they are failing on master too, not sure what are my next steps should be

[PhoebeHui]

The failures doesn't related to this change, @isanych, could you also update the Version in CONTROL file in related ports?

I will ask team member help to do feature review.

[PhoebeHui]

@isanych, could you please resolve the conflicts?

@strega-nil, could you help review this feature?

[PhoebeHui]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[PhoebeHui]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).