Mailing-List: contact dev-help@openoffice.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openoffice.apache.org
MIME-Version: 1.0
In-Reply-To: <528C9695.3020009@googlemail.com>
References: 
 <CAGj32160a+ioe2X96=OOX0jqC+wfup7+e+nKuLmPN_ZKKa0=2g@mail.gmail.com>
	<528C65C0.6020901@apache.org>
	<528C70B9.2000702@googlemail.com>
	<528C78E2.1090209@apache.org>
	<528C9695.3020009@googlemail.com>
Date: Wed, 20 Nov 2013 12:26:51 +0100
Message-ID: 
 <CAK2iWdSF9gyFCc1_Ye+V0-xUON5hrcq_uVZMGMz_zar+=uCdBQ@mail.gmail.com>
Subject: Re: many many stlport issues...can anyone help
From: jan i <jani@apache.org>
To: dev <dev@openoffice.apache.org>
Content-Type: multipart/alternative; boundary=089e0103ec24b99dd704eb9a0e90

--089e0103ec24b99dd704eb9a0e90
Content-Type: text/plain; charset=ISO-8859-1

On 20 November 2013 12:01, Andre Fischer <awf.aoo@gmail.com> wrote:

> On 20.11.2013 09:54, Herbert Duerr wrote:
>
>> On 20.11.2013 09:20, Andre Fischer wrote:
>>
>>> On 20.11.2013 08:33, Herbert Duerr wrote:
>>>
>>>>
>>>> Please use the --without-stlport configure switch.
>>>>
>>>> This option is the new default. Thanks to Jan for fixing configure.in.
>>>> But you'd need to update to the newest trunk version to benefit from
>>>> Jan's fix.
>>>>
>>>>
>>> Is there any reason why we still need this option (be it default or
>>> not)?
>>>
>>
>> If there is a choice between step-wise evolution and a big-bang change
>> I'd always prefer the step-wise evolution.
>>
>
> I agree.  But I would like steps that go from valid state to valid state.
>  From what I have heard I had the impression that the --without-stlport
> option had only one valid value left and that using --with-stlport would
> break the build.
>
>
>>   Is there any scenario where we would need that switch to turn on
>>> support for stlport?
>>>
>>
>> A developer reusing the latest recipes from our snapshots page would fail
>> with the latest trunk if the --without-stlport option was no longer
>> recognized.
>>
>
> Would it not be better to update the recipes?
>
> I would assume that removing the configure option and adapting the build
> recipes take just a couple of hours to do.  Would it not be better to spend
> this additional time and make the change of removing support for stlport
> complete in one step?
>

with my  change to configure.in, you can choose to use --without-stlport or
not it has he same effect, meaning developers do not need to change
configure options.

rgds
jan I.


> -Andre
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
>

--089e0103ec24b99dd704eb9a0e90--