Xcode mail archive

Xcode 3.1.2 Release Notes (Chris Espinosa)

John MacMullin — Sat, 22 Nov 2008 04:15:13 +0100

Ok, I have checked the ADC site and its not there. When will it
appear on ADC?

John

On Nov 21, 2008, at 6:08 PM, wrote:

> Send Xcode-users mailing list submissions to
>
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.apple.com/mailman/listinfo/xcode-users
> or, via email, send a message with subject or body 'help' to
>
>
> You can reach the person managing the list at
>
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Xcode-users digest..."
>
>
> Today's Topics:
>
> 1. Xcode 3.1.2 Release Notes (Chris Espinosa)
> 2. Re: Nothing (reliably) helpful from atos + dSYM (Jason Molenda)
> 3. Re: Xcode Config files question (Rush Manbert)
> 4. Re: Xcode Config files question (John Brisbin)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 21 Nov 2008 13:44:20 -0800
> From: Chris Espinosa <>
> Subject: Xcode 3.1.2 Release Notes
> To: XCode-Users Users <>
> Message-ID: <>
> Content-Type: text/plain; charset="utf-8"
>

Xcode 3.1.2 Release Notes

Chris Espinosa — Fri, 21 Nov 2008 21:44:20 +0100

Xcode 3.1.2 is an update to the Xcode development environment. It
works only on Mac OS X 10.5 “Leopard” and can be installed either
alongside or replacing Xcode 3.1.1 or earlier. Please see the Xcode
3.1.1 Release Notes and Xcode 3.1 Release Notes for details about
previous versions of Xcode.
Summary of changes from Xcode 3.1.1
Like Xcode 3.1.1, Xcode 3.1.2 has no significant new features over
Xcode 3.1. It restructures the relationship between Xcode and the
iPhone SDK plugin, and fixes a small number of bugs. Three additional
build settings are supported, but are not available in the Build
Settings user interface.

Note: Due to a production error, the XCODE_VERSION_ACTUAL build
setting value in Xcode 3.1.2 returns “0310”.

General

Supported configurations
Xcode 3.1.2 will run on Mac OS X 10.5 (Leopard) on a Macintosh with
either a PowerPC or an Intel processor. It will not install or run on
earlier versions of Mac OS X. Xcode supports development for Mac OS X
10.3 (Panther) and Universal development for Mac OS X 10.4 (Tiger) and
Mac OS X 10.5 (Leopard) using the Mac OS X SDK support. It also
supports cross-development for the iPhone, iPod Touch, and iPhone
Simulator using the iPhoneOS SDKs, but only on Macintosh computers
with an Intel processor.

Warning: Xcode 3.1 2 works only with the iPhone SDK packages delivered
with the iPhone 2.2 SDK. If you have installed previous versions of
the iPhone SDK, you must upgrade to the newer version of the iPhone
SDK when upgrading to Xcode 3.1.2. This will still allow you to
develop for iPhone 2.0 and 2.1 as well as 2.2.

Xcode Installation
The default location for Xcode Developer Tools is /Developer. However,
you may install Xcode 3.1.2 on any volume in any location, and you can
move or rename the entire Developer directory after installation. The
only restriction is that the directory names of its subdirectories
must not be changed, nor moved within the developer directory; but the
Developer directory itself may be renamed and placed in any other
directory or volume, including servers and external drives.

This allows you to have multiple versions of Xcode tools installed on
the same system but running independently. The Xcode IDE will use the
SDKs, build tools, and auxiliary applications from the Developer
directory it is launched from whenever possible, rather than those
from the root system.

Project File Format Compatibility and Versioning
Xcode 3.1.2 reads and builds the targets of project files created in
Xcode 2.1 through 3.1.1, and will automatically upgrade project files
created in Xcode 1.5 through 2.0.

Project files opened and edited with Xcode 3.1.2 are generally
compatible with Xcode 3.1.1, 3.1, 3.0, and 2.5; this means that
project files you create or open with Xcode 3.1.2 can always be opened
and built with Xcode 3.1.1, 3.1, 3.0, and 2.5. There are no
incompatibilities between Xcode 3.1.2 and 3.1, though bug fixes may
make projects build correctly in 3.1.2 that will not build correctly
in earlier versions.

If you use a particular feature that would cause your project to fail
to build on a prior version of Xcode, you’ll see a Compatibility
Notice in the lower right corner of your project window; see Project
▶ Get Info ▶ General ▶ Compatibility to investigate and resolve
the compatibility issue.

Summary of New Features

