Project Home
Project Home
Trackers
Trackers
Documents
Documents
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
BroadcastCommunity.qnx.com will be offline from May 31 6:00pm until June 2 12:00AM for upcoming system upgrades. For more information please go to https://community.qnx.com/sf/discussion/do/listPosts/projects.bazaar/discussion.bazaar.topc28418
Forum Topic - Problem upgrading project: (5 Items)
   
Problem upgrading project  
The project is from 6.3.2.  On a machine with only 6.4.0 on it I obtain the project from SVN.  I then edited our custom 
makefile to use 4.2.4 instead of -3.3.5. When I tried to build it qcc complain that it could find 4.2.4.

I check the project's setting it was showing TargetOS to be QNX6, Target CPUU to be X86 - Little Endian, Compierl GNU 
Compiler Collection 4.2.4 and run time to be default.  Everything was looking ok.

It's only when I changed the target CPU to arm and then back to X86 that is started working.  It seems the .cproject 
file got updated with the proper setting only when I made a change to the project.  

This is reproducible at will.
Re: Problem upgrading project  
Could you please send your makefile. If you can send unconverted 
project, it would be even better. As to the reported problem, it is not 
surprise for me. Some work should be done to clean up all around regular 
make projects.

On 05/01/2009 12:10 PM, Mario Charest wrote:
> The project is from 6.3.2.  On a machine with only 6.4.0 on it I obtain the project from SVN.  I then edited our 
custom makefile to use 4.2.4 instead of -3.3.5. When I tried to build it qcc complain that it could find 4.2.4.
>
> I check the project's setting it was showing TargetOS to be QNX6, Target CPUU to be X86 - Little Endian, Compierl GNU 
Compiler Collection 4.2.4 and run time to be default.  Everything was looking ok.
>
> It's only when I changed the target CPU to arm and then back to X86 that is started working.  It seems the .cproject 
file got updated with the proper setting only when I made a change to the project.
>
> This is reproducible at will.
>
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post19367
>
>    
RE: Problem upgrading project  

> -----Original Message-----
> From: Alex Chapiro [mailto:community-noreply@qnx.com]
> Sent: January-05-09 12:43 PM
> To: general-ide
> Subject: Re: Problem upgrading project
> 
> Could you please send your makefile. If you can send unconverted
> project, it would be even better. As to the reported problem, it is not
> surprise for me. Some work should be done to clean up all around
> regular
> make projects.

Not sure why you need the makefile.  I can send you the .cproject file just as the project is first open and the the .
cproject after I do the dummy change to the project's settings.

I thing the real bug is that the Project Settings will show the GNU Compiler Collection to be 4.2.4 even though it's set
 to 3.3.5 in the .cproject file.

> 
> On 05/01/2009 12:10 PM, Mario Charest wrote:
> > The project is from 6.3.2.  On a machine with only 6.4.0 on it I
> obtain the project from SVN.  I then edited our custom makefile to use
> 4.2.4 instead of -3.3.5. When I tried to build it qcc complain that it
> could find 4.2.4.
> >
> > I check the project's setting it was showing TargetOS to be QNX6,
> Target CPUU to be X86 - Little Endian, Compierl GNU Compiler Collection
> 4.2.4 and run time to be default.  Everything was looking ok.
> >
> > It's only when I changed the target CPU to arm and then back to X86
> that is started working.  It seems the .cproject file got updated with
> the proper setting only when I made a change to the project.
> >
> > This is reproducible at will.
> >
> > _______________________________________________
> > General
> > http://community.qnx.com/sf/go/post19367
> >
> >
> 
> 
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post19371
> 
Re: Problem upgrading project  
If you are using external builder, it uses Makefile and environment in 
order to build the project. Makefile does not depend on .cproject 
content (this is your creature).Environment matters if your makefile 
uses predefined macros such as CC, CCFLAGS etc., and it is generated 
using information about configuration, stored in .cproject. But you can 
verify environment looking to the project properties, cannot you?

