1.4rc2 build issues on XCode 2.1

#1 Some googling is showing me that Xcode is worse than I imagined. If you encounter issues such as this, the trick is to click the small button on the lower left corner of the build status panels window for displaying the raw output of the build. The button resembles tiny lines of text in a window.

tone

#2 I also have the same link error (though it tells me what symbols, they are in zlib) but I am using XCode 2.0 and TGE 1.3. Have you had any success fixing this problem?

#3 Yes. I cannot at the moment recall what the precise issue was, and what the fix was.

Sorry to be unhelpful-- try searching on zlib on the TGE site or (guessing here) attempting to add a -Lzlib or similar item to your link command line.

tone

#4 I am getting the same problem compiling for the MAC in Xcode.. just exactly the same.. Out of the box, fresh downloaded HEAD opened in Xcode 2.1

and i get the same error Anthony gets..

any ideas??

#5 One point to mention is that while I forget what exactly was hidden in my case (as the screenshot above shows), I have since worked past the issue.

One thing to check -- have you read the README file in the PB directory?

There is a script you need to run there (fix xcode build folders.command), and, as I recall, it does not "just work" as-is. There are two or three things wrong with it: it has MS-DOS end of line characters, the instructions to double-click it do not establish the proper working directory, and it may not be marked as executable.

Do this:

1. open up Terminal
2. cd to the pb folder
3. type "cat fix\ xcode\ build\ folders.command" (or whatever its filename is)
4. drag and select the entire text of the command file, and command+copy it to the clipboard
5. type "cat > fix\ xcode\ build\ folders.command" and hit enter.
6. paste the text back INTO the file and typer control+D (this fixes the MS-DOS crlf issue)
7. type chmod +x fix\ xcode\ build\ folders.command (this fixes the run permissions if indeed they were still broken)
8. lastly -- type "./fix\ xcode\ build\ folders.command" and hit enter. This way of invoking it (from the Terminal in the PB folder) addresses the issue of it not having the proper current working directory when it does its thing.

I am not sure that this is your issue (at all), but it is an issue perhaps next down the road for you!

edit: if you'd like to phone me, we can compare settings and then write up our discovery here. I am at
+1 617 642 9223 and on the US East Coast (GMT -5 or so)

tone

#6 I don't see the script you are talking about. Are you talking about the "ranlib" thing? I believe I have gotten past that one already. Other than that, I don't see any references to the commands you mention above. I'm currently using TGE 1.3.

Edit: Ah, but I see this thread is talking about 1.4rc2. I'll have to download it and look there.

#7 Sorry -- the script I mentioned only pertains to recent (1.4ish) versions.
I made a bad assumption.

I would not encourage you to try 1.4 if 1.3 is giving you trouble, but you never know!

tone

#8 I saw the script, it is true, it doesnt work.. so I opened a terminal, walk my way down to the pb folder and just copy the script and paste into the console and it ran...

I am having exactly the same problem shown in the sshoot, and i have done everithing right (i think :D)

Anthony, do you have SKYPE? maybe we can talk each other over there.. I am from Argentina, my english is not so good but i can hold my own... :D

btw: my skype ID is "martinrepetto"

bye..

#9 I am DulcetTone on Skype... just reinstalled it.

tone

#10 Let me know when you guys figure this out! Thanks...

#11 Will sure do.! talk to anthony tomorrow!..

#12 The current xcode project in CVS is missing the unicode.cc and unicode.hh files from the core directory. Once you add them to the project it should link fine.

#13 I will try linking those files. right now.. and let you know what happened....

#14 First try... gave me back the same error... making a clean and building again...

#15 I have added the files to the project, under the CORE directory, and the .h file under the CORE/HEADERS directory.

And it didnt work.... BUT..

When I right clicked the files.. and put.. GET INFO for example in unicode.cc, under the targets tabs I choose all the targets.

And then make a clean build...

And it works...

#16 FYI, in my case, just adding core.cc/h to the xcode project solved the problem.

and thanks for the Anthony's comment. I kept forgetting this.. indeed, xcode in this respect is really damn.

Quote:the trick is to click the small button on the lower left corner of the build status panels window for displaying the raw output of the build. The button resembles tiny lines of text in a window.

#17 @Andy: See the other thread for a fix on the link errors.

@Craig: unicode files added to both project files, thanks for the report.

@Anthony: An easier way to twiddle line endings is to open the file in Xcode, and set the line endings there. CVS gets a little evil about respecting +x flags sometimes, and about line endings; it should be fixed now. Added the cwd setting code to the top of the script. These issues should be fixed now. Thanks for the bug report.