[missing-sync-palmos-dev-talk] Re: Can't debug

[Matt DeCaro]

That did it.  I am a worthless novice!  I was making changes from the  
info screen of the entire project, not the individual target.  I am  
truly grateful for your assistance.


On Sep 26, 2006, at 8:37 PM, Scott Gruby wrote:

>
> On Sep 26, 2006, at 5:08 PM, Matt DeCaro wrote:
>
>> I used the sample conduit directly from the web site.  I compiled  
>> it using xcode 2.4.  It does not debug.  When I do the deployment  
>> conduit I don't get the sheet indicating PPC, the development one  
>> does.
>
> There is your problem. You need to:
>
> a) Set Active Build Configuration to Development
> b) Turn down the triangle on Targets
> c) Click on SampleConduit
> d) Get Info on it (Command-I)
> e) Click the build tab
> f) Make sure Configuration says Development
> g) Look for Architectures
> h) Double click, Click Intel (uncheck PowerPC)
>
> You cannot debug a PowerPC conduit on Intel with Missing Sync, so  
> you must be building an Intel native conduit. Furthermore, you can  
> only debug the development build.
>
>> Neither version will debug.  I think I have tried every  
>> permutation without success.  I am at a complete loss.
>>
>> As I indicated, the cocoa version will debug.  I am not familiar  
>> with objective-C unfortunately.  I have a fairly new macbook  
>> (intel)  I do have codewarrior 8.2 installed.  Is this somehow  
>> affecting things?
>>
>>
>> On Sep 26, 2006, at 3:32 PM, Scott Gruby wrote:
>>
>>>
>>> On Sep 25, 2006, at 9:57 AM, Matthew DeCaro wrote:
>>>
>>>> Has  anyone else had a similar problem?  I have a MacBook  
>>>> Intel.  Loaded on the system is CodeWarrior 8.2 as well as tthe  
>>>> CDK 4.03, Palm Desktop and of course Missing Sync.
>>>>
>>>> Is there anyting I can send you from my system that would help  
>>>> you troubleshoot with me?
>>>>
>>>> I am sorry to be a pain, but I need to get this working!
>>>
>>> Sorry for the delayed response, but I just tested debugging a  
>>> Carbon conduit and it worked fine with the caveat that I had to  
>>> change the architecture (it was set to ppc and I'm on Intel). In  
>>> the SampleConduit (not the PowerPlant example), click on  
>>> SampleConduit, get info, from the configuration menu, choose  
>>> Development, select architecture and make sure it is set to the  
>>> correct value (Intel).
>>>
>>> If when trying to debug, you get a dialog saying that this  
>>> conduit wasn't designed to work on this system, then your conduit  
>>> is a PPC conduit running on Intel.
>>>
>>> I tried this with the PowerPlant Sample and it worked as well.
>>>
>>> I hope this helps.
>>>
>>>
>>>>
>>> --
>>> Scott Gruby
>>> Mark/Space, Inc.
>>> <http://www.markspace.com/>
>>>
>>> Please visit <http://www.markspace.com/support/> for assistance  
>>> with Mark/Space products.
>>>
>>>
>>> _______________________________________________
>>> missing-sync-palmos-dev-talk mailing list
>>> missing-sync-palmos-dev-talk at lists.markspace.com
>>> http://lists.markspace.com/mailman/listinfo/missing-sync-palmos- 
>>> dev-talk
>>
>>
>>
>> __________________
>> Matt DeCaro
>> mdecaro at comcast.net
>>
>>
>>
>> _______________________________________________
>> missing-sync-palmos-dev-talk mailing list
>> missing-sync-palmos-dev-talk at lists.markspace.com
>> http://lists.markspace.com/mailman/listinfo/missing-sync-palmos- 
>> dev-talk
>
>
> --
> Scott Gruby
> Mark/Space, Inc.
> <http://www.markspace.com/>
>
> Please visit <http://www.markspace.com/support/> for assistance  
> with Mark/Space products.
>
>
> _______________________________________________
> missing-sync-palmos-dev-talk mailing list
> missing-sync-palmos-dev-talk at lists.markspace.com
> http://lists.markspace.com/mailman/listinfo/missing-sync-palmos-dev- 
> talk



__________________
Matt DeCaro
mdecaro at comcast.net



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.markspace.com/pipermail/missing-sync-palmos-dev-talk/attachments/20060926/edd8a8e1/attachment-0001.html