FibreBoy a écrit :
I am new to QNX and a bit confused. I am starting a new project using
QNX6 (RTP, Nuetrino and any other names that may fit with the newest
version). I have been developing Windows code with Borland BC5.02 for
the last 3 years and my vi/Unix skills are rather rusty. I am running
QNX on a dual boot windows system and desire to use another Windows
system to edit code.
Ok. it’s like I work.
I was able to get the QNX system’s “fs-cifs” command to mount a remote
shared folder from my windows system. This allows me to edit my code
with a friendly editor but still doing the compiling on the QNX target
system.
see at the end of this article!
I have found bits and pieces here and there that allude to the fact that
the QNX system needs to be running SAMBA to mount windows folders. Does
this mean that “fs-cifs” uses Samba ?
Not exactly, fs-cifs is the client version of the Common Interchange File
System used by windows.
So, with client you only cann access to a cifs server - your windows
workstation.
If so, why does it work without
Samba installed ?
With Samba installed, you will be able to access you files stored ON qrtp
FROM your windows IDE.
I think it’s the best choice as qrtp cannot deal with its access flag bits
on a win filesystem and can complain with it.
When I compile on the target QNX system everything works fine if there
are no errors in the compile. If qcc flags an error, it hangs the shell
(terminal window) and can only be freed with a ctrl-c. Upon further
investigation it turns out that the “as” assembler process from the
failed compile is still running in the background and cannot be
stopped. If the same scenario occurs 2-3 times, there are so many
processes running infinitely in the background that it brings the system
to its knees and must be rebooted.
It appears from pidin that the “as” processes are blocked on the
“fs-cifs” process.
Does this mean that Samba must be installed or is this a problem in the
new QNX version ?
Can someone provide any more information than a couple of the one-liners
in the Knowledge base ?
I’m absolutely not sure, but I experimented some similar problems with
‘windows’ files filled up with carriage returns.
UNIX tools don’t like carriage return. Especially make. I don’t know it as
could find CR in its input files. I don’t think so, but…
It’s because I think it’s better to let your project’s files on your qrtp
platform.
This can’t be a trivial issue since I have read so many entries in the
newsgroups about people looking for development tools (editors) because
the ones provided in RTP just won’t cut it.
A solution exists. qrtp provide xphoton which allow you to run x
applications. So you can run some better editors like gxedit.
Personnaly, I’m not very friend with x editors except xemacs.
Anyway, if you use an US keyboard, you can test it, look at
http://www.qnxstart.com.
If you don’t use an us keyboard, forget it for a while, and hope qnx works
on xphoton to support localisation!
From what I can tell there appears to be a large number of people
wanting to do their coding work from a Windows platform to speed up the
effort.
What is the secret to the mystery of mounting windows file systems ?
I hope I answered.
About compiling, we didn’t solve the problems because now we can access to
qrtp files from win. but we cannot execute the qrtp’s development tools on
win.
To do that, we need to use remote commands. As far as I know, only Sniff IDE
can do that. It support remote compiling and debugging. Fine but for about
3500$.
Finally, we choosed to use Visual Slick Edit (I’m not payed for the
publicity) it’s a fantastic IDE. Unfortunately, it doesn’t support remote
commands at that time. Of course, you can still use your Borland IDE.
Never mind, we use Phindows to have a graphical terminal on win connected to
our qrtp server. If you know PCanywhere, it’s a little bit like that. You
have a window on your win desktop with a full photon environment inside. It
works very well. We know some minor problems with it but, nothing serious.
It’s a good solution. Phindows is a separate product, you have to purchase
it to your qnx dealer.
qrtp provides everything to use it.
Alain.