Problem with bsh file

QNX Newsgroups (Archives) qnx.newuser
#1

I’ m trying evaluation version of QNX Momentics 6.3,
when i write bsh file with [script] or [virtual] and I use brace
the compiler do not work and generate text file signed with
various name.
They show that building stop when find a close brace },
but the image does not update.

Thanks, Any help would be appreciated

Walter

#2

Walter <wmiren@tin.it> wrote:

I’ m trying evaluation version of QNX Momentics 6.3,
when i write bsh file with [script] or [virtual] and I use brace
the compiler do not work and generate text file signed with
various name.
They show that building stop when find a close brace },
but the image does not update.

The contents of the “bsh” is what would normally be the
[+script] section of a build file for mkifs. The ide creates
a build file from the bsh and the other info provided on the
fly, runs mkifs on this build file, then deletes it.

So, in the bsh, you would only use modifiers that are allowed in
the [+script] section of a build file.

Other flags would be set through properties for your system builder
project.

Hope that clarifies things a bit.

-David

David Gibbs
QNX Training Services
dagibbs@qnx.com

#3

I have take the sample code below from the help guide
and I put it in the bsh file and when I build project it stop
at the first close brace }

[virtual=x86,bios] .bootstrap = {
startup-bios
PATH=/proc/boot procnto
}

[+script] .script = {
devc-con -n9 &
reopen /dev/con1
[+session] esh
}
libc.so
[data=copy]
devc-con
esh
[type=link] /usr/lib/ldqnx.so.2=/proc/boot/libc.so

I don’ t understand why, I think that this code is correct.

Thanks, any help would be appreciated

Walter

#4

Walter <wmiren@tin.it> wrote:

I have take the sample code below from the help guide
and I put it in the bsh file and when I build project it stop
at the first close brace }

Where did you find this in the helpfiles?

The following is, exactly what I described in my previous post as
a complete build file. You could pass it to mkifs at the command
line, but it is not a bsh part.

[virtual=x86,bios] .bootstrap = {
startup-bios
PATH=/proc/boot procnto
}

[+script] .script = {
Everything from here
devc-con -n9 &
reopen /dev/con1
[+session] esh

To here (3 lines) would be the contents of the bsh.

}
libc.so
[data=copy]
devc-con
esh
[type=link] /usr/lib/ldqnx.so.2=/proc/boot/libc.so

I don’ t understand why, I think that this code is correct.

Thanks, any help would be appreciated

Take the entire above contents, create a file on disk with it. Create a
new system builder project, and then “Import Existing Buildfile” in the
creation wizard, and select the file you wrote above.

Again, the bsh entry is ONLY the [+script] section of a complete
build file.

-David

David Gibbs
QNX Training Services
dagibbs@qnx.com

#5

Thank you a lot for your answer, I think I understand.
At the light of this, I read again the guide so my bad consideration
was that the bsh file was a buildfile, I think it isn’ t problem
because I work with Qnx only for few days.

Walter




“David Gibbs” <dagibbs@qnx.com> ha scritto nel messaggio
news:cl603h$mr$1@inn.qnx.com…

Walter <> wmiren@tin.it> > wrote:
I have take the sample code below from the help guide
and I put it in the bsh file and when I build project it stop
at the first close brace }

Where did you find this in the helpfiles?

The following is, exactly what I described in my previous post as
a complete build file. You could pass it to mkifs at the command
line, but it is not a bsh part.

[virtual=x86,bios] .bootstrap = {
startup-bios
PATH=/proc/boot procnto
}

[+script] .script = {
Everything from here
devc-con -n9 &
reopen /dev/con1
[+session] esh

To here (3 lines) would be the contents of the bsh.

}
libc.so
[data=copy]
devc-con
esh
[type=link] /usr/lib/ldqnx.so.2=/proc/boot/libc.so

I don’ t understand why, I think that this code is correct.

Thanks, any help would be appreciated

Take the entire above contents, create a file on disk with it. Create a
new system builder project, and then “Import Existing Buildfile” in the
creation wizard, and select the file you wrote above.

Again, the bsh entry is ONLY the [+script] section of a complete
build file.

-David

David Gibbs
QNX Training Services
dagibbs@qnx.com