cocoaforge

hm, no same errors with a new checkout.

btw: i don't need trunk necessarily, I just want an adium source to build and maybe commit some changes.

You won't be committing until you have some patches approved by a current committer.

Try to figure out why it's not building for you and then make a patch.

trunk builds for me at present and hasn't failed to do so in a while... It looks like your framework search paths are messed up somehow, but I'm not sure how.

alright, I got it build and run now.

What should I do with that now? Should I commit my changes to the project? (Because actually I did some rather strange things with it)

Well, describe what you did and then if it's something we can use we'll get you to generate a patch.

well, first of all "Growl-WithInstaller" wasn't listed in "Linked Frameworks" at all and the structure in "Growl-WithInstaller.framework" was unlike the other frameworks. So I created the "Growl-WithInstaller", "Headers", "Resources" and "Current" (in "Versions") links inside the .framework-folder. Then I copied it into Xcode's "Linked Frameworks". Because Xcode couldn't copy them (I have no idea why) I had to leave them linking to the Desktop. This version built fine for me now.
To make it run I had to copy the "Growl-WithInstaller.framework"-Folder from the Desktop into ../build/Development

There's something seriously wrong on your end if you had to do all of that from what I can tell.

but I used the unmodified checkout from 'http://svn.adiumx.com/adium/trunk '

Tidy up things like that needed to make it work on individual machines wouldn't likely be accepted as patches if it generally builds for all others.

I have exactly the same problem with rev 18404 (1.0b17). Xcode generates an error on the line in NEHGrowlPlugin.m. The Growl-WithInstaller framework lies in the same directory as this file but is not listed in linked frameworks.

I haven't coded muck in Xcode so my preferences are almost default. Maby there is a setting that needs to be changed in Xcode to be able to build Adium.

iirc the trac ticket on this indicated that the symlink is borked. Recreating it should fix the issue.

This solves the problem with the latest rev 18409: Shouldn't this be fixed in the repository?

Aahlborg wrote:This solves the problem with the latest rev 18409:

Code: Select all

cd Adium/Frameworks/Growl-WithInstaller.framework
ln -s Versions/A Current
ln -s Current/Growl-WithInstaller Growl-WithInstaller
ln -s Current/Headers Headers
ln -s Current/Resources Resources

Shouldn't this be fixed in the repository?

A lot of us are saying it's not broken in the repository. Only a handful of people are having problems with it.

The_Tick wrote:A lot of us are saying it's not broken in the repository. Only a handful of people are having problems with it.

Tried with a fresh checkout and got the error again. Maybe something to look into.

Aahlborg wrote:

The_Tick wrote:A lot of us are saying it's not broken in the repository. Only a handful of people are having problems with it.

Tried with a fresh checkout and got the error again. Maybe something to look into.

I understand that. However, since none of the devs are running into it, I'm hesitant as to whether this is just a project issue or a environment issue.

And since we're close to a release, I'd rather not invest the time to investigate it, and would rather get the release out.

You've got a work around for now, and until we can look at it you'll need to continue using it. If you find the cause of the problem on your machine then we'd be happy to look at a concise, point by point take on how to fix it, but otherwise it'll have to wait.

Not sure if this is related, but FWIW, since upgrading to Xcode 2.4.1, I experienced a similar issue trying to build Vienna. Moving the checked out sources to a path that contained no spaces and attempting to build again seemed to cause the error to vanish -- I understand though from the original post that this was already checked.

The_Tick wrote:I understand that. However, since none of the devs are running into it, I'm hesitant as to whether this is just a project issue or a environment issue.

And since we're close to a release, I'd rather not invest the time to investigate it, and would rather get the release out.

You've got a work around for now, and until we can look at it you'll need to continue using it. If you find the cause of the problem on your machine then we'd be happy to look at a concise, point by point take on how to fix it, but otherwise it'll have to wait.

I'm not an experienced Xcode user but I'll see if I can find out what makes it work for some people but not for others.

Error is in NEHGrowlPlugin.m

Growl-WithInstaller/Growl.h No Such file or directory

The Framework is referenced from the Project file. I do not have another version of the Growl SDK installed anywhere else. I'm using XCode 2.4. Should I upgrade to 2.4.1?

Sorry, for some reason when first reading this thread I only saw the first couple responses and after posting I see a big long discussion... Fixing the symlinks as above solved the problem for me.

andrewlmurray wrote:Error is in NEHGrowlPlugin.m

Growl-WithInstaller/Growl.h No Such file or directory

The Framework is referenced from the Project file. I do not have another version of the Growl SDK installed anywhere else. I'm using XCode 2.4. Should I upgrade to 2.4.1?

I upgraded to 2.4.1 but I got the same error. Seems like fixing the symlinks manually is our best shot at this time.