Re: Xcode-users Digest, Vol 10, Issue 144
Re: Xcode-users Digest, Vol 10, Issue 144
- Subject: Re: Xcode-users Digest, Vol 10, Issue 144
- From: Steven Fransen <email@hidden>
- Date: Tue, 14 May 2013 02:24:37 +0000
- Thread-topic: Xcode-users Digest, Vol 10, Issue 144
the project is in your project file.
look at both the target and Project level
you have it set to auto and only have a expired one in your folder or you have it hard code to a provision file that is expired or it is set to Distribution or Developer and building the other config.
On May 13, 2013, at 12:00 PM, email@hidden wrote:
> Send Xcode-users mailing list submissions to
> email@hidden
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://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. Re: instruments stall (Ken Thomases)
> 2. Re: Unable to compile Cocoa/Objective-C program to C++
> (Dan Treiman)
> 3. Provisioning Profile Expiring (David Delmonte)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 12 May 2013 14:10:52 -0500
> From: Ken Thomases <email@hidden>
> To: Scott Ribe <email@hidden>
> Cc: "email@hidden list" <email@hidden>
> Subject: Re: instruments stall
> Message-ID: <email@hidden>
> Content-Type: text/plain; charset=windows-1252
>
> On May 12, 2013, at 9:10 AM, Scott Ribe wrote:
>
>> So I was trying to run a command-line tool with the leaks tool, and after just a few seconds of operation it stalled. I actually thought Instruments was somehow configured to only record/run for a short length of time, and spent a while trying to find that non-existant pref ;-)
>>
>> Long story made short, I eventually thought to sample my process while it was stalled under Instruments, and that showed the problem: …
>
>> Yep, lots of debug info onto std::clog, apparently nothing reading that pipe, so as soon as the buffer is full, the process is blocked. I removed my verbose switch, and the test ran to completion just fine. (And no leaks!)
>>
>> Thing is, this is Xcode 3.2.6--still stuck in the past thanks to support of old systems--my questions:
>>
>> - Is there any way to view the output while running my process under Instruments? I wanted to do that anyway, regardless of this issue.
>
> There's a console view in the detail view. It's one of the choices in the pop-up in the "breadcrumb" path control (other choices are Statistics, Sample List, Call Trees, etc.).
>
> Also, you can run the "instruments" command-line tool rather than the GUI app.
>
> Regards,
> Ken
>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Sun, 12 May 2013 15:48:02 -0500
> From: Dan Treiman <email@hidden>
> To: email@hidden
> Subject: Re: Unable to compile Cocoa/Objective-C program to C++
> Message-ID: <email@hidden>
> Content-Type: text/plain; charset=us-ascii
>
> This is a bit of a shot in the dark, but are you by any chance including a C++ header in your Objective-C++ header file? This would account for the error you are seeing.
>
> Here is a typical pattern: ObjC.m includes ObjC++.h. ( ObjC++.mm also includes ObjC++.h ). ObjC++.h must contain obnly Objective-C since it will be included by an Objective-C class. If you use any C++ types in ObjC++.h, compilation of ObjC.m will fail, so you need to completely encapsulate all of your C++ code within .mm files.
>
> Hope this helps. If not, maybe send some of your code?
>
> - Dan Treiman
>
>
> On May 12, 2013, at 12:06 PM, Paul Johnson <email@hidden> wrote:
>
>> I am able to compile my one Objective-C++ file as Objective-C++. (I
>> selected the Build Phases tab for the project I expanded the Compile
>> Sources section and on the line for the Objective-C++ file I added in
>> the Compiler Flags column: '-x objective-c++'.
>>
>> When I do this, this compiler is called twice, one to compile the
>> Objective-C file and one to compile the Objective-C++ file.
>>
>> I'm still getting a fatal compile error in one of the header files
>> #included in the 3rd party software though.
>>
>> (If I compile the Objective-C++ file, by a calling clang in Terminal,
>> I can compile the Objective-C++ file with just one warning message, so
>> I'm definitely getting closer to solving this problem.)
>>
>> On Sun, May 12, 2013 at 11:03 AM, Paul Johnson <email@hidden> wrote:
>>> In my Cocoa/Objective-C program I'm trying to access 3rd party
>>> software written in C++.
>>>
>>> I'm trying to use Objective-C++ to accomplish this but it appears that
>>> Xcode is not recognizing the file where I call the C++ as having been
>>> written in Objective-C++. (The long compiler command contains '-x
>>> objective-c'.) I've renamed the file to give it a .mm extension, which
>>> is the extension used for Objective-C++ files, and I've also set the
>>> File Type to 'Default- Objective-C++' in the Identity and Type section
>>> of the File Inspector. I also removed the Objective-C++ file from my
>>> project and reinserted it.)
>>>
>>> I #include one header from the 3rd party software and have one line
>>> that calls the software to instantiate a C++ object there. This header
>>> file references other header files and one of them has the line
>>> '#include <string>'. The compiler complains that it can't find the
>>> file 'string'.
>>>
>>> I used the 'locate' command in Terminal to find the 'string' file, and
>>> found two occurrences, one at /usr/include/c++/4.2.1/string and
>>> another at /usr/lib/c++/v1/string.
>>>
>>> I've tried adding /usr/include/c++/4.2.1 to the HEADER_SEARCH_PATHS in
>>> Xcode but get lots of additional compile errors.
>>>
>>> Can someone help me with this issue with calling C++?
>> _______________________________________________
>> 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
>
>
>
>
> ------------------------------
>
> Message: 3
> Date: Mon, 13 May 2013 11:23:09 +0300
> From: David Delmonte <email@hidden>
> To: "email@hidden List" <email@hidden>
> Subject: Provisioning Profile Expiring
> Message-ID: <email@hidden>
> Content-Type: text/plain; charset=us-ascii
>
> I'm getting this warning in my project: "Target Integrity: Provisioning profile is expiring". However, when I look at the Provisioning section of developer.apple.com >
> Member Center > Certificates, Identifiers and Profiles, the project profile has an expiration date 4 months from now. Should I be looking elsewhere?
>
> Thanks
>
>
>
>
>
>
> ------------------------------
>
> _______________________________________________
> Xcode-users mailing list
> email@hidden
> https://lists.apple.com/mailman/listinfo/xcode-users
>
> End of Xcode-users Digest, Vol 10, Issue 144
> ********************************************
_______________________________________________
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