Hmm .. I'm using the latest and greatest build from my local version
(what would be 130 which isn't up on the site yet), and it seems to
be working fine for me. I can open EOModeler and it finds my
prototypes, and I can open Xcode from my .xcodeproj (.xcode tries to
upgrade, but it upgrades it to a file that appears to work fine?).
Oh, and this project has a .eogen file. There should be nothing
special about EOGenerator support. It literally is just a regular
file that just happens to have a file association. Are you building
from a local version or from the build server?
On May 20, 2006, at 10:53 AM, Pierre Frisch wrote:
> Any project that use the eogenerator feature appears to have a
> broken project file. When I try to open it it comes up with a
> project cannot be parsed message.
>
> I cannot see what is the cause but it appears to be the case or at
> least it is with the commits between the 15 and the 19th.
>
> This is a very annoying bug as without the Xcode project EOModeler
> will not load the Prototype model.
>
> Thanks
>
> Pierre
>
> On 19-May-06, at 11:06 AM, John Huss wrote:
>
>> I had the same problem.
>>
>> John
>>
>> On 5/19/06, Pierre Frisch <pierre.frisc..pearway.com> wrote:
>>> Am I the only one? The Xcode project is broken with the latest build
>>> (May 19 2006)
>>>
>>> Thanks
>>>
>>> Pierre
>>>
>>
>
This archive was generated by hypermail 2.0.0 : Sat May 20 2006 - 13:47:48 EDT