Three new build settings allow you to control the output file of
strings and plist files processed by Xcode. Note that these settings
must be added as a User-Defined Setting and do not normally appear in
the Build Settings pane.
INFOPLIST_OUTPUT_FORMAT
PLIST_FILE_OUTPUT_FORMAT
STRINGS_FILE_OUTPUT_ENCODING
The default value for these settings is “XML”. Setting the value of
one of these build settings to “binary” causes all indicated files
(Info.plist, other plists file, or .strings file) in the target to be
copied into the product bundle in binary format.
Significant Bug Fixes from Xcode 3.1.1

In Xcode 3.0, External Targets lost the ability to output the
environment variables that are passed to them. This has been restored
in Xcode 3.1.2. 6169099
Downloading and installing documentation sets no longer consumes
excessive amounts of CPU. 5891184
Edit All in Scope no longer crashes when typing certain composed
Unicode characters. 6217303
Known Issues and Workarounds

Here are some commonly-reported issues that are known with this
release of Xcode.

If the project.pbxproject file inside your project wrapper is locked,
your separate user.pbxuser file will not be written, and breakpoints,
custom executables, and window positions you change will not be saved.
4440006
While most known cases have been taken care of, having a space, comma,
slash, backslash, tilde, or other character special to the Unix shell
in the directory name of any parent folder of your project can cause
your project build to fail in unexpected ways. 4101529
Having the same file in your project referred to both directly and via
a symbolic link from separate places can corrupt the project index and
cause Xcode to crash. Remove the project index and remove the symlink
reference to the file. 4056799
On a very small number of systems and for unknown reasons, the I-beam
editing cursor does not hide when you start typing. 4191120
In certain circumstances, applications like Xcode can exhaust the
Window Server’s ability to create new windows, causing an
NSInternalInconsistencyException Error (1000) creating CGSWindow. This
will be addressed in a future version of Mac OS X. 3108154
The Touch menu item (or clicking in the “hammer” column) only works
for source code files, not headers, libraries, NIB files, resources,
or other project files. 4912312
If you define a Source Tree in the Preferences pane, you must quit and
reopen Xcode for it to take effect. 4416517
Xcode does not interact well with Spaces; opening auxiliary Xcode
windows may switch you to Xcode’s main Space. 5308807
The function popup does not distinguish between functions with the
same identifier. 2566673
NSImage caches images in a manner that makes the Objective-C Garbage
Collector issue a console log of the form “malloc: free_garbage:
garbage ptr = 0x3846140, has non-zero refcount = 1”. These can be
ignored.
The default setting for debugging libraries and frameworks is Load
Symbols Lazily. On occasion this causes breakpoints to not be hit.
Turning off this setting makes it take longer to start debugging, but
hits breakpoints more reliably.
Referring to an .xcconfig file using #include does not consult any of
the target’s Search Paths; all referenced configuration files should
be stored in the same directory. 5850085
Using a port number when setting up a Subversion repository in the
Repositories panel generates an inaccurate svn+ssh: URL. Instead of
entering the port number in the Repository setup pane, leave off the
port number in Xcode and add an entry with the port number in ~/.ssh/
config for the desired host. 5801847
A bug in NSFileManager makes restoring from snapshots fail
catastrophically in specific circumstances. Until this is addressed,
ensure that you have a Time Machine backup or a repository version of
your working code before attempting to restore from a snapshot. 5468824
If you build a project prior to importing it into SCM, then the
project’s build folder may be imported into your repository, and
subsequent Commit Entire Project operations will fail. Remove the
build folder from the repository. 4896482
Regular expression searches are limited to single lines. 5842770
Only the version installed in /Developer is available as a Distributed
Build volunteer by other computers. 5939834
When adding frameworks or libraries using the Target Inspector, you
can only see frameworks in the SDK that the inspected target is
configured for. To add frameworks from a different SDK, first change
the Base SDK setting of that target. 5931773
Find in File and Project Find will only find the actual key names in a
Property List file, not the display names as seen in the Property List
Editor. 5946354 Replace does not work in the embedded Property List
editor; command-click and choose Open As ▶ Source Code File to
perform Find and Replace. 5946376
Syntax-Aware Indentation does not work correctly with certain keyboard
layouts, such as German. 5848499
The default Build and Go toolbar item is not useful in projects
without a configured Executable, such as KEXT projects. Add a Custom
Executable or replace the Build and Go item with Build. 5939297

Tabbing to Placeholders

Greg Deward — Fri, 21 Nov 2008 15:22:29 +0100

Good morning!

I am just moving from .NET to Mac (Cocoa / ObjC) and finding that I am
using the code assist feature of XCode a lot. Is it possible to tab
or jump to the next placeholder in the selector? For example:

[tableView editColumn:0 row:<#(NSInteger)row#> withEvent:<#(NSEvent
*)theEvent#> select:<#(BOOL)select#>]