On 05/01/2009 1:10 PM, Mario Charest wrote:
>    
>> -----Original Message-----
>> From: Alex Chapiro [mailto:community-noreply@qnx.com]
>> Sent: January-05-09 12:43 PM
>> To: general-ide
>> Subject: Re: Problem upgrading project
>>
>> Could you please send your makefile. If you can send unconverted
>> project, it would be even better. As to the reported problem, it is not
>> surprise for me. Some work should be done to clean up all around
>> regular
>> make projects.
>>      
>
> Not sure why you need the makefile.  I can send you the .cproject file just as the project is first open and the the .
cproject after I do the dummy change to the project's settings.
>
> I thing the real bug is that the Project Settings will show the GNU Compiler Collection to be 4.2.4 even though it's 
set to 3.3.5 in the .cproject file.
>
>    
>> On 05/01/2009 12:10 PM, Mario Charest wrote:
>>      
>>> The project is from 6.3.2.  On a machine with only 6.4.0 on it I
>>>        
>> obtain the project from SVN.  I then edited our custom makefile to use
>> 4.2.4 instead of -3.3.5. When I tried to build it qcc complain that it
>> could find 4.2.4.
>>      
>>> I check the project's setting it was showing TargetOS to be QNX6,
>>>        
>> Target CPUU to be X86 - Little Endian, Compierl GNU Compiler Collection
>> 4.2.4 and run time to be default.  Everything was looking ok.
>>      
>>> It's only when I changed the target CPU to arm and then back to X86
>>>        
>> that is started working.  It seems the .cproject file got updated with
>> the proper setting only when I made a change to the project.
>>      
>>> This is reproducible at will.
>>>
>>> _______________________________________________
>>> General
>>> http://community.qnx.com/sf/go/post19367
>>>
>>>
>>>        
>> _______________________________________________
>> General
>> http://community.qnx.com/sf/go/post19371
>>
>>      
>
>
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post19379
>
>    
RE: Problem upgrading project  

> -----Original Message-----
> From: Alex Chapiro [mailto:community-noreply@qnx.com]
> Sent: January-05-09 1:30 PM
> To: general-ide
> Subject: Re: Problem upgrading project
> 
> If you are using external builder, it uses Makefile and environment in
> order to build the project. Makefile does not depend on .cproject
> content (this is your creature).Environment matters if your makefile
> uses predefined macros such as CC, CCFLAGS etc., and it is generated
> using information about configuration, stored in .cproject. But you can
> verify environment looking to the project properties, cannot you?

I can see the environment (QCC_*) originally set for 3.3.5 but yet the Project Settings shows 4.2.4. Only when I do a 
dummy change to the Project Setting will QCC_*  be set to point to 4.2.4/6.4.0 stuff.

> 
> On 05/01/2009 1:10 PM, Mario Charest wrote:
> >
> >> -----Original Message-----
> >> From: Alex Chapiro [mailto:community-noreply@qnx.com]
> >> Sent: January-05-09 12:43 PM
> >> To: general-ide
> >> Subject: Re: Problem upgrading project
> >>
> >> Could you please send your makefile. If you can send unconverted
> >> project, it would be even better. As to the reported problem, it is
> not
> >> surprise for me. Some work should be done to clean up all around
> >> regular
> >> make projects.
> >>
> >
> > Not sure why you need the makefile.  I can send you the .cproject
> file just as the project is first open and the the .cproject after I do
> the dummy change to the project's settings.
> >
> > I thing the real bug is that the Project Settings will show the GNU
> Compiler Collection to be 4.2.4 even though it's set to 3.3.5 in the
> .cproject file.
> >
> >
> >> On 05/01/2009 12:10 PM, Mario Charest wrote:
> >>
> >>> The project is from 6.3.2.  On a machine with only 6.4.0 on it I
> >>>
> >> obtain the project from SVN.  I then edited our custom makefile to
> use
> >> 4.2.4 instead of -3.3.5. When I tried to build it qcc complain that
> it
> >> could find 4.2.4.
> >>
> >>> I check the project's setting it was showing TargetOS to be QNX6,
> >>>
> >> Target CPUU to be X86 - Little Endian, Compierl GNU Compiler
> Collection
> >> 4.2.4 and run time to be default.  Everything was looking ok.
> >>
> >>> It's only when I changed the target CPU to arm and then back to X86
> >>>
> >> that is started working.  It seems the .cproject file got updated
> with
> >> the proper setting only when I made a change to the project.
> >>
> >>> This is reproducible at will.
> >>>
> >>> _______________________________________________
> >>> General
> >>> http://community.qnx.com/sf/go/post19367
> >>>
> >>>
> >>>
> >> _______________________________________________
> >> General
> >> http://community.qnx.com/sf/go/post19371
> >>
> >>
> >
> >
> > _______________________________________________
> > General
> > http://community.qnx.com/sf/go/post19379
> >
> >
> 
> 
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post19386
>