| Re: Provinding files for VM-Application [message #61826] |
Fri, 08 August 2008 14:34  |
ben.bighair
Messages: 221
Registered: April 2007
|
Senior Member |
|
|
On Aug 8, 10:15 am, wengi <andreas.w...@gmail.com> wrote:
> On 8 Aug., 15:22, Vince Hradil <hrad...@yahoo.com> wrote:
>
>
>
>> On Aug 8, 7:10 am, wengi <andreas.w...@gmail.com> wrote:
>
>>> On 8 Aug., 14:03, Bob Crawford <Snowma...@gmail.com> wrote:
>
>>>> On Aug 8, 7:51 am, wengi <andreas.w...@gmail.com> wrote:
>
>>>> > Hi there,
>
>>>> > I'm currently coding a project for a colleague. Unfortunately I have
>>>> > to build the application for the VM because the colleague does not
>>>> > have an IDL-license.
>>>> > The project needs some kind of dummy-files to read some information
>>>> > from. Using the idlde I have the opportunity to provide these files, I
>>>> > think. I just put the file in the "data-folder" of the project. Later
>>>> > on I want to open the file with openr.
>>>> > While testing the application on a VM I always run into a "file-not-
>>>> > found" error. I have no idea in which way I have to specify the path
>>>> > to the file in the source-code.
>>>> > I tried:
>
>>>> > hname = '\data\header.ima'
>>>> > hname = '\header.ima'
>
>>>> > and then
>
>>>> > openr,unit,hname,/get_lun
>
>>>> > Always running into the "file-not-found" error. So where can I find my
>>>> > provided files after having built the project? Any idea would be
>>>> > appreciated.
>
>>>> > Regards,
>>>> > Andreas
>
>>>> no experience (yet) with the VM, but have you tried
>>>> hname = 'data\header.ima'
>>>> or
>>>> hname = 'header.ima'
>>>> with the file in the same dir as the VM executable (or a data subdir)?
>
>>> I tried both hnames. The file is "inside" the project. It is not
>>> explicitly saved on the other machine. I hoped not to have to do this.
>>> When creating the project one has the opportunity to include files of
>>> other types than sourcode files. I hoped that it would be possible
>>> that the files will then be available on the other machine.
>
>> You WILL have to copy the file to the other machine. How else would
>> the vm find it? I suppose you could read the file in, encode it
>> somehow into a variable then use that encoding as a hard coded
>> variable in the sav file (hard to describe) - but that seems like a
>> lot of hard work. Why can't you just make the file available to the
>> vm?
>
>> Maybe the better question is - what do you need the "dummy" file for?
>> Can this be changed to, say, a template or an anonymous structure,
>> etc. Something that can be coded into idl and not have to be read
>> from the file system...
>
>> Just a thought.
>
> I think it would be no problem to copy it. I just thought that with
> packing it into the project I can build a bundle for the colleague
> which provides him all he needs. But I will see...
> Thanks for that thought.
Hi,
If you must distribute the extra stuff with the VM .sav file, then you
can use the SOURCEROOT.pro routine to at least determine where
the .sav file is. From there you have to depend upon a cooperative
(aka meek and submissive) end-user who will not mess with your
distribution's file structure. There is more here at http://tinyurl.com/6qgzdn
Cheers,
BEn
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
