gvSIG bugs #3069

Corregir el gvSIG.sh para que ejecute correctamente en Windows con Busybox

Added by Joaquín del Cerro Murciano over 9 years ago. Updated over 9 years ago.

Status:Closed% Done:

0%

Priority:NormalSpent time:-
Assignee:Joaquín del Cerro Murciano
Category:-
Target version:2.1.0-2260
Severity:Minor Add-on version:
gvSIG version:2.1.0 Add-on build:
gvSIG build: Add-on resolve version:
Operative System: Add-on resolve build:
Keywords: Proyecto:
Has patch: Hito:
Add-on name:Unknown

Associated revisions

Revision 41888
Added by Joaquín del Cerro Murciano over 9 years ago

refs #3069, correcciones en el gvSIG.sh para que ejecute correctamente en windows con busybox.

Revision 41906
Added by Joaquín del Cerro Murciano over 9 years ago

refs #3069, actualizado el gvSIG.sh para que referencia al jre 7 en lugar de al 6.

History

#1 Updated by Joaquín del Cerro Murciano over 9 years ago

  • Status changed from New to Fixed

#2 Updated by Antonio Falciano over 9 years ago

Hi Joaquín,
I've noticed the following line in the fix of this ticket:

PJH5="$GVSIG_INSTALL_FOLDER/gvSIG/extensiones/jre_6_windows_i586/jre" 

...while we are using jre_7_windows_i586 now.

#3 Updated by Antonio Falciano over 9 years ago

In order to launch gvSIG in Windows, we should have:

-Djava.library.path=\"${GVSIG_NATIVE_LIBS}\" \
instead of
-Djava.library.path=\"${GVSIG_NATIVE_LIBS}\":/usr/lib \
Furthermore, we should have all the needed DLLs in the GVSIG_INSTALL_FOLDER/native folder, because:
export GVSIG_NATIVE_LIBS="${GVSIG_INSTALL_FOLDER}/native" 

#4 Updated by Álvaro Anguix over 9 years ago

  • Status changed from Fixed to Closed

Also available in: Atom PDF