Re: compilation problems on Windows

Alex <[email protected]>
Newsgroups gmane.comp.video.mesa3d.user
Message-ID <[email protected]>
I am not Brian, but I tried compiling it too from the link you gave and got
a compilation error in src\gallium\include\pipe/p_compiler.h telling that
stdbool.h is not found.

On Mon, Apr 25, 2011 at 8:09 PM, Brian Paul <[email protected]> wrote:

> On 04/22/2011 10:27 AM, K M wrote:
>
>> Hi,
>>
>> It is possible to build Mesa 7.9 or or newer on Windows?  The VS
>> solution files want to compile files that do not exist.  The current
>> compilation instructions at mesa3d.org <http://mesa3d.org> say to use
>> SCons, but it looks like the tarballs are missing some files needed to
>> do this.
>>
>> I grabbed the repository code for the 7.10.2 tag and the 7.10 branch.
>> Both of these had some additional files needed for SCons, but the
>> build process for both of them would fail to create an opengl32.dll,
>> giving a link error.
>>
>
> What exactly was the error?
>
>
>  I also grabbed the mainline code from the repository.  Running SCons,
>> I am able to build both a 32bit and 64bit Windows opengl32.dll,
>> glut32.dll, libEGL.dll, libOpenVG.dll, and graw.dll libraries.
>> However, it does not build a glu32.dll or a osmesa32.dll like Mesa 7.8
>> does.
>>
>
> I think Jose fixed that over the weekend.
>
>
>  Is this the current state of affairs due to the transition to using
>> SCons instead of VS?
>>
>
> I fixed the problem w/ missing scons files in the tarballs for the next
> release.  You can try some test .zip files in
> ftp://ftp.freedesktop.org/pub/mesa/tmp/
>
> -Brian
> _______________________________________________
> mesa-users mailing list
> [email protected]
> http://lists.freedesktop.org/mailman/listinfo/mesa-users
>

_______________________________________________
mesa-users mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/mesa-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.