Does it come with the free download? All the tools with the free download
seem to only run under QNX.
I want a way to use cc and c++ and other gnu tools from my windows
workstation. This way I can use SlickEdit along with the gnu tools and have
a windows based cross-platform development station.
What do I need to do this?
“Chris Rose” <chris.rose@viasat.com> wrote in message
news:9vl0lb$1jo$1@inn.qnx.com…
Does it come with the free download?
No
All the tools with the free download seem to only run under QNX.
That is the case
I want a way to use cc and c++ and other gnu tools from my windows
workstation.
In some cases you need more then gnu tools to build an executable.
This way I can use SlickEdit along with the gnu tools and have
a windows based cross-platform development station.What do I need to do this?
What about installing Samba on the QNX machine to give you access
to your files from Windows. You can then compile from a telnet
session. Or other way around keep you file on Windows and
have QNX access them (that will result in slow compilation though)
\
Is this what purchasing a development seat buys you (besides the obvious
legality for fielding commercial products and QSSL support)?
In otherwords, do I only get the Windows SDK when a development seat is
purchased?
“Mario Charest” <mcharest@clipzinformatic.com> wrote in message
news:9vl2a2$2pe$1@inn.qnx.com…
“Chris Rose” <> chris.rose@viasat.com> > wrote in message
news:9vl0lb$1jo$> 1@inn.qnx.com> …
Does it come with the free download?No
All the tools with the free download seem to only run under QNX.
That is the case
I want a way to use cc and c++ and other gnu tools from my windows
workstation.In some cases you need more then gnu tools to build an executable.
This way I can use SlickEdit along with the gnu tools and have
a windows based cross-platform development station.What do I need to do this?
What about installing Samba on the QNX machine to give you access
to your files from Windows. You can then compile from a telnet
session. Or other way around keep you file on Windows and
have QNX access them (that will result in slow compilation though)
\
“Chris Rose” <chris.rose@viasat.com> wrote in message
news:9vl3g3$3e0$1@inn.qnx.com…
Is this what purchasing a development seat buys you (besides the obvious
legality for fielding commercial products and QSSL support)?
In otherwords, do I only get the Windows SDK when a development seat is
purchased?
There are three development environment available. QNX6 (self hosted),
Windows and Solaris.
From what I know (never used Windows or Solaris) they have the
same capability.
“Mario Charest” <> mcharest@clipzinformatic.com> > wrote in message
news:9vl2a2$2pe$> 1@inn.qnx.com> …“Chris Rose” <> chris.rose@viasat.com> > wrote in message
news:9vl0lb$1jo$> 1@inn.qnx.com> …
Does it come with the free download?No
All the tools with the free download seem to only run under QNX.
That is the case
I want a way to use cc and c++ and other gnu tools from my windows
workstation.In some cases you need more then gnu tools to build an executable.
This way I can use SlickEdit along with the gnu tools and have
a windows based cross-platform development station.What do I need to do this?
What about installing Samba on the QNX machine to give you access
to your files from Windows. You can then compile from a telnet
session. Or other way around keep you file on Windows and
have QNX access them (that will result in slow compilation though)
\
Chris Rose <chris.rose@viasat.com> wrote:
Hi Chris,
Is this what purchasing a development seat buys you (besides the obvious
legality for fielding commercial products and QSSL support)?
In otherwords, do I only get the Windows SDK when a development seat is
purchased?
Please contact our sales rep or please feel free to call our customer
service line at 1-800-363-9001. Also you can visit our customer service
web site at:
http://www.qnx.com/support/csupport.html
Best Regards,
Marcin
“Mario Charest” <> mcharest@clipzinformatic.com> > wrote in message
news:9vl2a2$2pe$> 1@inn.qnx.com> …“Chris Rose” <> chris.rose@viasat.com> > wrote in message
news:9vl0lb$1jo$> 1@inn.qnx.com> …
Does it come with the free download?No
All the tools with the free download seem to only run under QNX.
That is the case
I want a way to use cc and c++ and other gnu tools from my windows
workstation.In some cases you need more then gnu tools to build an executable.
This way I can use SlickEdit along with the gnu tools and have
a windows based cross-platform development station.What do I need to do this?
What about installing Samba on the QNX machine to give you access
to your files from Windows. You can then compile from a telnet
session. Or other way around keep you file on Windows and
have QNX access them (that will result in slow compilation though)
\
IMHO, Chris is asking a very interesting question.
With cross tools the infrastucture is simpler.
You don’t need QNX machines and network and hence don’t bother how to admin.
it.
Though you still need your target machines.
So, I’d also like to listen to someone, who had some real experience
in QNX cross platform development for windows because the QSSL
explanations sometimes are a bit vague.
For example Mario mentioned that “In some cases you need more then gnu tools
to build an executable”
I guess he should have talked about utils like mkifs.
It sound strange. Does it mean that cross dev. tools lack some important
instruments in order
to build a target? Like you got only gnu tools and libraries?
And in fact, you’ve got to buy both native and cross dev tools
to have fully functional cross development environment?
Could anyone list cons and pros of native and cross development approaches?
chees,
Igor
“Igor Levko” <i_levko@hotmail.com> wrote in message
news:9vnn54$h5$1@inn.qnx.com…
IMHO, Chris is asking a very interesting question.
With cross tools the infrastucture is simpler.
You don’t need QNX machines and network and hence don’t bother how to
admin.
it.
Though you still need your target machines.So, I’d also like to listen to someone, who had some real experience
in QNX cross platform development for windows because the QSSL
explanations sometimes are a bit vague.For example Mario mentioned that “In some cases you need more then gnu
tools
to build an executable”
I guess he should have talked about utils like mkifs.
It sound strange. Does it mean that cross dev. tools lack some important
instruments in order to build a target?
These tools comes with the SDK, but the origninal posters specified
requirement for free development kit based on GNU. I was attempting
to point out that one could probably port the GNU tool kit to
Windows (keeping things free). However QNX specific tools can’t
be ported since the source aren’t available. So unlike the QNX 6 self
hosted development the cross development isn’t available for free for
non-commercial use.
Like you got only gnu tools and libraries?
And in fact, you’ve got to buy both native and cross dev tools
to have fully functional cross development environment?
I do not know. I imagine not.
- Mario
On Tue, 18 Dec 2001 10:27:44 -0500, “Igor Levko” <i_levko@hotmail.com> wrote:
IMHO, Chris is asking a very interesting question.
With cross tools the infrastucture is simpler.
You don’t need QNX machines and network and hence don’t bother how to admin.
it.
Though you still need your target machines.So, I’d also like to listen to someone, who had some real experience
in QNX cross platform development for windows because the QSSL
explanations sometimes are a bit vague.For example Mario mentioned that “In some cases you need more then gnu tools
to build an executable”
I guess he should have talked about utils like mkifs.
It sound strange. Does it mean that cross dev. tools lack some important
instruments in order
to build a target? Like you got only gnu tools and libraries?
And in fact, you’ve got to buy both native and cross dev tools
to have fully functional cross development environment?
No, the Windows hosted SDK has everything you need to develop.
It’s almost equivalent to the selfhosted, but some pieces will be available soon (e.g. DDD).
When done, it will be equivalent.
The price is the same.