In the snippet above, I just finished typing "0" for editColumn. I
would love to be able to jump to the variable for "row".
Unfortunately, hitting "tab" just inserts an actual tab.

Thanks, in advance.

-- Greg

Project handling multiple developers

mahaboob pa — Fri, 21 Nov 2008 04:04:06 +0100

Hi all,
I need to make further developments of my project with multiple developers.
By googling I got one solution as using CVS. I'm using Leopard and Xcode3.1.
My project resides on the folder Desktop/myProject. In Terminal I did like
this.
newtoks-mac-mini:~ Newtok$ mkdir first_cvs
newtoks-mac-mini:~ Newtok$ export CVSROOT=/first_cvs
newtoks-mac-mini:~ Newtok$ cvs init
newtoks-mac-mini:~ Newtok$ cd desktop
newtoks-mac-mini:~ desktop Newtok$ cd myProject
newtoks-mac-mini:myProject Newtok$ cvs import -m "first" first_cvs yoyo
start
newtoks-mac-mini:myProject Newtok$ cd
newtoks-mac-mini:~ Newtok$ cvs checkout first_cvs

When I checkout one file and then making any editing and commit it, then the
file is updating and information is enters into the Entries file.

But I can't make it accessible to multiple developers. How can I do that?
How can I add another developer?In the article I found it by using NetInfo
Manager.App can do this. But I can't find out this in system. Is there any
other easly manageable free version control system available ?

Thanks in advance
mahaboob

Renaming nibs and files in Xcode 3.1

DKJ — Fri, 21 Nov 2008 00:36:36 +0100

I'm having no end of difficulty renaming both nib and source files. IB
refuses to recognise the new names I give to source files that were
created by a project template. For example, it won't recognise the new
name when I try to set File's Owner. I also get run-time errors when I
rename any of the nib files that the template created. Has anyone else
run into this problem?

To rename the files, I've just been right-clicking the filename in the
project window and choosing "Rename" from the menu.

For now I'll just leave the template-chosen names alone. But it looks
ugly seeing things like "FirstViewController" in the project window.

dkj

building cURL?

Rich Collyer — Thu, 20 Nov 2008 22:39:26 +0100

I need to build and link with my own version of cURL (mostly because
we need to implement the SSL_FILETYPE_ENGINE case in the function
cert_stuff). The library needs to be a universal binary that works on
both 10.4.x and 10.5.x. I have tried to use build commands similar to
openssl (see below), but it just does not seem to work.

Any hints?

+++++++++++++++++++++++
Rich Collyer - Senior Software Engineer

IronKey - The World's Most Secure Flash Drive
2008 SC Magazine Readers Choice Award Winner
2008 FOSE Best of Show Winner
2007 GCN Labs Reviewers Choice Winner
+++++++++++++++++++++++

# i386 Static Library - shell script goes here
BUILD_DIR=build/static/i386
make clean
./Configure 386 darwin-i386-cc
make "CC=cc -arch i386 -mmacosx-version-min=10.4 -isysroot /Developer/
SDKs/MacOSX10.4u.sdk"
mkdir -p $BUILD_DIR
cp *.a $BUILD_DIR
echo "Done i386 - Static Library"
exit 0

# ppc static library - shell script goes here
BUILD_DIR=build/static/ppc
rm *.a
make clean
./Configure ppc darwin-ppc-cc
make "CC=cc -arch ppc -mmacosx-version-min=10.4 -isysroot /Developer/
SDKs/MacOSX10.4u.sdk"
mkdir -p $BUILD_DIR
ls *.a > libnames.tmp
mv *.a $BUILD_DIR
echo "Done PPC - Static Library"
exit 0

