gvSIG bugs #4011
gvSIG 2.3 build 2414 can't be executed
| Status: | Closed | % Done: | 0% | |
|---|---|---|---|---|
| Priority: | Immediate | Spent time: | - | |
| Assignee: |  Joaquín del Cerro Murciano | |||
| Category: | Application | |||
| Target version: | 2.3.0-2417 (rev. org.gvsig.desktop-2.0.123) | |||
| Severity: | Blocker | Add-on version: | ||
| gvSIG version: | 2.3.0 | Add-on build: | ||
| gvSIG build: | 2414 | Add-on resolve version: | ||
| Operative System: | Add-on resolve build: | |||
| Keywords: | Proyecto: | |||
| Has patch: | Hito: | |||
| Add-on name: | Unknown |
Description
gvSIG 2.3 build 2414 can't be executed on win64. The console is closed unexpectedly checking the shared library dependencies. No gvSIG.log is generated.
Associated revisions
refs #4011, añadido que cree la carpeta del plugin en el home del usuario si no existe antes de intentar acceder a ella en el autorun.sh
History
#1
Updated by Álvaro Anguix over 8 years ago
- Operative System deleted (
Windows)
In Linux don't work. I think that it's a problem with folder "plugins"
#2
Updated by Álvaro Anguix over 8 years ago
- Priority changed from Normal to Immediate
- Assignee set to Joaquín del Cerro Murciano
#3
Updated by Álvaro Anguix over 8 years ago
It seems that it's a problem with scripting plugin. Almost in Linux, if you install gvSIG without this plugin, gvSIG works.
#4
Updated by Antonio Falciano over 8 years ago
Álvaro Anguix wrote:
It seems that it's a problem with scripting plugin. Almost in Linux, if you install gvSIG without this plugin, gvSIG works.
Hi Alvaro,
I can confirm. Removing the scripting plugin, gvSIG is executed regularly also in win64.
#5
Updated by Joaquín del Cerro Murciano over 8 years ago
- Target version set to 2.3.0-2415
- Status changed from New to Fixed
- Subject changed from gvSIG 2.3 build 2414 can't be executed on win64 to gvSIG 2.3 build 2414 can't be executed
Falla en todas las plataformas cuando no existe la carpeta del plugin de scripting en el home del usuario.
#6
Updated by Antonio Falciano over 8 years ago
- Status changed from Fixed to Closed
#7
Updated by Antonio Falciano over 8 years ago
- Target version changed from 2.3.0-2415 to 2.3.0-2447-final (rev. org.gvsig.desktop-2.0.153)
- Status changed from Closed to New
I've just tried with a fresh install of 2415 without the gvSIG home folder and gvSIG.sh stops to work when trying to cd to the below scripts directory:
INFO launch Running autorun from plugin org.gvsig.scripting.app.mainplugin gvSIG.sh: cd: line 33: can't cd to C:\Users\Antonio/gvSIG/plugins/org.gvsig.scri pting.app.mainplugin/scripts
If I apply the fix commented in #4033#note-1 and create such directory manually, then gvSIG can be executed. So, in the org.gvsig.scripting.app.mainplugin autorun.sh I'd substitute row 33 with:
autorun_dir="$GVSIG_HOME_FOLDER/plugins/$PLUGIN_NAME/scripts" if [ ! -d "$autorun_dir" ]; then mkdir -p "$autorun_dir" fi cd "$autorun_dir"
and row 38 with:
sc_autorun="$autorun_dir/$sc_autorun"
#8
Updated by Antonio Falciano over 8 years ago
- Target version changed from 2.3.0-2447-final (rev. org.gvsig.desktop-2.0.153) to 2.3.0-2417 (rev. org.gvsig.desktop-2.0.123)
- Status changed from New to Closed
It's ok in build 2416, so I close the ticket.