the install script should work for you.
David Duffey
, let us know more about it and it's
requirements!
David Duffey
on.
--
David Duffey
National Instruments
Yes, LabVIEW 6i works on the 2.4 kernel.
I am currently runing the Debian testing distribution with the 2.6
kernel and was able to at least run LabVIEW 6i. Don't use 2.6 though,
IIRC there are some new threading issues that affect LabVIEW 7.0 and
earlier with the new threads in 2.6.
As far as I
I'm not sure what you mean with before being concatenated with the
rest of the pointer.
An x86 machine is little endian. So the CPU expects the bytes to be
in reverse order. If a function in your dll expects an int32, it will
want the bytes in reverse order.
So, when LabVIEW makes calls to
Hi Jason,
Ideally you'll want to use the exact same version of g++ that was used
to compile LabVIEW. For 7.0 on Linux, this was g++-3.1 (so I've been
told). I used g++-3.0 (which happened to be on my machine) and it
worked okay. This is because exceptions are compiler specific, and
the ABI has
I didn't make it clear, if you used the modified linker line, you
should be able to use any version of gcc.
-Duffey
In your false case you need to fill in the {0,0} missing elements.
The only way that you hit the false case is if you come across a time
stamp that is larger that the current interval. So, what you should
do is put a loop in the false case that add the correct number of
elements to catch up to
Unfortunetly, I don't know how to script in a password for ssh. SSH
closes the stdin and re-opens the tty that you are logged in at. This
is actually a security feature. As well as a way to send stdin to
remote programs (otherwise your password would get in the way.)
If you don't need to ssh
Hi JP,
Yes you can use g++ to build shared libraries that labview can use.
You'll want to give your C++ library a C interface. This is really
common practice. You can do this by simply declaring functions as
'extern C'. Here is a link with more information:
Hey JP,
Does your problem stem from the fact that you have no way to enter
your password?
If so, you could setup a public/private key and use the
authorized_keys file so that ssh never prompts for a password.
Everything should work after that.
You could also use an agent so that you only have
The top-left corner of the subPanel uses the same coords as the
top-left corner of your saved sub VI. Also the subPanel document
size will be the same size as your running VI. I.E. the sub VI's
should have the same placement / appearance as regular VIs, or
exsiting in a subPanel.
If you want to
I found a defora core 1 release and verified your problem (on LabVIEW
7.0). It's because the fedora kernel uses native posix threads
instead of pthreads. This changes the behavior of signals.
If you recompile your kernel and use pthreads the problem should go
away. (Although I have not done
13 matches
Mail list logo