Ok (I guess) but this causes severe problems running shell scripts that call out the GRASS modules ... there is no way of knowing which modules are compiled executables (which run fine from the shell script) and which ones are Windows Batch files (which DON'T run when called from a script) ... unless you run the script and figure out which modules make it crash. If you look in the bin directory, you'll see a mix of both ... for example r.mask, v.build.all and v.db.addcolumn are Windows Batch files which you can''t run from a shell script - you have to add the "python {path to script}/{script}.py" to run it whereas in the same bin directory v.build, v.clean, r.what, etc are compiled executables.
This is really really (really) bad. There are a lot of legacy shell scripts that will need extensive rewriting for which there are no resources to do. It's bad enough that msys is gone, the topology is no longer valid (have to update all data), a large amount of the module syntax options have changed, and so on ... for me all of this grief is because v.net doesn't snap points to the network and the fix (in v7) won't be ported to v6.4.4 .... They modules should all be compiled executables so legacy shell scripts users have can run them ... please make at least ONE thing about this "upgrade" semi-straightforward. It's been a nightmare.
Chris Bartolomei P.E.
Engineer/Scientist
ENSCO, Inc.
bartolomei.chris@ensco.com
________________________________________
From: grass-user [grass-user-bounces@lists.osgeo.org] On Behalf Of Helmut Kudrnovsky [hellik@web.de]
Sent: Saturday, April 30, 2016 1:05 AM
To: grass-user@lists.osgeo.org
Subject: Re: [GRASS-user] why is v.build.all (and many others) a windows batch file and not an executable?
Bartolomei.Chris-2 wrote
Good evening and happy weekend!
I am (still) upgrading from 6.4.4 to 7.0.3 and I discovered that the
vector topography of all my data is not upwards compatible so per the
instructions at
https://urldefense.proofpoint.com/v2/url?u=https-3A__grasswiki.osgeo.org_wiki_Convert-5Fall-5FGRASS-5F6-5Fvector-5Fmaps-5Fto-5FGRASS-5F7&d=CwIGaQ&c=DsZY2bea7iNIzyp-7sZ0t0F2UfNQZUfZhEPCv_2wBI0&r=O31ltou6ygJL2Y01kQyNJJD2kiILIsbyz2V0Hn4lFUY&m=OBfSgl1s_aokN50AbM4hgIa8k--o2IlLBqyw5RqMUhE&s=oC4JyxynBdHD_R4xFz0sx_PQrQbEkquIEGJIHlwZqtk&e=
I am (trying) to us v.build.all to update the topography. I had installed
GRASS with MSYS from OSGEO4W but that goodness uses the unix-like msys
shell as the command console - which for what I need is perfect ... I can
copy/paste commands to test as I write shell scripts to do GIS magic. BUT
... go ahead and try to run v.build.all ... and nope - it isn't going to
let you. Ends up v.build.all (and many other modules) are Windows Batch
files !! the msys command console won't run the GRASS modules that are
Windows Batch files. I was able to work around this a little issue by
also installing just the regular GRASS 7.0.3 (they install in different
directories) and run the v.build.all from the Windows cmd console (it is
the standard command console that runs with "normal" 7.0.3 (not from
OSGEO4W) but which won't run any of the code I put into a shell script
because, well, it's unix shell not DOS - hence the need for msys)... I was
going to drop a note to the OSGEO4W project about the issue but the same
thing is part of the current (non-OSGEO4W) package ... look in \Program
Files\GRASS GIS 7.0.3\bin\ and you'll see many executables (compiled
python scripts I assume) and quite a few Windows Batch files.... why is
this? Should they not all be compiled executables ??
I don't understand this and it makes it really hard to create shell
scripts to run the modules...
Thanks,
Chris
Chris Bartolomei P.E.
Engineer/Scientist
ENSCO, Inc.
bartolomei.chris@
The information contained in this email message is intended only for the
use of the individual(s) to whom it is addressed and may contain
information that is privileged and sensitive. If you are not the intended
recipient, or otherwise have received this communication in error, please
notify the sender immediately by email at the above referenced address and
note that any further dissemination, distribution or copying of this
communication is strictly prohibited.
The U.S. Export Control Laws regulate the export and re-export of
technology originating in the United States. This includes the electronic
transmission of information and software to foreign countries and to
certain foreign nationals. Recipient agrees to abide by these laws and
their regulations -- including the U.S. Department of Commerce Export
Administration Regulations and the U.S. Department of State International
Traffic in Arms Regulations -- and not to transfer, by electronic
transmission or otherwise, any content derived from this email to either a
foreign national or a foreign destination in violation of such laws.
_______________________________________________
grass-user mailing list
grass-user@.osgeo
https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.osgeo.org_mailman_listinfo_grass-2Duser&d=CwIGaQ&c=DsZY2bea7iNIzyp-7sZ0t0F2UfNQZUfZhEPCv_2wBI0&r=O31ltou6ygJL2Y01kQyNJJD2kiILIsbyz2V0Hn4lFUY&m=OBfSgl1s_aokN50AbM4hgIa8k--o2IlLBqyw5RqMUhE&s=6HsZmdgYxBVR5YxnNSQ8MO0SPOsr9DW0JqK9sKi6NcQ&e=
the exe files are compiled C/C++ modules.
the bat-files are starting wrapper files for python scripts living in
..\scripts.
These wrapper files are needed as winGRASS standalone/Osgeo4w uses its own
python stack and doesn't use the system wide python.
The scripts in .. \scripts are all python scripts in Grass7, this has
changed from grass6 to grass7. Therefore the starting scripts wrapper
bat-files in .. \bin which point to the scripts in .. \scripts by using the
right python interpreter (have a look into the bat-files).
-----
best regards
Helmut
--
View this message in context: https://urldefense.proofpoint.com/v2/url?u=http-3A__osgeo-2Dorg.1560.x6.nabble.com_why-2Dis-2Dv-2Dbuild-2Dall-2Dand-2Dmany-2Dothers-2Da-2Dwindows-2Dbatch-2Dfile-2Dand-2Dnot-2Dan-2Dexecutable-2Dtp5263621p5263629.html&d=CwIGaQ&c=DsZY2bea7iNIzyp-7sZ0t0F2UfNQZUfZhEPCv_2wBI0&r=O31ltou6ygJL2Y01kQyNJJD2kiILIsbyz2V0Hn4lFUY&m=OBfSgl1s_aokN50AbM4hgIa8k--o2IlLBqyw5RqMUhE&s=fnBmjhWXFdNCDrx6XE__RPs75E2dfHgCt9zjMAxggfE&e=
Sent from the Grass - Users mailing list archive at Nabble.com.
_______________________________________________
grass-user mailing list
grass-user@lists.osgeo.org
https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.osgeo.org_mailman_listinfo_grass-2Duser&d=CwIGaQ&c=DsZY2bea7iNIzyp-7sZ0t0F2UfNQZUfZhEPCv_2wBI0&r=O31ltou6ygJL2Y01kQyNJJD2kiILIsbyz2V0Hn4lFUY&m=OBfSgl1s_aokN50AbM4hgIa8k--o2IlLBqyw5RqMUhE&s=6HsZmdgYxBVR5YxnNSQ8MO0SPOsr9DW0JqK9sKi6NcQ&e=
The information contained in this email message is intended only for the use of the individual(s) to whom it is addressed and may contain information that is privileged and sensitive. If you are not the intended recipient, or otherwise have received this communication in error, please notify the sender immediately by email at the above referenced address and note that any further dissemination, distribution or copying of this communication is strictly prohibited.
The U.S. Export Control Laws regulate the export and re-export of technology originating in the United States. This includes the electronic transmission of information and software to foreign countries and to certain foreign nationals. Recipient agrees to abide by these laws and their regulations -- including the U.S. Department of Commerce Export Administration Regulations and the U.S. Department of State International Traffic in Arms Regulations -- and not to transfer, by electronic transmission or otherwise, any content derived from this email to either a foreign national or a foreign destination in violation of such laws.
