Perhaps I've chimed in too soon. I haven't used the most recent
version of the plugin, so I was assuming the Xcode project was being
modified.
Unfortunately, there are a few shops which haven't made a 100%
commitment to Eclipse/WOLips, and still have to keep an unmodified
Xcode project around.
If there comes a day that the Xcode project will be modified by the
WOLips plugin, please also allow the user to opt out.
Thanks.
_ _
Ian
On Sep 16, 2005, at 11:04 AM, Anjo Krank wrote:
> What feature?
>
> The last time I checked, the incremental builder did exactly
> nothing with the xcode files. Only the ant builder *may* do this if
> there is an xcodeindex task in there.
>
> Has this changed?
>
> Am 16.09.2005 um 19:21 schrieb Ian McDougall:
>
>
>> I'd like to put another vote in for this feature.
>> _ _
>> Ian
>>
>> On Sep 16, 2005, at 9:37 AM, Sébastien Sahuc wrote:
>>
>>
>>
>>> Hey there,
>>>
>>> While playing with WOLisp plugin HEAD with Eclipse 3.1.1 I
>>> noticed that I couldn't build again/run again with XCode because
>>> most of the XCode project have been modified while working with
>>> WOLisp in Eclipse. Is there any way to prevent that (through
>>> properties for example) ?
>>>
>>> This is critical in our environment because we'd like to have
>>> the two build system {Ant;woproject;WOLips;Eclipse} vs {shell
>>> scripts;xcode} working together while doing the transition. And
>>> since we don't need WOLisp to update XCode projects at all, we'd
>>> like to see WOLisp NOT touching those files.
>>>
>>> Thanks,
>>>
>>> Sebastien
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>
>
This archive was generated by hypermail 2.0.0 : Fri Sep 16 2005 - 16:43:20 EDT