<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">El 22/05/13 13:53, Nacho Uve escribi&oacute;:<br>
    </div>
    <blockquote
cite="mid:CAGYV1bJd4WmCZdfv=zWV+-Up5FVotziCjkHertKRBemKRWh2xQ@mail.gmail.com"
      type="cite">
      <div dir="ltr">0_0<br>
        <div><br>
        </div>
        <div style="">Is that&nbsp;<span
            style="font-family:arial,sans-serif;font-size:13px">NCS_USER_PREFS
            export need on 32bits? Or can it be included safely on the
            script anyway?</span></div>
        <div style="">
          <span style="font-family:arial,sans-serif;font-size:13px"><br>
          </span></div>
        <div style="">Regards,</div>
        <div style="">Nacho V</div>
        <div style=""><br>
        </div>
      </div>
      <div class="gmail_extra"><br>
        <br>
        <div class="gmail_quote">2013/5/22 C&egrave;sar Ordi&ntilde;ana <span
            dir="ltr">&lt;<a moz-do-not-send="true"
              href="mailto:cordinyana@gvsig.com" target="_blank">cordinyana@gvsig.com</a>&gt;</span><br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">El
            22/05/13 11:52, Simon Cropper escribi&oacute;:<br>
            <div class="im">&gt; On 22/05/13 18:56, C&egrave;sar Ordi&ntilde;ana
              wrote:<br>
              &gt;&gt; export NCS_USER_PREFS=/tmp/dummy<br>
              &gt; I did what you said, click... click, open...<br>
              &gt;<br>
              &gt; A smile spreads across my face... :)<br>
              &gt;<br>
              &gt; Yes, it worked.<br>
              &gt;<br>
              &gt; Thank you C&egrave;sar<br>
              <br>
            </div>
            Great! I have added all the info to the issue ticket
            [#1695], for this<br>
            to be taken into account in the following gvSIG release.<br>
            <br>
            Also, I have not tried it, but I suppose the same trick
            would work for<br>
            gvSIG 1.11 or 1.12. The launcher script is not the same as
            the one used<br>
            in gvSIG 2.0, but the "export ..." line may be included
            anywhere in the<br>
            script before the java execution, for example in the first
            line.<br>
            <br>
            Regards,<br>
            <br>
            [#1695] <a moz-do-not-send="true"
              href="https://devel.gvsig.org/redmine/issues/1695"
              target="_blank">https://devel.gvsig.org/redmine/issues/1695</a><br>
            <div class="im HOEnZb"><br>
            </div>
          </blockquote>
        </div>
      </div>
    </blockquote>
    <br>
    Hi Nacho,<br>
    <br>
    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. <br>
    <br>
    Also, if you want to use the library's internal default value, you
    can change the line to:<br>
    <br>
    &nbsp;&nbsp;&nbsp; export NCS_USER_PREFS=${HOME}/.erm/ncsuserprefs.xml<br>
    <br>
    Regards,<br>
    <pre class="moz-signature" cols="72">-- 
C&egrave;sar Ordi&ntilde;ana Navarro
gvSIG software architect
DiSiD Technologies (<a class="moz-txt-link-freetext" href="http://www.disid.com">http://www.disid.com</a>)
</pre>
  </body>
</html>