|
Gervais Mulongoy
09/14/2009 1:39 PM
post37925
|
Hello:
I built a boot image for x86 based on bios.build from the IDE and one from the command line utility (mkifs). The cli
version worked fine, but the version from the IDE did not. Lots of dots with a big S at the end (missing OS signature).
Any ideas why the IDE might be failing here? Is this a known bug, or am I missing some obvious GUI option?
Thanks
|
|
|
|
|
|
Christian Damus(deleted)
09/14/2009 2:36 PM
post37933
|
Hi, Gervais,
Where do you see the dots with the big S at the end? In the IDE's build
console, or is that what the contents of the image file look like?
Do you see any errors or warnings printed in the build console?
How did you create the System Builder project? If you import the build
file that works with command-line mkifs, how does the resulting System
Builder project compare to the project that doesn't work?
Cheers,
Christian
On Mon, 2009-09-14 at 13:39 -0400, Gervais Mulongoy wrote:
> Hello:
>
> I built a boot image for x86 based on bios.build from the IDE and one from the command line utility (mkifs). The cli
version worked fine, but the version from the IDE did not. Lots of dots with a big S at the end (missing OS signature).
>
> Any ideas why the IDE might be failing here? Is this a known bug, or am I missing some obvious GUI option?
>
> Thanks
>
>
>
> _______________________________________________
>
> General
> http://community.qnx.com/sf/go/post37925
>
|
|
|
|
|
|
Gervais Mulongoy
09/14/2009 2:58 PM
post37939
|
Hello Christian:
I saw the dots when I tried to boot my system using the image built
using the IDE. The IDE didn't indicate any errors, I only noticed this
when I tried to use the image. The IDE appeared to have worked without
issue.
The only comparaison I made between the cli and the ide images was
trying to boot from them. I have not distinguished them in any other
way. My assumption at this point is that the IDE uses a different set of
tools to prepare the boot images and in the case of the bios.build that
I tried it seemed to have not worked in the same way as the mkifs
counter-part.
Thanks,
Gervais
-----Original Message-----
From: Christian Damus [mailto:community-noreply@qnx.com]
Sent: September 14, 2009 2:37 PM
To: general-ide
Subject: Re: making a boot image
Hi, Gervais,
Where do you see the dots with the big S at the end? In the IDE's build
console, or is that what the contents of the image file look like?
Do you see any errors or warnings printed in the build console?
How did you create the System Builder project? If you import the build
file that works with command-line mkifs, how does the resulting System
Builder project compare to the project that doesn't work?
Cheers,
Christian
On Mon, 2009-09-14 at 13:39 -0400, Gervais Mulongoy wrote:
> Hello:
>
> I built a boot image for x86 based on bios.build from the IDE and one
from the command line utility (mkifs). The cli version worked fine, but
the version from the IDE did not. Lots of dots with a big S at the end
(missing OS signature).
>
> Any ideas why the IDE might be failing here? Is this a known bug, or
am I missing some obvious GUI option?
>
> Thanks
>
>
>
> _______________________________________________
>
> General
> http://community.qnx.com/sf/go/post37925
>
_______________________________________________
General
http://community.qnx.com/sf/go/post37933
|
|
|
|
|
|
Christian Damus(deleted)
09/14/2009 3:04 PM
post37942
|
Hi, Gervais,
If you export a mkifs build file from your IDE project, how does it
compare with the build file that generates the correct result using the
mkifs tool? I ask because there are some known issues in the IDE's
generation of build files (it just runs mkifs and other tools under the
hood). For example, it doesn't generate XIP settings for code/data.
The IDE will use the same tools that you are using on the command-line
if you haven't set it to select a different SDP version in the "QNX"
preference page.
Cheers,
Christian
On Mon, 2009-09-14 at 14:58 -0400, Gervais Mulongoy wrote:
> Hello Christian:
>
> I saw the dots when I tried to boot my system using the image built
> using the IDE. The IDE didn't indicate any errors, I only noticed this
> when I tried to use the image. The IDE appeared to have worked without
> issue.
>
> The only comparaison I made between the cli and the ide images was
> trying to boot from them. I have not distinguished them in any other
> way. My assumption at this point is that the IDE uses a different set of
> tools to prepare the boot images and in the case of the bios.build that
> I tried it seemed to have not worked in the same way as the mkifs
> counter-part.
>
> Thanks,
>
> Gervais
>
> -----Original Message-----
|
|
|
|
|
|
Gervais Mulongoy
09/14/2009 3:20 PM
post37945
|
The images have different sizes. The IDE version is smaller. I tried
running dumpifs -m on the IDE version and it just hung. Works fine with
the cli version.
Gervais
-----Original Message-----
From: Christian Damus [mailto:community-noreply@qnx.com]
Sent: September 14, 2009 3:05 PM
To: general-ide
Subject: RE: making a boot image
Hi, Gervais,
If you export a mkifs build file from your IDE project, how does it
compare with the build file that generates the correct result using the
mkifs tool? I ask because there are some known issues in the IDE's
generation of build files (it just runs mkifs and other tools under the
hood). For example, it doesn't generate XIP settings for code/data.
The IDE will use the same tools that you are using on the command-line
if you haven't set it to select a different SDP version in the "QNX"
preference page.
Cheers,
Christian
On Mon, 2009-09-14 at 14:58 -0400, Gervais Mulongoy wrote:
> Hello Christian:
>
> I saw the dots when I tried to boot my system using the image built
> using the IDE. The IDE didn't indicate any errors, I only noticed this
> when I tried to use the image. The IDE appeared to have worked without
> issue.
>
> The only comparaison I made between the cli and the ide images was
> trying to boot from them. I have not distinguished them in any other
> way. My assumption at this point is that the IDE uses a different set
> of tools to prepare the boot images and in the case of the bios.build
> that I tried it seemed to have not worked in the same way as the mkifs
> counter-part.
>
> Thanks,
>
> Gervais
>
> -----Original Message-----
_______________________________________________
General
http://community.qnx.com/sf/go/post37942
|
|
|
|
|
|
David Sarrazin
09/14/2009 3:28 PM
post37951
|
Gervais,
You should actually be able to look at the source file that the IDE
passes to mkifs, and compare that to your cmd-line version. I think
that's what Christian was thinking of with the "export" comment.
David
> -----Original Message-----
> From: Gervais Mulongoy [mailto:community-noreply@qnx.com]
> Sent: September 14, 2009 3:21 PM
> To: general-ide
> Subject: RE: making a boot image
>
> The images have different sizes. The IDE version is smaller.
> I tried running dumpifs -m on the IDE version and it just
> hung. Works fine with the cli version.
>
> Gervais
>
> -----Original Message-----
> From: Christian Damus [mailto:community-noreply@qnx.com]
> Sent: September 14, 2009 3:05 PM
> To: general-ide
> Subject: RE: making a boot image
>
> Hi, Gervais,
>
> If you export a mkifs build file from your IDE project, how
> does it compare with the build file that generates the
> correct result using the mkifs tool? I ask because there are
> some known issues in the IDE's generation of build files (it
> just runs mkifs and other tools under the hood). For
> example, it doesn't generate XIP settings for code/data.
>
> The IDE will use the same tools that you are using on the
> command-line if you haven't set it to select a different SDP
> version in the "QNX"
> preference page.
>
> Cheers,
>
> Christian
>
>
> On Mon, 2009-09-14 at 14:58 -0400, Gervais Mulongoy wrote:
>
> > Hello Christian:
> >
> > I saw the dots when I tried to boot my system using the image built
> > using the IDE. The IDE didn't indicate any errors, I only
> noticed this
>
> > when I tried to use the image. The IDE appeared to have
> worked without
>
> > issue.
> >
> > The only comparaison I made between the cli and the ide images was
> > trying to boot from them. I have not distinguished them in
> any other
> > way. My assumption at this point is that the IDE uses a
> different set
> > of tools to prepare the boot images and in the case of the
> bios.build
> > that I tried it seemed to have not worked in the same way
> as the mkifs
>
> > counter-part.
> >
> > Thanks,
> >
> > Gervais
> >
> > -----Original Message-----
>
>
>
>
>
>
> _______________________________________________
>
> General
> http://community.qnx.com/sf/go/post37942
>
>
>
>
> _______________________________________________
>
> General
> http://community.qnx.com/sf/go/post37945
>
>
|
|
|
|
|
|
Gervais Mulongoy
09/14/2009 3:49 PM
post37954
|
The exported file is much of the sameness as the original build file. A
few, what appear to be, minor differences:
Exported file Original file
[virtual=x86,bios]
[compress=3] instead of [virtual=x86,bios + compress]
The startup script name is different:
.script instead of startup-script
Explicit permissions in the exported file where the original was
implied:
[dperms=0777 uid=0 gid=0]
[type=link] /tmp = /dev/shmem
[perms=0777]
Keyword expansion:
[data=copy] instead of [data=c]
Note: I didn't diff the files, just used my programmer goggles.
I built the exported file using mkifs and was able to boot from it.
Thanks,
Gervais
-----Original Message-----
From: David Sarrazin [mailto:community-noreply@qnx.com]
Sent: September 14, 2009 3:29 PM
To: general-ide
Subject: RE: making a boot image
Gervais,
You should actually be able to look at the source file that the IDE
passes to mkifs, and compare that to your cmd-line version. I think
that's what Christian was thinking of with the "export" comment.
David
> -----Original Message-----
> From: Gervais Mulongoy [mailto:community-noreply@qnx.com]
> Sent: September 14, 2009 3:21 PM
> To: general-ide
> Subject: RE: making a boot image
>
> The images have different sizes. The IDE version is smaller.
> I tried running dumpifs -m on the IDE version and it just hung. Works
> fine with the cli version.
>
> Gervais
>
> -----Original Message-----
> From: Christian Damus [mailto:community-noreply@qnx.com]
> Sent: September 14, 2009 3:05 PM
> To: general-ide
> Subject: RE: making a boot image
>
> Hi, Gervais,
>
> If you export a mkifs build file from your IDE project, how does it
> compare with the build file that generates the correct result using
> the mkifs tool? I ask because there are some known issues in the
> IDE's generation of build files (it just runs mkifs and other tools
> under the hood). For example, it doesn't generate XIP settings for
> code/data.
>
> The IDE will use the same tools that you are using on the command-line
> if you haven't set it to select a different SDP version in the "QNX"
> preference page.
>
> Cheers,
>
> Christian
>
>
> On Mon, 2009-09-14 at 14:58 -0400, Gervais Mulongoy wrote:
>
> > Hello Christian:
> >
> > I saw the dots when I tried to boot my system using the image built
> > using the IDE. The IDE didn't indicate any errors, I only
> noticed this
>
> > when I tried to use the image. The IDE appeared to have
> worked without
>
> > issue.
> >
> > The only comparaison I made between the cli and the ide images was
> > trying to boot from them. I have not distinguished them in
> any other
> > way. My assumption at this point is that the IDE uses a
> different set
> > of tools to prepare the boot images and in the case of the
> bios.build
> > that I tried it seemed to have not worked in the same way
> as the mkifs
>
> > counter-part.
> >
> > Thanks,
> >
> > Gervais
> >
> > -----Original Message-----
>
>
>
>
>
>
> _______________________________________________
>
> General
> http://community.qnx.com/sf/go/post37942
>
>
>
>
> _______________________________________________
>
> General
> http://community.qnx.com/sf/go/post37945
>
>
_______________________________________________
General
http://community.qnx.com/sf/go/post37951
|
|
|
|
|
|
Christian Damus(deleted)
09/14/2009 4:29 PM
post37959
|
Hi, Gervais,
If you can use mkifs to build a viable image from the exported
buildfile, then perhaps the issue is in either the post-processing steps
performed by the IDE or in the version of the SDP tools that it is
targeting. None of these differences are significant.
Are you doing any post-processing? (e.g., combining with other images)
Is your IDE targeting the same SDP install as your command-line
environment? (qconfig variables)
cW
On Mon, 2009-09-14 at 15:49 -0400, Gervais Mulongoy wrote:
> The exported file is much of the sameness as the original build file. A
> few, what appear to be, minor differences:
>
> Exported file Original file
> [virtual=x86,bios]
> [compress=3] instead of [virtual=x86,bios + compress]
>
> The startup script name is different:
> .script instead of startup-script
>
> Explicit permissions in the exported file where the original was
> implied:
> [dperms=0777 uid=0 gid=0]
> [type=link] /tmp = /dev/shmem
>
> [perms=0777]
>
> Keyword expansion:
> [data=copy] instead of [data=c]
>
> Note: I didn't diff the files, just used my programmer goggles.
>
> I built the exported file using mkifs and was able to boot from it.
>
> Thanks,
>
> Gervais
>
> -----Original Message-----
--------8<--------
|
|
|
|
|
|
Gervais Mulongoy
09/15/2009 9:25 AM
post37982
|
Hello Christian:
No I am not doing any post-processing and my IDE is targeting the same
version of the SDP install as my command-line environment.
Thanks,
Gervais
-----Original Message-----
From: Christian Damus [mailto:community-noreply@qnx.com]
Sent: September 14, 2009 4:30 PM
To: general-ide
Subject: RE: making a boot image
Hi, Gervais,
If you can use mkifs to build a viable image from the exported
buildfile, then perhaps the issue is in either the post-processing steps
performed by the IDE or in the version of the SDP tools that it is
targeting. None of these differences are significant.
Are you doing any post-processing? (e.g., combining with other images)
Is your IDE targeting the same SDP install as your command-line
environment? (qconfig variables)
cW
On Mon, 2009-09-14 at 15:49 -0400, Gervais Mulongoy wrote:
> The exported file is much of the sameness as the original build file.
> A few, what appear to be, minor differences:
>
> Exported file Original file
> [virtual=x86,bios]
> [compress=3] instead of [virtual=x86,bios + compress]
>
> The startup script name is different:
> .script instead of startup-script
>
> Explicit permissions in the exported file where the original was
> implied:
> [dperms=0777 uid=0 gid=0]
> [type=link] /tmp = /dev/shmem
>
> [perms=0777]
>
> Keyword expansion:
> [data=copy] instead of [data=c]
>
> Note: I didn't diff the files, just used my programmer goggles.
>
> I built the exported file using mkifs and was able to boot from it.
>
> Thanks,
>
> Gervais
>
> -----Original Message-----
--------8<--------
_______________________________________________
General
http://community.qnx.com/sf/go/post37959
|
|
|
|
|
|
Christian Damus(deleted)
09/15/2009 9:31 AM
post37983
|
Hi, Gervais,
Hmmm ... this sounds, then, like a problem that I should be able to
reproduce to debug it. Can you please raise a PR and attach your
project to it?
Thanks,
Christian
On Tue, 2009-09-15 at 09:26 -0400, Gervais Mulongoy wrote:
> Hello Christian:
>
> No I am not doing any post-processing and my IDE is targeting the same
> version of the SDP install as my command-line environment.
>
> Thanks,
>
> Gervais
>
--------8<--------
|
|
|
|
|
|
