TeamForge : Post

Forum Topic - invalid buildfile message when importing buildfile into IDE401 and IDE45: (4 Items)

View: as

Jeevan Mathew(deleted)

04/24/2008 5:07 AM

post7232

invalid buildfile message when importing buildfile into IDE401 and IDE45

Hi,

Can someone please explain why the buildfile (x86ph.build) attached to post5156 is 'invalid' for importing in the 
IDE[401 45] ?

It just builds fine from commandline selfhosted and windows hosted.

THX,
Jeevan

Jeevan Mathew(deleted)

04/24/2008 6:14 AM

post7235

Re: invalid buildfile message when importing buildfile into IDE401 and IDE45

> Hi,
> 
> Can someone please explain why the buildfile (x86ph.build) attached to 
> post5156 is 'invalid' for importing in the IDE[401 45] ?
> 
> It just builds fine from commandline selfhosted and windows hosted.
> 
> THX,
> Jeevan
> 
> 


Is it a problem with ${QNX_TARGET} string in the buildfile ?

I can import the default /boot/build/bios.build.

Jeevan

Alex Chapiro

04/24/2008 10:00 AM

post7238

Re: invalid buildfile message when importing buildfile into IDE40 1 and IDE45

This is because of "#//". Insert ' ' (space) after '#'. I found it long 
time ago but didn't fix it for the reason I don't remember now. Probably 
there is a PR opened about that, I just is very limited of time now to 
find it out.

Jeevan Mathew wrote:
>
> > Hi,
> >
> > Can someone please explain why the buildfile (x86ph.build) attached to
> > post5156 is 'invalid' for importing in the IDE[401 45] ?
> >
> > It just builds fine from commandline selfhosted and windows hosted.
> >
> > THX,
> > Jeevan
> >
> >
>
>
> Is it a problem with ${QNX_TARGET} string in the buildfile ?
>
> I can import the default /boot/build/bios.build.
>
> Jeevan
>
>
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post7235
>

Jeevan Mathew(deleted)

04/24/2008 10:41 AM

post7241

Re: invalid buildfile message when importing buildfile into IDE40 1 and IDE45

> This is because of "#//". Insert ' ' (space) after '#'. I found it long 
> time ago but didn't fix it for the reason I don't remember now. Probably 
> there is a PR opened about that, I just is very limited of time now to 
> find it out.
> 

Super Alex !

I will check  for an existing PR tomorrow, if not I will file one.

Jeevan

Return