Windows dev tools (non MW)

QNX Newsgroups (Archives) qdn.public.qnxrtp.devtools
1

Should it be possible to edit, debug compile a Photon GUI app
from Windows. I saw Cygnus mentioned in a related thread somewhere.
The idea would be to develop the initial GUI using PhAB (self hosted),
but to do all editing, compiling and debugging from the comfort of
the customer’s MS Windows.

Anyone attempt this?
Any reason why this shouldn’t work?

(The reason for the above is to avoid having to purchase the
Metrowerks tools on top of PhAB, and still have the benefit
of Windows cross development.)

2

Why not use Phindows ? I have never used it (since “comfortable
windows” is an oxymoron IMO), but one computational deviant with whom I
used to work, used Phindows for xdev, and other than the regular Windows
crashes it seemed to work well.

-----Original Message-----
From: Alex [mailto:acellarius@systems104.co.za]
Posted At: Wednesday, May 02, 2001 7:44 AM
Posted To: devtools
Conversation: Windows dev tools (non MW)
Subject: Windows dev tools (non MW)


Should it be possible to edit, debug compile a Photon GUI app
from Windows. I saw Cygnus mentioned in a related thread somewhere.
The idea would be to develop the initial GUI using PhAB (self hosted),
but to do all editing, compiling and debugging from the comfort of
the customer’s MS Windows.

Anyone attempt this?
Any reason why this shouldn’t work?

(The reason for the above is to avoid having to purchase the
Metrowerks tools on top of PhAB, and still have the benefit
of Windows cross development.)

3

Doesn’t Phindows accomplish this?

“Alex” <acellarius@systems104.co.za> wrote in message
news:3AF03949.269A7F4@systems104.co.za…

Should it be possible to edit, debug compile a Photon GUI app
from Windows. I saw Cygnus mentioned in a related thread somewhere.
The idea would be to develop the initial GUI using PhAB (self hosted),
but to do all editing, compiling and debugging from the comfort of
the customer’s MS Windows.

Anyone attempt this?
Any reason why this shouldn’t work?

(The reason for the above is to avoid having to purchase the
Metrowerks tools on top of PhAB, and still have the benefit
of Windows cross development.)

4

Phindows is just a window on the QNX box.
I’m thinking of the GNU toolchain hosted on the windows box.
Also a Windows based graphical front end on GDB
(Insight? DDD?)

So I’m really thinking Metrowerks at $0 :^)

The customer doesn’t like the standard editors shipped with
QNX. Would also like to cross develop from Windows.

The alternative they are considering is NT Embedded, as then
they can use all the familiar editors, compilers & debuggers /IDE
(Delphi).

The QNX 6 environment is too much of a learning curce.
SO I am trying to configure a cheaper development environment,
that is close as possible to the Windows environment.

MW obviously offers this, but there is a price tag attached to
this combo. One has to purchase both the QNX dev CD as well as the
MW tools.

Marty Doane wrote:

Doesn’t Phindows accomplish this?

“Alex” <> acellarius@systems104.co.za> > wrote in message
news:> 3AF03949.269A7F4@systems104.co.za> …
Should it be possible to edit, debug compile a Photon GUI app
from Windows. I saw Cygnus mentioned in a related thread somewhere.
The idea would be to develop the initial GUI using PhAB (self hosted),
but to do all editing, compiling and debugging from the comfort of
the customer’s MS Windows.

Anyone attempt this?
Any reason why this shouldn’t work?

(The reason for the above is to avoid having to purchase the
Metrowerks tools on top of PhAB, and still have the benefit
of Windows cross development.)

5

Alex wrote:

Phindows is just a window on the QNX box.
I’m thinking of the GNU toolchain hosted on the windows box.
Also a Windows based graphical front end on GDB
(Insight? DDD?)

So I’m really thinking Metrowerks at $0 :^)

The customer doesn’t like the standard editors shipped with
QNX. Would also like to cross develop from Windows.

The alternative they are considering is NT Embedded, as then
they can use all the familiar editors, compilers & debuggers /IDE
(Delphi).

I suppose those familiar tools/IDE are free, right?
Anyway, if they are about commercial development, they’d have to buy
commercial license no matter what. For a reasonable price if they join
one of developer programs.

There’s no big deal to hack a windows based environment without buying
MW, but you still need libraries and headers. While you can get them
from free download, that’s only good for non-commercial stuff. When they
need commercial license they still will have to buy whatever QNX sells,
I doubt they will sell them libs and headers separately :wink:

The QNX 6 environment is too much of a learning curce.
SO I am trying to configure a cheaper development environment,
that is close as possible to the Windows environment.

If customer is totally alien to POSIX environment, don’t even waste your
time. They will be happier in their ‘Windows comfort’ no matter how
better any other system is.

  • igor
6

Igor Kovalenko wrote:

I suppose those familiar tools/IDE are free, right?

Of course, that’s what the $ in MS stands for ;^)
Seriously, no, they are not, but they have been bought
already. A factor of course is platform builder, but at
$3000 that’s roughly comparable to the QNX SDK.
The problem withthe MW tools is it’s another $$$ on top,
so the QNX dev tools look expensive.

Anyway, if they are about commercial development, they’d have to buy
commercial license no matter what. For a reasonable price if they join
one of developer programs.

There’s no big deal to hack a windows based environment without buying
MW, but you still need libraries and headers. While you can get them
from free download, that’s only good for non-commercial stuff. When they
need commercial license they still will have to buy whatever QNX sells,
I doubt they will sell them libs and headers separately > :wink:

Agreed, they will have to buy a QNX SDK, no matter what.

The QNX 6 environment is too much of a learning curce.
SO I am trying to configure a cheaper development environment,
that is close as possible to the Windows environment.

If customer is totally alien to POSIX environment, don’t even waste your
time. They will be happier in their ‘Windows comfort’ no matter how
better any other system is.

I hear you. But being sales, one must explore all avenues to get to YES
:slight_smile:

But if the customer can’t see the competitive advantage in QNX, it’s a
doubly hard sell with a customer like this.

7

The customer doesn’t like the standard editors shipped with
QNX. Would also like to cross develop from Windows.

This isn’t an issue. Simply Run Samba on the QNX box, and mount the QNX
drive into Windows, then use whatever Windows editors make you happy.
You can’t use the “click-on-callback” to launch the editor, but who uses
that anyway ? I only use that feature to create the stubs, then I edit
the file separately anyway (and I work natively, so it’s not like I’m
being forced to do that).