El 22/05/13 13:53, Nacho Uve escribió:
0_0
Is that NCS_USER_PREFS export need on 32bits? Or can it be included
safely on the script anyway?
Regards,
Nacho V
2013/5/22 Cèsar Ordiñana <[email protected]
<mailto:[email protected]>>
El 22/05/13 11:52, Simon Cropper escribió:
> On 22/05/13 18:56, Cèsar Ordiñana wrote:
>> export NCS_USER_PREFS=/tmp/dummy
> I did what you said, click... click, open...
>
> A smile spreads across my face... :)
>
> Yes, it worked.
>
> Thank you Cèsar
Great! I have added all the info to the issue ticket [#1695], for this
to be taken into account in the following gvSIG release.
Also, I have not tried it, but I suppose the same trick would work for
gvSIG 1.11 or 1.12. The launcher script is not the same as the one
used
in gvSIG 2.0, but the "export ..." line may be included anywhere
in the
script before the java execution, for example in the first line.
Regards,
[#1695] https://devel.gvsig.org/redmine/issues/1695
Hi Nacho,
I think it is not related to the 32/64 bits issue, in any case you can
include the "export" line safely. It seems that environment variable is
the path of a configuration file used by the ecw library, and you don't
need to create it.
Also, if you want to use the library's internal default value, you can
change the line to:
export NCS_USER_PREFS=${HOME}/.erm/ncsuserprefs.xml
Regards,
--
Cèsar Ordiñana Navarro
gvSIG software architect
DiSiD Technologies (http://www.disid.com)
_______________________________________________
Gvsig_internacional mailing list
[email protected]
To see the archives, edit your preferences or unsubscribe from this mailing
list, please access this url:
http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional
