On 16 December 2014 at 11:27, Jose Fonseca wrote:
> On 15/12/14 19:47, Emil Velikov wrote:
>>
>> On 15/12/14 12:19, Jose Fonseca wrote:
>>>
>>> From: José Fonseca
>>>
>>> Instead of just MSVC builds.
>>>
>>> Because pkg-config is not commonly available when compiling natively on
>>> Windows, and
On 15/12/14 19:47, Emil Velikov wrote:
On 15/12/14 12:19, Jose Fonseca wrote:
From: José Fonseca
Instead of just MSVC builds.
Because pkg-config is not commonly available when compiling natively on
Windows, and gives the wrong results (the host package instead of target
package) when cross-co
On 15/12/14 20:09, Jose Fonseca wrote:
> On 15/12/14 19:47, Emil Velikov wrote:
>> On 15/12/14 12:19, Jose Fonseca wrote:
>>> From: José Fonseca
>>>
>>> Instead of just MSVC builds.
>>>
>>> Because pkg-config is not commonly available when compiling natively on
>>> Windows, and gives the wrong res
On 15/12/14 19:47, Emil Velikov wrote:
On 15/12/14 12:19, Jose Fonseca wrote:
From: José Fonseca
Instead of just MSVC builds.
Because pkg-config is not commonly available when compiling natively on
Windows, and gives the wrong results (the host package instead of target
package) when cross-co
On 15/12/14 12:19, Jose Fonseca wrote:
> From: José Fonseca
>
> Instead of just MSVC builds.
>
> Because pkg-config is not commonly available when compiling natively on
> Windows, and gives the wrong results (the host package instead of target
> package) when cross-compiling to Windows.
Short ve
From: José Fonseca
Instead of just MSVC builds.
Because pkg-config is not commonly available when compiling natively on
Windows, and gives the wrong results (the host package instead of target
package) when cross-compiling to Windows.
---
CMakeLists.txt | 2 +-
1 file changed, 1 insertion(+), 1
