Re: [Piglit] [PATCH 2/4] cmake: Don't rely on pkg-config for all Windows builds.

2014-12-21 Thread Emil Velikov
On 16 December 2014 at 11:27, Jose Fonseca jfons...@vmware.com wrote:
 On 15/12/14 19:47, Emil Velikov wrote:

 On 15/12/14 12:19, Jose Fonseca wrote:

 From: José Fonseca jfons...@vmware.com

 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 version:
 Also might be worth checking Dylan's fixes (touching both waffle and
 piglit). And then build on top if needed.


 Yes, Dylan's changes eliminate the need of most of these.

 But I'm pushing this series as is for now, so I can upgrade all my
 build/test slave machines to start using waffle on Windows.

Since those are in, and it all works atm, can we look into the problem
and fix it properly ?
Pasting/attaching your logs  config would be nice start.

Meanwhile I gave it another try - both PKGBUILD (cross compilation
using mingw-w64) and the documentation (MSVC on top of Win7) work like
a charm.

Thanks
-Emil

P.S. Please post/report bugs with Waffle WGL as soon as you see them,
I would prefer if we can avoid pushing nasty hacks as the above.
___
Piglit mailing list
Piglit@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/piglit


Re: [Piglit] [PATCH 2/4] cmake: Don't rely on pkg-config for all Windows builds.

2014-12-16 Thread Jose Fonseca

On 15/12/14 19:47, Emil Velikov wrote:

On 15/12/14 12:19, Jose Fonseca wrote:

From: José Fonseca jfons...@vmware.com

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 version:
Also might be worth checking Dylan's fixes (touching both waffle and
piglit). And then build on top if needed.


Yes, Dylan's changes eliminate the need of most of these.

But I'm pushing this series as is for now, so I can upgrade all my 
build/test slave machines to start using waffle on Windows.


Jose


___
Piglit mailing list
Piglit@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/piglit


Re: [Piglit] [PATCH 2/4] cmake: Don't rely on pkg-config for all Windows builds.

2014-12-15 Thread Emil Velikov
On 15/12/14 12:19, Jose Fonseca wrote:
 From: José Fonseca jfons...@vmware.com
 
 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 version:
Also might be worth checking Dylan's fixes (touching both waffle and
piglit). And then build on top if needed.


Longer version:
Don't know about native non-msvc builds, but cygwin had pkg-config which
was working fine. I've not tried waffle or piglit with cygwin.

The cross-compiling issue is likely to be caused by
something/miss-configured in your toolchain file. Take a look/install
the mingw-w64-cmake [1].


Cheers,
Emil

[1] https://aur.archlinux.org/packages/mingw-w64-cmake/

___
Piglit mailing list
Piglit@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/piglit


Re: [Piglit] [PATCH 2/4] cmake: Don't rely on pkg-config for all Windows builds.

2014-12-15 Thread Jose Fonseca

On 15/12/14 19:47, Emil Velikov wrote:

On 15/12/14 12:19, Jose Fonseca wrote:

From: José Fonseca jfons...@vmware.com

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 version:
Also might be worth checking Dylan's fixes (touching both waffle and
piglit). And then build on top if needed.


Longer version:
Don't know about native non-msvc builds, but cygwin had pkg-config which
was working fine. I've not tried waffle or piglit with cygwin.

The cross-compiling issue is likely to be caused by
something/miss-configured in your toolchain file. Take a look/install
the mingw-w64-cmake [1].


Cheers,
Emil

[1] 
https://urldefense.proofpoint.com/v2/url?u=https-3A__aur.archlinux.org_packages_mingw-2Dw64-2Dcmake_d=AAIDaQc=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEsr=zfmBZnnVGHeYde45pMKNnVyzeaZbdIqVLprmZCM2zzEm=jZIn8FKasi0habXCHbsoRS823LO0ZFGCba4GIDrlUBws=uISto3_loppZ5FFgWi7vZfrdad1Vlw1IiRXRCruxjMoe=




I did but it couldn't make it work for me.  pkg-config insists on 
picking the system's waffle-1.pc somehow.


Does this actually work for you?

Jose
___
Piglit mailing list
Piglit@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/piglit


Re: [Piglit] [PATCH 2/4] cmake: Don't rely on pkg-config for all Windows builds.

2014-12-15 Thread Emil Velikov
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 jfons...@vmware.com

 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 version:
 Also might be worth checking Dylan's fixes (touching both waffle and
 piglit). And then build on top if needed.


 Longer version:
 Don't know about native non-msvc builds, but cygwin had pkg-config which
 was working fine. I've not tried waffle or piglit with cygwin.

 The cross-compiling issue is likely to be caused by
 something/miss-configured in your toolchain file. Take a look/install
 the mingw-w64-cmake [1].


 Cheers,
 Emil

 [1]
 https://urldefense.proofpoint.com/v2/url?u=https-3A__aur.archlinux.org_packages_mingw-2Dw64-2Dcmake_d=AAIDaQc=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEsr=zfmBZnnVGHeYde45pMKNnVyzeaZbdIqVLprmZCM2zzEm=jZIn8FKasi0habXCHbsoRS823LO0ZFGCba4GIDrlUBws=uISto3_loppZ5FFgWi7vZfrdad1Vlw1IiRXRCruxjMoe=


 
 
 I did but it couldn't make it work for me.  pkg-config insists on
 picking the system's waffle-1.pc somehow.
 
 Does this actually work for you?
 
Yes it did. I recall having two successful cross-builds of the whole of
piglit around the time of the GSoC midterm. One with glut and another
one with waffle.

Things may have changed since then, but I'll check within the next
couple of days.


-Emil

___
Piglit mailing list
Piglit@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/piglit