# Static Universal - shell script goes here
for lib in `cat libnames.tmp`; do
lipo -create build/static/*/$lib -output build/static/$lib
ranlib build/static/*.a
done
exit 0

Nothing (reliably) helpful from atos + dSYM

Nathan Vander Wilt — Thu, 20 Nov 2008 18:23:38 +0100

I recently sent out a release of an upcoming product to some alpha
testers, who found a few crashers. They sent me the crashlogs and
since I had generated dSYM info for the build, I gave atos a shot.

From the directory where I had both Mercatalog.app and
Mercatalog.app.dSYM, I tried:
/Developer/user/bin/atos -arch x86_64 -o Mercatalog.app/Contents/MacOS/
Mercatalog 0x0000000100020ff4
but all I got back was the almost-useless:
0x0000000100020ff4 (in Mercatalog)

I used dwarfdump --uuid to compare the UUIDs between the .dSYM and the
app executable and they matched.
I also tried using:
dwarfdump Mercatalog.app.dSYM --arch=x86_64 --lookup= 0x0000000100020ff4
but that didn't find anything either, although maybe I'm using that
wrong (It outputs "Looking up address: 0x00000000ffffffff in the debug
information...not found.", which isn't what I wanted it to look up
anyway...)

The odd thing is that I did get atos to work just fine (with the exact
same project.pbxproj) when I force a crash by adding a
printf((char*)1) to the otherwise unchanged source code. Why would it
work with the build I just made this morning, but not the copy of the
build I sent out last week? Does atos break if the executable/symbols
are moved from the original build path? I need a reliable way of
getting symbol information for released products.

thanks,
-natevw

Re: get rid of warning "suggest parenthesis around assignment used as truth value"

Greg Guerin — Thu, 20 Nov 2008 17:28:18 +0100

Jean-Daniel Dupas wrote:

> To enable it you have to either add the -Wparentheses warning flag
> or check the "Missing Braces and Parentheses" build setting.

The man page also says "This warning is enabled by -Wall."

http://developer.apple.com/documentation/Darwin/Reference/ManPages/
man1/gcc.1.html

-- GG

Wrangling 3rd party libraries with xcconfig settings?

Allen Cronce — Thu, 20 Nov 2008 17:02:49 +0100

Hi all,

We make heavy use of open source third party libraries. For a variety
of reasons, we need to build static versions of these libraries. We
have scripts that help us build these periodically, by implementing
the usual configure, make, make install, rinse, repeat dance.

The problem with this approach is maintainability. Currently our
regular Xcode projects all share common project and target xcconfig
files. When we want to make a global change, like targeting a new base
SDK, it's in one place and is really easy to do. But the third party
library builds don't have access to our Xcode config settings. So when
we make fundamental changes, we have to manually monkey with the third
party configurations to match what we're building with the main
projects.

To make this process easier, we're trying a hybrid approach where
Xcode drives the configure and make process, similar to what this
developer did for sqlite:

http://ascarter.wordpress.com/2006/05/21/xcode-project-for-sqlite/

The difference in our case is that we're translating our Xcode config
settings to environment flags passed to a given open source library's
configure script. So for example, if someone changes the debug symbol
type in our base xcconfig files, this results in the right parameter
being set in the CFLAGS variable provided during configure. The
resulting MakeFile will then do the right thing at build time,
resulting in libraries that match our main Xcode settings.

Currently we've written a magic script that translates between common
Xcode config values and the corresponding gcc command line parameters.
The script is generic, with override values that can be set as needed
in the target of the configure build phase for a given library. This
works surprisingly well on the few open source libraries we've
experimented with so far.

But I'm concerned that we're still looking at a maintenance issue
(although greatly reduced). The problem is that this solution will
only be as good as the translation script. We can't realistically
implement every possible gcc option, so we only deal with the big
ones, like debug symbols, optimization level, SDK, symbol visibility,
etc.

Further when Apple makes changes to the dev system, we'll have to
track them. For example, if Apple moves to dwarf-3, we'll have to
change our translation script, which currently detects dwarf style
symbols and generates the command line parameter for dwarf-2.

Is there a better way for us to obtain the gcc C and Link command line
parameters for a given target? Admittedly I haven't dug into how Xcode
creates its CompileC and Ld commands. Maybe the answer is in there
somewhere.

One alternative might be a hack where we create a hello world project
that inherits from our xcconfig files, build it via xcodebuild, snag
the resulting gcc command lines, and parse out the parameters. This
could also be scripted to make it automatic. It would probably work,
but seems somewhat nasty. I'd much prefer a more direct approach to
obtaining the parameters, if possible.

Any thoughts or suggestions for a reasonable way to solve this problem
would be appreciated.

Best,
--
Allen Cronce

How to use /Developer/MacOSX10.4u.sdk/usr/lib/

B. Blodau — Thu, 20 Nov 2008 15:56:00 +0100

Hi,
my Carbon project includes some third party libraries which require
some system libs, like libiconv.dylib, libconvert.dylib etc.

If I add them from "/usr/lib/" to my project the project builds
successfully. But if I use the same libs from "/Developer/
MacOSX10.4u.sdk/usr/lib/", I'm getting link errors about unresovled
externals - unknown symbols. These are the same error, I would get if
I did not add the libs at all.
So it seems that these libs are not found or linked.

Is there something else I have to set up, if using libs from the
location: "/Developer/MacOSX10.4u.sdk/usr/lib/"
I'm working on Tiger with XCode 2.4.1 using "/Developer/
MacOSX10.4u.sdk/" as the SDK path.

Thanks for any help.
Ciao
Bert