[GRASS-dev] [GRASS GIS] #2333: choose python interpreter during the GRASS installation on windows
GRASS GIS
trac at osgeo.org
Mon Jun 16 03:14:20 PDT 2014
#2333: choose python interpreter during the GRASS installation on windows
--------------------------------------------------+-------------------------
Reporter: zarch | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: normal | Milestone: 7.1.0
Component: Python | Version: svn-trunk
Keywords: windows installer python interpreter | Platform: MSWindows 8
Cpu: All |
--------------------------------------------------+-------------------------
Comment(by zarch):
Hi Martin,
Replying to [comment:13 martinl]:
> Replying to [comment:12 zarch]:
>
> > There is a way to view/test the modified NSIS file?
>
> Ideal place would be trunk (+ daily builds). Unfortunately daily
> builds of winGRASS 7.1 (trunk) are completely broken (1)* thanks
> to r60679 (so called "magic to break the whole system"). We could
> probably try to fix it first(?).
If I interpreted correctly [0], the solution should be to generate the
.bat files for each GRASS module/scripts written in python, right?.
Do you think that could be possible to generate the .bat files in the NSIS
file during the installation process?
Do you think that the NSIS file is the correct place where these .bat
files should be generated or we should put this action in some other place
during the installation process?
Pietro
[0] https://www.mail-archive.com/grass-dev@lists.osgeo.org/msg35001.html
--
Ticket URL: <http://trac.osgeo.org/grass/ticket/2333#comment:14>
GRASS GIS <http://grass.osgeo.org>
More information about the grass-dev
mailing list