Re: #import with dynamic path
"Faisal" <faisalm83@gmail.com> wrote in message
news:69740326-7550-41f2-b153-61c42939c077@u18g2000pro.googlegroups.com
I want to import .lib file to automate the labVIEW software.
I wrote the code like this
#import "C:\Program Files\National Instruments\LabVIEW 8.5\resource
\LabVIEW.tlb"
This is working correcty
But in some machines labVIEW is installed in different path.
So I want a code something like this
char path[] = GetLavIewTlbPath();
#import path
#import directive works at compile time. The line of code above it would
be invoked at runtime. Naturally, you'll have to compile the program
before you can run it.
You seem to believe that #import directive somehow affects how your
application runs on the target machine. #import directive doesn't
require that the TLB be installed on the target machine at the specified
path, just as #include directive doesn't require that the header file be
installed on the target machine.
The path you specify is resolved on developer's machine. The resolution
works the same way as for #include directives. E.g. you can just write
#import "LabVIEW.tlb"
and copy the file over to your project directory, or add its path to
Additional Include Files list in your project settings.
--
With best wishes,
Igor Tandetnik
With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly
overhead. -- RFC 1925