[GRASS-dev] r.in.lidar not running in Mac binaries for 7.1

[William Kyngesburye]

Looking closer at lastools/laslib and liblas, I think I got it partly right - the tools are funtionally the same between the two, but the libraries have very different headers (API).  I was interested in getting las into my QGIS package, which uses the tools, not the library, and I didn't realize that difference.

So the question is if GRASS supports one or the other library or both, or does it also use the tools in a script so it doesn't matter.

As far as the linking goes, that embedded path to the library shouldn't matter since GRASS uses DYLD_LIBRARY_PATH to redirect linking.  If it does still fail, maybe the library wasn't packaged with GRASS?

On Sep 16, 2015, at 1:33 AM, Michael Barton <michael.barton at asu.edu> wrote:

> That’s what I’m using. I’d previously compiled libLAS with gdal 1.10. There are a number of pieces to compiling libLAS in C++, including compiling Boost, and a number of places for things to go wrong.
> 
> Michael
> ____________________
> C. Michael Barton
> Director, Center for Social Dynamics & Complexity 
> Professor of Anthropology, School of Human Evolution & Social Change
> Head, Graduate Faculty in Complex Adaptive Systems Science
> Arizona State University
> 
> voice:  480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
> fax: 480-965-7671 (SHESC),  480-727-0709 (CSDC)
> www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>> On Sep 15, 2015, at 11:30 PM, Markus Neteler <neteler at osgeo.org> wrote:
>> 
>> 
>> On Sep 16, 2015 4:40 AM, "Michael Barton" <Michael.Barton at asu.edu> wrote:
>> >
>> > So far I'm stuck on compiling liblas with new gdal and no one has had any advice for a way forward.
>> 
>> Maybe stick to GDAL 1.11 for now?
>> 
>> Markus
>> 
> 
> _______________________________________________
> grass-dev mailing list
> grass-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev

-----
William Kyngesburye <kyngchaos*at*kyngchaos*dot*com>
http://www.kyngchaos.com/

All generalizations are dangerous, even this one.