Started compilation: Sat Dec 9 21:35:30 2017
--
Errors in:
/c/msys64/usr/src/grass_trunk/raster/r.in.lidar
/c/msys64/usr/src/grass_trunk/raster3d/r3.in.lidar
/c/msys64/usr/src/grass_trunk/vector/v.out.lidar
/c/msys64/usr/src/grass_trunk/vector/v.in.lidar
--
lidar tools are already deactivated in winGRASS 32bit, now it seems also
winGRASS 64bit affected.
have seen the same error on a local 64bit compilation.
Started compilation: Sat Dec 9 21:35:30 2017
--
Errors in:
/c/msys64/usr/src/grass_trunk/raster/r.in.lidar
/c/msys64/usr/src/grass_trunk/raster3d/r3.in.lidar
/c/msys64/usr/src/grass_trunk/vector/v.out.lidar
/c/msys64/usr/src/grass_trunk/vector/v.in.lidar
--
lidar tools are already deactivated in winGRASS 32bit, now it seems also
winGRASS 64bit affected.
have seen the same error on a local 64bit compilation.
The opinions I express are my own and are not representative of the official policy of the U.S.Fish and Wildlife Service or Dept. of the Interior. Life is too short for undocumented, proprietary data formats.
__NOTE: This email correspondence and any attachments to and from this sender is subject to the Freedom of Information Act (FOIA) and may be disclosed to third parties.__
the liblas [1] tools and laszip in OSGeo4W are broken.
what would be needed: someone may investigate the issues a little bit more
and may recompile these tools from scratch that they are working again. it
seems to be some kind of dll mismatches with different flavours in 32bit and
64bit.
the liblas [1] tools and laszip in OSGeo4W are broken.
what would be needed: someone may investigate the issues a little bit more
and may recompile these tools from scratch that they are working again. it
seems to be some kind of dll mismatches with different flavours in 32bit
and
64bit.
deactivated now lidar modules in winGRASS 32bit and 64bit by:
[GRASS-SVN] r71920 - grass/trunk/mswindows/osgeo4w svn_grass at
osgeo.org
[GRASS-SVN] r71921 - grass/branches/releasebranch_7_4/mswindows/osgeo4w
svn_grass at osgeo.org
[GRASS-SVN] r71922 - grass/trunk/mswindows/osgeo4w svn_grass at
osgeo.org
[GRASS-SVN] r71923 - grass/branches/releasebranch_7_2/mswindows/osgeo4w
svn_grass at osgeo.org
in a mid term, a fix of the liblas/libzip tools in OSGeo4W is needed.
taken from the related OSGeo4W ticket:
-------------------
hobu:
This was caused by me. I updated LASzip, but libLAS hasn't been updated to
use the new LASzip API. You'll have to revert to the LASzip 2.2.0 version to
use libLAS
------------------
the winGRASS build environment there are 2 choices now:
- compilation works with the the buggy liblas/laszip due to my fixes above,
though no lidar modules
- build environment reverts back to the LASzip 2.2.0 version to use libLAS
On Thu, Dec 14, 2017 at 10:43 AM, Helmut Kudrnovsky <hellik@web.de> wrote:
Helmut Kudrnovsky wrote
> deactivated now lidar modules in winGRASS 32bit and 64bit by:
>
> [GRASS-SVN] r71920 - grass/trunk/mswindows/osgeo4w svn_grass at
> osgeo.org
> [GRASS-SVN] r71921 - grass/branches/releasebranch_7_4/mswindows/osgeo4w
> svn_grass at osgeo.org
> [GRASS-SVN] r71922 - grass/trunk/mswindows/osgeo4w svn_grass at
> osgeo.org
> [GRASS-SVN] r71923 - grass/branches/releasebranch_7_2/mswindows/osgeo4w
> svn_grass at osgeo.org
>
> in a mid term, a fix of the liblas/libzip tools in OSGeo4W is needed.
taken from the related OSGeo4W ticket:
-------------------
hobu:
This was caused by me. I updated LASzip, but libLAS hasn't been updated to
use the new LASzip API. You'll have to revert to the LASzip 2.2.0 version
to
use libLAS
------------------
the winGRASS build environment there are 2 choices now:
- compilation works with the the buggy liblas/laszip due to my fixes above,
though no lidar modules
- build environment reverts back to the LASzip 2.2.0 version to use libLAS
I think the latter course of action is better in the short term. Howard,
--
Doug Newcomb
USFWS
551F Pylon Dr
Raleigh, NC
919-856-4520 ext. 14 doug_newcomb@fws.gov
---------------------------------------------------------------------------------------------------------
The opinions I express are my own and are not representative of the
official policy of the U.S.Fish and Wildlife Service or Dept. of the
Interior. Life is too short for undocumented, proprietary data formats.
*NOTE: This email correspondence and any attachments to and from this
sender is subject to the Freedom of Information Act (FOIA) and may be
disclosed to third parties.*
- build environment reverts back to the LASzip 2.2.0 version to use libLAS
yes, we can downgrade version in building environment, and also in
packaging environment (for standalone installer). But osgeo4w will
download latest version, and the modules will be likely broken on
runtime. Why cannot be broken packages simply reverted back?
- build environment reverts back to the LASzip 2.2.0 version to use
libLAS
yes, we can downgrade version in building environment, and also in
packaging environment (for standalone installer). But osgeo4w will
download latest version, and the modules will be likely broken on
runtime. Why cannot be broken packages simply reverted back?