Arne Stocker wrote:
> My question :
>
> a) how to get the temporary directory
> b) Is there a way to force qtjambi to use a special temp-dir, regardless
> wether it is an user application or a system service
>
Hi, Arne.
The directory name of the temp directory will be:
<tmpdir> / QtJambi_<user name>_<architecture>_<jambi version>_<key>
where <tmpdir> is the "java.ui.tmpdir" system property, <user name> is
the system property "user.name" and <architecture> is the system
property "os.arch". The Jambi version is retrieved from
com.trolltech.qt.Utilities.VERSION_STRING and the key is specified in
the deployment spec XML file inside the .jar file that contains the
native libraries. If you want to have a temporary directory of your own,
you would set this key to something unique. By default it's set to the
compiler spec plus a timestamp for the time of the build.
In com.trolltech.tools there's a tool called CacheCleaner which we
include for developers who build Qt Jambi from source, since this will
typically give you several different cache entries and pollute your
temporary directory quickly. It is of course not our intention that you
have to deploy this type of tool with your own software, but maybe it
could be helpful to you in this particular situation.
I find the problem very strange though, so I'd like to try to find out
more about it. Do you know if the customers in question are using any
other Qt Jambi applications at the moment? Are you by chance building Qt
and Qt Jambi from source, or are you using the binary packages?
It would be very interesting to be able to get the actual contents of
the cache directory at the point where this problem occurs.
-- Eskil
_______________________________________________
Qt-jambi-interest mailing list
[email protected]
http://lists.trolltech.com/mailman/listinfo/qt-jambi-interest
