Re: How to make 0launch look in extract directory instead of pwd
"Bastian Eicher" <[email protected]> Mon, 6 Jun 2016 10:37:36 +0200
| Newsgroups | gmane.comp.file-systems.zero-install.devel |
|---|---|
| Message-ID | <[email protected]> |
Hi Eric,
If your application is a Windows application, you can add a <working-dir>
tag to the <command> to achieve this effect. For example:
<implementation ...>
<command name="run" path="my-binary.exe">
<working-dir src="." />
</command>
...
</implementation>
This is currently not support on Linux and OS X. For these platforms you
could use an <environment> binding. For example:
<implementation>
<environment name="MY_DATA_DIR" insert="." mode="replace" />
...
</implementation>
At runtime the environment variable $MY_DATA_DIR will contain the fully
qualified path of the extracted implementation and can be used by your
binary to locate its data files.
Regards
Bastian
-----Original Message-----
From: Eric Duhamel [mailto:[email protected]]
Sent: Montag, 6. Juni 2016 01:21
To: [email protected]
Subject: [Zero-install-devel] How to make 0launch look in extract directory
instead of pwd
I've created a feed for a program that has a binary and data files in an
archive. 0launch downloads, extracts, and caches the archive; but when it
runs the binary the program looks in the current working directory for the
data files. This causes the program to fail since it can't find the data
files (they are within the cached archive directory, not the current working
directory). If I specifically invoke 0launch from within the cached archive,
the program does run since the data files are in the current working
directory, but obviously this isn't the way 0launch is usually run.
How do I configure the feed file to change the current working directory to
the cached directory? Or is there another technique for this?
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e