ward@[EMAIL PROTECTED]
(ward mcfarland) wrote in message
news:<1gizcku.1vrw8c6511474N%ward@[EMAIL PROTECTED]
>...
> Yves Surrel <surrel@[EMAIL PROTECTED]
> wrote:
>
> > > If LabView for X is Cocoa and not Carbon, it will almost surely not
be
> > > able to link to Carbon SharedLibs.
> >
> > This is probably the point, if the second part of your sentence is
> > true. Labview 7.0 for macOSX is surely Cocoa...
>
> Offhand, I cannot think of an easy way to differentiate between a Mach
> (Cocoa) bundled app and a CFM (Carbon) one, although there likely is
> one. I could not find any "real" technical specs on LabView at NI's
> site, nor what type of shared libraries LV7 requires. Do they supply no
> sample libraries nor do***entation about building libraries to use with
> LV?
>
>
I have found the following NI statement about LV7 for MacOSX:
"Shared libraries compiled for Mac OS 9.x or earlier are _not_
compatible with LabVIEW for Mac OS X. You must recompile them in the
Mach-O binary format as a bundle with natural alignment, not the 68k
alignment. Apple provides free developer tools for producing such
binaries."
So I need PowerMops to be able to achieve this...
>
> Apple Events might work for you, since they are much faster under X than
> previously. Unfortunately, the old PPC Toolbox is no longer available,
> as that was **very** fast and suitable for passing large blocks of fdata
> between applications (probably was deemed too insecure for X, what with
> isolated memory spaces, etc). TCPIP would be another method you might
> look into and give the added benefit of being able to run client-server
> on different machines - it appears that LV sup****ts this.
You answer to my other post "The same Forth on different OS"!
Cheers
Yves
|
