Can't open project

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Steve Mills - 30 Aug 2004 20:42 GMT

I needed to do some work in OS9, so I synced our source on my old G3
while in OSX, and was going to rebuild our app. When attempting to open
the project in CW9, it gives me this error:

206004
Unable to open project. Directory could not be found.

*What* directory? I did a fixprecomps from the Terminal, and am now
rebuilding the MSL libraries and pch's. I even tried exporting the
project as xml from a machine that *can* open the project, then
importing that xml on the G3. Same error. This project opens on every
other machine we have, and they're all running the same version of CW.

The only thing I can think of is that for a while, I was developing a
compiler plugin, and that plugin's info was added to the project. But
that plugin only existed on one machine (my G5), and like I said, other
machines can open it even without that plugin present.

Any thoughts?

Signature

Steve Mills
Mac geek, drummer

Reply to this Message

MW Ron - 30 Aug 2004 22:01 GMT

>I needed to do some work in OS9, so I synced our source on my old G3
>while in OSX, and was going to rebuild our app. When attempting to open
>the project in CW9, it gives me this error:
>
>206004
>Unable to open project. Directory could not be found.

I've seen that happen when you have a multi target project and your
current target is an OS X target. It can't find the OS X frameworks

>*What* directory? I did a fixprecomps from the Terminal, and am now
>rebuilding the MSL libraries and pch's. I even tried exporting the
>project as xml from a machine that *can* open the project, then
>importing that xml on the G3. Same error. This project opens on every
>other machine we have, and they're all running the same version of CW.

Try changing the open target from Mach-O to classic.

You also have to show CW where the Frameworks are on classic, you might
have to set the OS X Volume.

>The only thing I can think of is that for a while, I was developing a
>compiler plugin, and that plugin's info was added to the project. But
>that plugin only existed on one machine (my G5), and like I said, other
>machines can open it even without that plugin present.
>
>Any thoughts?

Try setting the OS X Volume and then see if it opens. If not change it
to a classic target, although I'm not sure that always works.

Hope this helps,

Ron

Signature

Metrowerks Community Forum is a free online resource for developers
to discuss CodeWarrior topics with other users and Metrowerks' staff
-- http://www.metrowerks.com/community --

Ron Liechty - MWRon@metrowerks.com - http://www.metrowerks.com

Reply to this Message

Steve Mills - 30 Aug 2004 23:07 GMT

I think the project I'm trying to open (Carbon app that builds a
packaged app) is OK, but maybe one of the subprojects (OSX framework) is
causing the error.

>Try changing the open target from Mach-O to classic.

I'm not sure what you're talking about here. You mean which linker the
target uses?

>You also have to show CW where the Frameworks are on classic, you might
>have to set the OS X Volume.

I'm trying to open the project in OSX, not 9.

>Try setting the OS X Volume and then see if it opens. If not change it
>to a classic target, although I'm not sure that always works.

If you mean to add a source tree in prefs named "OS X Volume" that
points to "/", that's already in there.

Signature

Steve Mills
Mac geek, drummer

Reply to this Message

MW Ron - 31 Aug 2004 19:42 GMT

>I think the project I'm trying to open (Carbon app that builds a
>packaged app) is OK, but maybe one of the subprojects (OSX framework) is
[quoted text clipped - 4 lines]
>I'm not sure what you're talking about here. You mean which linker the
>target uses?

the project will open with the target that was opened when you closed
the project.

So for example you have classic, carbon, Mach-O targets and you closed
it with Mach-O on the machine where it does work, close the project
with the classic target opened instead.

Then see if it will open on the other machine and if you change the
target you might get a more useful error message.

>I'm trying to open the project in OSX, not 9.

I misread that

>>Try setting the OS X Volume and then see if it opens. If not change it
>>to a classic target, although I'm not sure that always works.
>
>If you mean to add a source tree in prefs named "OS X Volume" that
>points to "/", that's already in there.

Do you have any funky paths? path or file names with a / in them or ?
or ! ' or * in them, That might be a problem too.

Ron

Signature

Reply to this Message

Steve Mills - 31 Aug 2004 22:12 GMT

Figured it out. For some reason, the .framework (and all the files and
folders inside it) that existed in the build folder was owned by some
other user. Don't know who the owner was, but it was wrong. I can now
open the main app project (that included the framework project) without
that goofy error. I submitted a bug that it should at least tell you the
name of the folder. Hopefully they'll fix that before the next release
so more user don't pull their hair out for 2 days straight.

Signature

Steve Mills
Mac geek, drummer

Reply to this Message

Adriaan van Os - 31 Aug 2004 07:10 GMT

> 206004
> Unable to open project. Directory could not be found.

The cure for "Unable to open project" errors is often to remove the
"<prohectname> Data" folder, but I don't know if it helps in this
particular case.

If the target is a package, you may want to remove it also.

My two cents.

Regards,

Adriaan van Os

Reply to this Message

Steve Mills - 31 Aug 2004 15:24 GMT

>The cure for "Unable to open project" errors is often to remove the
>"<prohectname> Data" folder, but I don't know if it helps in this
>particular case.
>
>If the target is a package, you may want to remove it also.

Nope, that didn't do it. This is incredibly annoying. I wish the error
message would tell me what *@&@^$ folder it's talking about! I'll go
enter that as a big a.s bug right now. It's early and I'm cranky.

Signature

Steve Mills
Mac geek, drummer

Reply to this Message

Mac Forum / Programming / CodeWarrior / August 2004

Can't open project