Dan Nicholson wrote:
> On Thu, Aug 13, 2009 at 7:10 PM, tom fogal<tfo...@alumni.unh.edu> wrote:
>> Brian Paul <bri...@vmware.com> writes:
>>> tom fogal wrote:
>>>> Is there interest in bumping [the MAX_WIDTH/HEIGHT] limit up?  Are
>>>> there issues we're not considering when we do this?
>>>>
>>>> Perhaps we could have [...] a --with-max-width=16384 [which] could
>>>> accomodate our case without inflating the standard buffer sizes.
>>> I should add this to the FAQ because I answer it every 6 months or
>>> so...
>> [snip]
>>> I'd be OK with modifying config.h to read:
>>>
>>> #ifndef MAX_WIDTH
>>> #define MAX_WIDTH 4096
>>> #endif
>>>
>>> Then allowing a config option like --with-max-width=16384 which
>>> defines MAX_WIDTH, MAX_HEIGHT.  Feel free to submit a patch.
>> Sure.  3 patches attached.
>>
>>  1. aforementioned define change
>>  2. autoconf changes as described here + warning
>>  3. FAQ entry for this.
>>
>> They apply cleanly to both master and mesa_7_5_branch.
> 
> For the autoconf patch, the custom has been to put macros into the
> DEFINES variable. Otherwise, looks good.

I've made that change and committed the patches.

-Brian


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Mesa3d-dev mailing list
Mesa3d-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev

Reply via email to