I changed the Active Build configuration to Distribution and then select the
code signing identity to my distribution profile as suggested in the iPhone
Developer portal. Then I build the application. But,I got the following
message:
File /../.../.../...xxx.app depends on itself. This target
1) read the error message and attempt to understand it
2) see if the error message applies and you have in fact included the
product in its own target
3) if 1) and 2) don't work mail the XCode list because this isn't a
cocoa question
Mahaboob wrote:
I changed the Active Build
Hi all,
I hope someone can help me shine some light on this error. I have two
errors coming up on build, but they are not highlighted anywhere in
the code as is normally the case with warnings and errors. This is
what I see in the Errors and Warnings list:
(In red)
On Sat, May 23, 2009 at 6:21 AM, Ian Piper ianpi...@mac.com wrote:
(In red) _TLTableBgColorKey, referenced from:
(in grey) _TLTableBGColorKey$non_lazy_ptr in
MyDocument.o
(in red) _TLColorChangedNotification, referenced from:
(in grey)
Kyle Sluder wrote:
One of the following has happened:
Variations:
4. The build configuration that worked last week (e.g. Debug) isn't
the one that's being compiled today (e.g. Release), and there are
differences in something specific to the config, such as lib search
paths, include
Can anyone tell me what the following means and what is the cause?
I understand that it is a link error. Elsewhere, Graham Cox in
replying to a similar problem by another poster stated This is a link
error. Add the QuartzCore framework to your project. I did exactly
that to no avail.
Hi,
I am trying to get CocoaMySQL running in my XCode. So I created an
easy application to query my database. In the Controller.m file I
added the line:
#import MCPKit_bundled/MCPKit_bundled.h
CODE:
__
MCPConnection * mySQLConnection =
I've been working on a project for a few weeks now and suddenly today
I get this error while building (see below). I was getting this same
error in one of my real classes so after commenting out almost every
bit of code and still seeing the error, I decided to just create a new
TestClass
you forgot the break;
On 17-Apr-08, at 3:47 PM, Don Arnel wrote:
I've been working on a project for a few weeks now and suddenly
today I get this error while building (see below). I was getting
this same error in one of my real classes so after commenting out
almost every bit of code and
On Fri, Apr 18, 2008 at 12:47 AM, Don Arnel [EMAIL PROTECTED] wrote:
switch (1) {
default:
}
(x)(error: label at end of compound statement)
You need a statement to execute for the default case. The code you
have written is equivalent to:
-
On Thu, Apr 17, 2008 at 11:47 PM, Don Arnel [EMAIL PROTECTED] wrote:
I've been working on a project for a few weeks now and suddenly today I get
this error while building (see below). I was getting this same error in one
of my real classes so after commenting out almost every bit of code and
on 4/17/08 4:56 PM, [EMAIL PROTECTED] purportedly said:
A break; is not required, but it does cause the compound statement
error to go away. Even with the break; inserted the other error still
occurs if the comments are removed.
On Apr 17, 2008, at 6:50 PM, Robert Kukuchka wrote:
you
The break isn't required, but something is. You could put
NSLog(@defaulting); after default:. Or you could put a semicolon; or
a lovely set of empty braces.
To fix the other problem, try this:
switch (1) {
case 1:
{
NSMutableArray *myArray=[[NSMutableArray
Change it to:
- (void)TestFunction
{
switch (1) {
case 1:
{
NSMutableArray *myArray=[[NSMutableArray alloc]
init];
break;
}
}
}
No need to declare
Ah, that did the trick! I love mailing lists!
Many thanks to all who responded.
On Apr 17, 2008, at 7:15 PM, Michael Vannorsdel wrote:
Change it to:
- (void)TestFunction
{
switch (1) {
case 1:
{
NSMutableArray
GCC is alerting you to the fact that the switch at the end of the
statement is unnecessary. If you really want to do something for all
cases, use default. Otherwise just omit it. Using the empty
statement (; by itself) will fool GCC, but an empty default case is
useless.
--Kyle Sluder
On 18/04/2008, at 9:54 AM, Kyle Sluder wrote:
GCC is alerting you to the fact that the switch at the end of the
statement is unnecessary.
That's not what GCC is trying to do; GCC is trying to alert you to the
fact that it's invalid syntax. As I just said in my earlier e-mail,
labels must
17 matches
Mail list logo
