The patches for msys are minor (and being merged). Check Qt-builds project
on sourceforge.
On 16 May 2013 22:49, "Bruno Souza Cabrral" <[email protected]> wrote:

> @andy,
> I'm building from "c:/q" and it far exceed the limit to be related to the
> folder path alone.
>
>
> @Ray ,
> I think that build from cmd is the recommended scenario for W32.
> MSYS is the other option, but it do not work without patches.
>
> On Thu, May 16, 2013 at 6:31 PM, andy fillebrown <
> [email protected]> wrote:
>
>> I don't build the WebKit module anymore, but when I did I made sure the
>> Qt source tree was in a directory with a very short name, like D:\Qt-5.1.0.
>>  That way the command line stays small enough to make it through the build.
>>
>> Cheers,
>> ~ andy.f
>>
>>
>>
>>
>>
>> On Thu, May 16, 2013 at 4:05 PM, Bruno Souza Cabrral <[email protected]>wrote:
>>
>>> Hello,
>>>
>>> For a while, I can't do any W32 builds with Webkit installed, because it
>>> hit a command-line limit and fails.
>>>
>>> The cmd in Windows have an 8191 characters limit where during the webkit
>>> build it far extrapolate this.
>>>
>>> Attached there is a example, where the gcc invocation contains 9890
>>> characters !
>>>
>>> This can be extremely frustrating because a build will randomly fail
>>> with a random cryptically message depending on the build env and the folder
>>> name.
>>>
>>> One solution I can see is moving the defines bundled in the gcc
>>> invocation to a header. But I can't see a easy way of doing this.
>>>
>>> Suggestions ?
>>>
>>> []'s
>>> Bruno
>>>
>>> _______________________________________________
>>> Development mailing list
>>> [email protected]
>>> http://lists.qt-project.org/mailman/listinfo/development
>>>
>>>
>>
>
> _______________________________________________
> Development mailing list
> [email protected]
> http://lists.qt-project.org/mailman/listinfo/development
>
>
_______________________________________________
Development mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/development

Reply via email to