Xcode-users Digest, Vol 8, Issue 2
Xcode-users Digest, Vol 8, Issue 2
- Subject: Xcode-users Digest, Vol 8, Issue 2
- From: James Jaeger <email@hidden>
- Date: Tue, 4 Jan 2011 21:28:05 -0800
Send Xcode-users mailing list submissions to
email@hidden
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
email@hidden
You can reach the person managing the list at
email@hidden
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Xcode-users digest..."
Today's Topics:
1. XCode Build And Archive Is Dimmed, (Alex Jurgensen)
2. Re: XCode Build And Archive Is Dimmed, (M Pulis)
3. Re: Xcode crashes on iPhone4 restore (Clark Cox)
4. Re: Xcode crashes on iPhone4 restore (Jonathon Kuo)
5. Re: Xcode crashes on iPhone4 restore (Clark Cox)
6. Re: XCode: Still Not Able To Code Sign (Phillip Hutchings)
7. Workaround for Xcode Not Noticing new Build Settings in
Info.plist Preprocessing (Jerry Krinock)
8. no SubSystem declaration error (email@hidden)
9. Breakpoints in dependent project? (McLaughlin, Michael P.)
10. ISO versions of open(), read(), lseek() (Todd Heberlein)
11. Re: ISO versions of open(), read(), lseek() (Sherm Pendley)
12. Re: ISO versions of open(), read(), lseek() (Tom Seddon)
13. Re: ISO versions of open(), read(), lseek() (Todd Heberlein)
14. Re: ISO versions of open(), read(), lseek() (Todd Heberlein)
15. Re: ISO versions of open(), read(), lseek() (Alastair Houghton)
----------------------------------------------------------------------
Message: 1
Date: Mon, 3 Jan 2011 00:51:09 -0800
From: Alex Jurgensen <email@hidden>
Subject: XCode Build And Archive Is Dimmed,
To: email@hidden
Message-ID: <email@hidden>
Content-Type: text/plain; charset=us-ascii
Hi All,
The Build And Archive feature of the latest version of XCode.
I am trying to build a Mac application for submission to the Mac App
Store.
I am running Mac OS X 10.6.5 Snow Leopard.
Do I need to install anything than my developer certificates and XCode.
Any help with this is greatly appreciated.
Regards,
Alex,
------------------------------
Message: 2
Date: Mon, 3 Jan 2011 03:27:01 -0700
From: M Pulis <email@hidden>
Subject: Re: XCode Build And Archive Is Dimmed,
To: Alex Jurgensen <email@hidden>
Cc: email@hidden
Message-ID: <email@hidden>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
On Jan 3, 2011, at 1:51 AM, Alex Jurgensen wrote:
Hi All,
The Build And Archive feature of the latest version of XCode.
I am trying to build a Mac application for submission to the Mac App
Store.
I am running Mac OS X 10.6.5 Snow Leopard.
Do I need to install anything than my developer certificates and
XCode.
Any help with this is greatly appreciated.
Regards,
Alex,
Have you selected Device and Release in the Overview popup?
Gary
------------------------------
Message: 3
Date: Mon, 3 Jan 2011 08:15:18 -0800
From: Clark Cox <email@hidden>
Subject: Re: Xcode crashes on iPhone4 restore
To: Jonathon Kuo <email@hidden>
Cc: Xcode-list Users <email@hidden>
Message-ID:
<AANLkTimZy=email@hidden>
Content-Type: text/plain; charset=UTF-8
On Wed, Dec 29, 2010 at 8:17 PM, Jonathon Kuo
<email@hidden> wrote:
On Dec 29, 2010, at 6:14 PM, David Duncan wrote:
On Dec 29, 2010, at 1:17 PM, Jonathon Kuo wrote:
Xcode crashes every time I try to restore my iPhone4, even after
a reboot of the iPhone and my iMac. The iPhone was on 4.0.1 and I
selected 4.2.1 and clicked "Restore". Crash! What to do now?
1) File a bug
2) Use iTunes for the restore
That's what I ended up doing, although the Provisioning section of
the portal was out to lunch, resulting in an invalid Team
Provisioning Profile, which I had to regenerate later in the day.
What is the number of the bug that you filed?
--
Clark S. Cox III
email@hidden
------------------------------
Message: 4
Date: Mon, 3 Jan 2011 09:40:00 -0800
From: Jonathon Kuo <email@hidden>
Subject: Re: Xcode crashes on iPhone4 restore
To: Clark Cox <email@hidden>
Cc: Xcode-list Users <email@hidden>
Message-ID:
<email@hidden>
Content-Type: text/plain; charset=us-ascii
On Jan 3, 2011, at 8:15 AM, Clark Cox wrote:
On Wed, Dec 29, 2010 at 8:17 PM, Jonathon Kuo
<email@hidden> wrote:
On Dec 29, 2010, at 6:14 PM, David Duncan wrote:
On Dec 29, 2010, at 1:17 PM, Jonathon Kuo wrote:
Xcode crashes every time I try to restore my iPhone4, even after
a reboot of the iPhone and my iMac. The iPhone was on 4.0.1 and
I selected 4.2.1 and clicked "Restore". Crash! What to do now?
1) File a bug
2) Use iTunes for the restore
That's what I ended up doing, although the Provisioning section of
the portal was out to lunch, resulting in an invalid Team
Provisioning Profile, which I had to regenerate later in the day.
What is the number of the bug that you filed?
I didn't file a bug report per se, but submitted the crash report to
Apple.
------------------------------
Message: 5
Date: Mon, 3 Jan 2011 10:04:37 -0800
From: Clark Cox <email@hidden>
Subject: Re: Xcode crashes on iPhone4 restore
To: Jonathon Kuo <email@hidden>
Cc: Xcode-list Users <email@hidden>
Message-ID:
<AANLkTi=c-QAbNBsowL12pF5sGUVk3wEsYUx=email@hidden>
Content-Type: text/plain; charset=UTF-8
On Mon, Jan 3, 2011 at 9:40 AM, Jonathon Kuo
<email@hidden> wrote:
On Jan 3, 2011, at 8:15 AM, Clark Cox wrote:
On Wed, Dec 29, 2010 at 8:17 PM, Jonathon Kuo
<email@hidden> wrote:
On Dec 29, 2010, at 6:14 PM, David Duncan wrote:
On Dec 29, 2010, at 1:17 PM, Jonathon Kuo wrote:
Xcode crashes every time I try to restore my iPhone4, even
after a reboot of the iPhone and my iMac. The iPhone was on
4.0.1 and I selected 4.2.1 and clicked "Restore". Crash! What
to do now?
1) File a bug
2) Use iTunes for the restore
That's what I ended up doing, although the Provisioning section
of the portal was out to lunch, resulting in an invalid Team
Provisioning Profile, which I had to regenerate later in the day.
What is the number of the bug that you filed?
I didn't file a bug report per se
Then please do so.
--
Clark S. Cox III
email@hidden
------------------------------
Message: 6
Date: Tue, 4 Jan 2011 11:36:50 +1300
From: Phillip Hutchings <email@hidden>
Subject: Re: XCode: Still Not Able To Code Sign
To: Xcode Users <email@hidden>
Message-ID: <email@hidden>
Content-Type: text/plain; charset="us-ascii"
On 3/01/2011, at 3:24 PM, Alex Jurgensen wrote:
Hi,
I am trying to submit my application to the Mac App Store.
I am having a little trouble with XCode though.
I don't see my code signing certificate as an option in the code
signing section of the "Build" tab of my projects inspector window.
I have used the reverse domain name org.myorganization.application
as my "CFBndleIdentifier" in my project's "Info.plist" file.
I created an "Application ID" with the same reverse domain
identifier using Apple's tools for this task.
Then I created an app certificate by uploading a certificate
signing request, using Apple's tools for this task, downloading the
certificates and installing them.
I don't see how the reverse style domain is tied to the developer
certificate.
I still can't get XCode to code sign the application.
any help with this is greatly appreciated.
Posting the same question three times to the same list in 2 days
isn't likely to elicit new responses, especially over the new year
period. You'll probably get more responses in the coming days as
people come back online and read the list.
Anyway, few things to check - caveat: I haven't done Mac App Store
development, only iOS App Store, but I assume Xcode works the same:
Open Keychain Access (Applications -> Utilities), look in My
Certificates (under Category on the left) and make sure your
certificate is there, on iOS it's named "iPhone Distribution -
Developer Name", so something similar to that I assume. Open the
disclosure arrow on your certificate and check your private key is
there. Also check that the certificate is valid.
If there's no disclosure arrow next to your certificate you don't
have the private key. The private key is stored on the computer that
generated the certificate request and never exported unless you do so
explicitly, if this is the case go to the computer you requested the
certificate with and export the key from Keychain Access.
If you have the private key but the certificate isn't valid then
check you have all intermediate and root certificates - Apple's
website will tell you what you need.
If both of those are correct then restart Xcode, as it doesn't seem
to pick up new certs while running, and check again.
Finally restart Xcode and create an entirely new application and see
if you can set up code signing.
Extra notes:
Certificates aren't tied to application identifiers. Using Xcode you
can sign any app with your cert, but on iOS we have provisioning
profiles that are signed with the certificate and contain the
identifier. That profile is distributed with the application and if
the identifiers don't match it'll fail.
I haven't seen the Mac App Store, but check there's no provisioning
profile or similar to download.
--
Phillip Hutchings
email@hidden
--
Phillip Hutchings
email@hidden
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2302 bytes
Desc: not available
Url : http://lists.apple.com/pipermail/xcode-users/attachments/
20110104/1c6c872a/smime.bin
------------------------------
Message: 7
Date: Mon, 3 Jan 2011 17:26:48 -0800
From: Jerry Krinock <email@hidden>
Subject: Workaround for Xcode Not Noticing new Build Settings in
Info.plist Preprocessing
To: XCode Users <email@hidden>
Message-ID: <email@hidden>
Content-Type: text/plain; charset=windows-1252
I should have thought of this a long time ago, but since we've
discussed this here before and never got a good solution, I just
realized that there is an easy workaround for Apple Bug 24954,
Duplicate/4505141 in Xcode, which is that Xcode does not check for
changed Build Settings that are referenced in Info.plist when it
decides whether or not to preprocess and produce a new Info.plist
file. Therefore, for example, if you are using the placeholder $
{CURRENT_PROJECT_VERSION} in your Info.plist, and you change your
CURRENT_PROJECT_VERSION Build Setting and then rebuild, the version
number in the new product's Info.plist will still be the prior version.
The workaround is to add a Run Script Build Phase. The script's text
is one line of bash
touch "$INFOPLIST_FILE"
Add this Build Phase before the Copy Files Build Phase, in any Target
that has an Info.plist. Xcode will now preprocess and produce a new
Info.plist file (which takes a few milliseconds) with each and every
build.
------------------------------
Message: 8
Date: Tue, 4 Jan 2011 17:29:03 -0000
From: email@hidden
Subject: no SubSystem declaration error
To: email@hidden
Message-ID:
<email@hidden>
Content-Type: text/plain;charset=iso-8859-1
Hi Folks,
I am currently converting a Kernel Extension Project to 64 bit. Almost
there but I am getting no SubSystem declaration in Mig
clock_types.defs
, mach_types.h and std_types.h. The error is tagged at the end of each
file.
I think MiG needs a "subsystem" definition somewhere but as these are
framework files I'm assuming I have the wrong project settings.
GCC version is 4.2
arch is x86_64
SDKROOT /Developer/SDKs/MacOSX10.6.sdk
Any thoughts on what to check?
Cheers,
Paul.
------------------------------
Message: 9
Date: Tue, 4 Jan 2011 13:12:15 -0500
From: "McLaughlin, Michael P." <email@hidden>
Subject: Breakpoints in dependent project?
To: "email@hidden" <email@hidden>
Message-ID: <C948CD2F.3B7%email@hidden>
Content-Type: text/plain; charset="windows-1252"
I know this has been discussed in years past, sometimes with the
suggestion to wait for the next Xcode version, but it is still an
issue (for me).
In Xcode 3.2.5, I have a Cocoa app with a dependent Cocoa (sub)
project. In this case, the subproject is not a library but code for
what will be a set of parallel NSTask(s). Breakpoints I place in the
subproject do not trigger and I have been resorting to judicious, but
kludgy, NSLog() statements.
Is there a reliable way to get breakpoints to work in a subproject?
I have a second such project pair which is working as designed but
thought Id check again wrt the breakpoint issue.
Thanks in advance.
BTW, please do not suggest NSOperation(s). These do not work here
due to massive malloc contention due, in turn, to millions of vector
and matrix computations. I tried this route for a very long time
before giving up.
--
Mike McLaughlin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.apple.com/pipermail/xcode-users/attachments/
20110104/acf3887b/attachment.html
------------------------------
Message: 10
Date: Tue, 04 Jan 2011 11:16:39 -0800
From: Todd Heberlein <email@hidden>
Subject: ISO versions of open(), read(), lseek()
To: email@hidden
Message-ID: <email@hidden>
Content-Type: text/plain; CHARSET=US-ASCII
I have to maintain some C++ code between Xcode on a Mac and Visual
Studio on Windows, and the Windows compiler kindly encouraged me to
use the ISO versions of open(), read(), lseek() and so on (these are
_open(), _read(), _lseek() ... (and seem to be defined in io.h)). I
was looking for these library calls on the Mac and could not find them.
Are they there somewhere and I just couldn't find them?
If not, are the ISO calls in Apple's public (i.e., non-NDA) "to do"
list for future Xcode releases?
Thanks,
Todd
------------------------------
Message: 11
Date: Tue, 4 Jan 2011 14:32:12 -0500
From: Sherm Pendley <email@hidden>
Subject: Re: ISO versions of open(), read(), lseek()
To: Todd Heberlein <email@hidden>
Cc: email@hidden
Message-ID:
<AANLkTi=oQsx5jn=email@hidden>
Content-Type: text/plain; charset=ISO-8859-1
On Tue, Jan 4, 2011 at 2:16 PM, Todd Heberlein
<email@hidden> wrote:
I have to maintain some C++ code between Xcode on a Mac and Visual
Studio on Windows, and the Windows compiler kindly encouraged me to
use the ISO versions of open(), read(), lseek() and so on (these
are _open(), _read(), _lseek() ... (and seem to be defined in
io.h)). I was looking for these library calls on the Mac and could
not find them.
Are they there somewhere and I just couldn't find them?
I suspect you're looking at the wrong "open" man page. "man 2 open" is
the one you want, and indicates that open() is declared in fcntl.h.
"man 1 open" describes the shell command, not the C function.
sherm--
--
Cocoa programming in Perl:
http://camelbones.sourceforge.net
------------------------------
Message: 12
Date: Tue, 04 Jan 2011 19:38:01 +0000
From: Tom Seddon <email@hidden>
Subject: Re: ISO versions of open(), read(), lseek()
To: email@hidden
Message-ID: <email@hidden>
Content-Type: text/plain; charset=us-ascii
On Tue, 04 Jan 2011 11:16:39 -0800, Todd Heberlein
<email@hidden> wrote:
I have to maintain some C++ code between Xcode on a Mac and Visual
Studio on Windows, and the Windows compiler kindly encouraged me to
use the ISO versions of open(), read(), lseek() and so on (these
are _open(), _read(), _lseek() ... (and seem to be defined in
io.h)). I was looking for these library calls on the Mac and could
not find them.
Are they there somewhere and I just couldn't find them?
If not, are the ISO calls in Apple's public (i.e., non-NDA) "to do"
list for future Xcode releases?
I think what VC++ means by "ISO conformant" is that because they don't
support POSIX/Unix/etc., they don't pollute the global namespace with
their extra implementation-defined functions that happen to be a bit
like the POSIX/Unix/etc. equivalents. Instead, they include them with
the "_" prefix that the ISO standard reserves for this kind of thing.
Reasonable enough, but rather inconvenient :)
The easiest option is to get VC++ not to deprecate the unadorned
functions. Put this in your precompiled header:
#define _CRT_NONSTDC_NO_DEPRECATE
or set up "_CRT_NONSTDC_NO_DEPRECATE" as a #define in the Project
Settings.
This should then give you the POSIX/Unix/etc.-style functions under
their usual names. No underscores necessary!
--Tom
------------------------------
Message: 13
Date: Tue, 04 Jan 2011 14:57:01 -0800
From: Todd Heberlein <email@hidden>
Subject: Re: ISO versions of open(), read(), lseek()
To: Sherm Pendley <email@hidden>
Cc: email@hidden
Message-ID: <email@hidden>
Content-Type: text/plain; CHARSET=US-ASCII
On Jan 4, 2011, at 11:32 AM, Sherm Pendley wrote:
I suspect you're looking at the wrong "open" man page. "man 2 open" is
the one you want, and indicates that open() is declared in fcntl.h.
I am actually moving my code from Xcode is Visual Studio (I am
surprised at the overall similarity of the two development
environments), so my open() calls on Snow Leopard in Xcode are happy.
Interestingly, working with Win32 has forced me to think more about
UTF-16 file and directory names, so using things like _open() and its
sister function _wopen() makes some sense. I had not previously
thought about non-ASCII path names for file operations.
Todd
------------------------------
Message: 14
Date: Tue, 04 Jan 2011 15:00:43 -0800
From: Todd Heberlein <email@hidden>
Subject: Re: ISO versions of open(), read(), lseek()
To: Tom Seddon <email@hidden>
Cc: email@hidden
Message-ID: <email@hidden>
Content-Type: text/plain; charset="us-ascii"
The easiest option is to get VC++ not to deprecate the unadorned
functions. Put this in your precompiled header:
#define _CRT_NONSTDC_NO_DEPRECATE
Thanks.
With that as a starting point I ran across this web page. It might be
useful for others who need to take their Mac/Unix code to Windows.
Deprecated CRT Functions
Deprecated POSIX functions
http://msdn.microsoft.com/en-us/library/ms235384(VS.80).aspx
Todd
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.apple.com/pipermail/xcode-users/attachments/
20110104/d1e073fe/attachment.html
------------------------------
Message: 15
Date: Tue, 4 Jan 2011 23:09:35 +0000
From: Alastair Houghton <email@hidden>
Subject: Re: ISO versions of open(), read(), lseek()
To: Todd Heberlein <email@hidden>
Cc: email@hidden
Message-ID: <email@hidden>
Content-Type: text/plain; charset=us-ascii
On 4 Jan 2011, at 19:16, Todd Heberlein wrote:
I have to maintain some C++ code between Xcode on a Mac and Visual
Studio on Windows, and the Windows compiler kindly encouraged me to
use the ISO versions of open(), read(), lseek() and so on (these
are _open(), _read(), _lseek() ... (and seem to be defined in io.h)).
There's no such thing as "the ISO versions" of open(), read(), lseek
() et al. ISO (or in reality ANSI) doesn't define any of those
functions; POSIX does, but the versions included with Visual Studio
are not POSIX compliant (though they are similar and *mostly*
compatible if you're careful).
Prepending the underscores was a strange decision IMO; I don't think
they can really justify it from a compliance perspective (since the
presence of those functions in the standard library won't affect a
strictly compliant program that defines its own functions with
similar names---the linker simply won't link the library code in),
and it makes it harder to write portable programs because you end up
needing things like
#ifdef _WIN32
#define stat _stat
#endif
(*very* common in portable software).
Mac OS X, of course, is POSIX compliant (and has the certificate to
prove it).
Kind regards,
Alastair.
--
http://alastairs-place.net
------------------------------
_______________________________________________
Xcode-users mailing list
email@hidden
http://lists.apple.com/mailman/listinfo/xcode-users
End of Xcode-users Digest, Vol 8, Issue 2
***************************************** _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden