<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body dir="auto">
<div>So far I'm stuck on compiling liblas with new gdal and no one has had any advice for a way forward. If that can happen, I can recompile with new liblas. That is why I was hoping for laslib. It may be that I just did not link it correctly. I'm open to advice. </div>
<div><br>
<div>Michael Barton</div>
<div>School of Human Evolution &Social Change</div>
<div>Center for Social Dynamics & Complexity</div>
<div>Arizona State University</div>
<div><br>
</div>
...Sent from my iPad</div>
<div><br>
On Sep 15, 2015, at 6:02 PM, Vaclav Petras <<a href="mailto:wenzeslaus@gmail.com">wenzeslaus@gmail.com</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">[Was: Re: [GRASS-dev] New Mac binaries uploaded]<br>
</div>
<div class="gmail_quote"><br>
Hi Michael,<br>
</div>
<div class="gmail_quote"><br>
On Mon, Aug 24, 2015 at 11:45 PM, Michael Barton <span dir="ltr"><<a href="mailto:Michael.Barton@asu.edu" target="_blank">Michael.Barton@asu.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
That would be wonderful. I sort of got that impression too. But will the GRASS lidar tools be able to use LASlib instead of Liblas?<span class="im"><br>
</span></blockquote>
<div><br>
</div>
<div>the binary in Dropbox has lasinfo et al. from LAStools. However, r.in.lidar doesn't work (2 different computers). Does it work for you? Running r.in.lidar or v.in.lidar --help and says<br>
<br>
</div>
<div>dyld: Library not loaded: /usr/local/lib/liblas.2.2.0.dylib<br>
</div>
<div><br>
</div>
<div>As I said earlier, GRASS is made to dynamically link with libLAS. In case the API of LAStools library is the same, there might be a way to change the GRASS configuration and makefiles or the ones for LAStools, so that GRASS can compile with LAStools statically
but I don't know the way.<br>
<br>
</div>
<div>Currently with LAStools compiled with GRASS on Mac, you can use the tools in command line but it's useless for GRASS modules, namely r|v.in.lidar.<br>
<br>
</div>
<div>Thanks,<br>
</div>
<div>Vaclav<br>
</div>
<div><br>
</div>
<div>PS: Although I'm working on migration to PDAL [1], it will take some time before it gets even to 7.1 (trunk), not mentioning 7.0. So, the libLAS library is still needed.</div>
<div><br>
[1] <a href="https://trac.osgeo.org/grass/ticket/2732">https://trac.osgeo.org/grass/ticket/2732</a><br>
</div>
<div><br>
<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<span class="im"></span>
<div class="">
<div class="h5">> On Aug 24, 2015, at 8:40 PM, William Kyngesburye <<a href="mailto:woklist@kyngchaos.com">woklist@kyngchaos.com</a>> wrote:<br>
><br>
> I looked at LAS this spring. From what I found, libLAS is superceded by LASlib, found in LAStools. laslib and some of the tools are still opensource, but other tools are not.<br>
><br>
> Laslib does not have a configure, it's a simple makefile that needs a little tweaking for OS X. And there appears to be no dependence on BOOST or Geotiff, or anything else.<br>
><br>
> For laslib, all I needed to do was edit laslib/src/makefile and change these lines:<br>
><br>
> COPTS = -Os -Wall -Wno-deprecated -DNDEBUG -DUNORDERED -arch x86_64 -isysroot /Developer/SDKs/MacOSX10.7.sdk<br>
> COMPILER = clang++<br>
><br>
> And in the liblas.a target, add a line after the cp line (tha's a tab at the start):<br>
><br>
> ranlib ../lib/$@<br>
><br>
> Also delete the precompiled Windows lib in laslib/lib.<br>
><br>
> You should be able to use the library right from the source, it's static so it will be built into GRASS without needing a copy of the laslib. For GRASS configuration, the library will be in that lib folder and includes in the laslib/inc folder.<br>
><br>
> On Aug 24, 2015, at 3:47 PM, Michael Barton <<a href="mailto:michael.barton@asu.edu">michael.barton@asu.edu</a>> wrote:<br>
><br>
>> For LASlib compliing, I managed to get past the GEOTIFF problem with the following:<br>
>><br>
>> cmake -G "Unix Makefiles" -D CMAKE_OSX_ARCHITECTURES="i386;x86_64” \<br>
>> -D CMAKE_OSX_SYSROOT="/Developer/SDKs/MacOSX10.7.sdk” \<br>
>> -D GDAL_CONFIG=/Library/Frameworks/GDAL.framework/Programs/gdal-config \<br>
>> -D GEOTIFF_INCLUDE_DIR=/Library/Frameworks/UnixImageIO.framework/unix/include \<br>
>> -D GEOTIFF_LIBRARY=/Library/Frameworks/UnixImageIO.framework/unix/lib/libgeotiff.dylib \<br>
>> ../<br>
>><br>
>> But now cmake is complaining about the CMAKE_OSX_ARCHITECTURES flag. I don’t know if this harkens back to the similar problem with boost or if this is new. I’ve tried both i386 and x86_64 individually and it still won’t compile.<br>
>><br>
>> Michael<br>
<br>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</blockquote>
</body>
</html>