[Liblas-devel] ARSF LiDAR Analysis GUI

Mark Seibel mseibel at gmail.com
Thu Aug 23 07:57:57 PDT 2012


I copied the .hpp files into /usr/local/include/laslib and the
compilation went further.  Any suggestions?

Now I end up with errors:

/usr/bin/ld: cannot find -llaslib
/usr/bin/ld: cannot find -ljemalloc
collect2: ld returned 1 exit status
make[1]: *** [liblidarquadtree.la] Error 1


Mark

On Thu, Aug 23, 2012 at 9:50 AM, Berin Smaldon <besm at pml.ac.uk> wrote:
> Hi Mark,
>
> Sorry about that, it seems that on our systems we have installed the
> laslib headers to /usr/local/include/laslib. Problematically, both
> programs I think expect the headers to be in the format laslib/*.hpp,
> I'm not sure yet whether that's specific to our system and we should
> change the program to ignore the "laslib/" prefix, so that the configure
> script can be configured to point the compiler to any old directory, or
> whether there is some conventional way of installing laslib that we've
> followed. I'm afraid Mike, who would know, is away until Tuesday, so I
> can't say for sure.
>
> Your options are to either wait for me to find out and I will set it up
> how it should be, (configure already points the compiler at both
> /usr/local/include and /usr/local/include/laslib, so you or I should be
> able to change any of the include statements over without trouble) OR
> you can work around it for now if you don't mind the hassle.
>
> To work around it, either copy the headers to
> /usr/local/include/laslib/, or copy them to some local location you'll
> remember to delete, and as long as they're in a folder called laslib,
> you'll be able to point the compiler to the parent folder with:
>
> export laslib_CFLAGS=-I/path/to/folder # where folder contains laslib/*.hpp
> export laslib_LIBS=-L/path/to/object/files -llaslib
> ./configure
>
> I'm concerned that our .pc files for laslib are our own version and that
> there is no official version. I will get back to you on Tuesday with
> more details on that.
>
> Berin
>
> On 23/08/12 14:06, Mark Seibel wrote:
>> When I try to compile LAG, I have all components present except lidarquadtree.
>>
>> I'm trying to compile the lidarquadtree, and have encountered errors.
>>
>> configure error for LAG is:
>> Package requirements (lidarquadtree >=1.2 were not met:  no package
>> lidarquadtree found.
>>
>> So I went to the lidarquadtree directory in the lidarsf-lag-53d94dd
>> directory and did ./configure and make.
>>
>> Make returned this error:
>> In file included from src/LidarPoint.cpp:34:0:
>> src/LidarPoint.h:38:37: fatal error: laslib/lasdefinitions.hpp: No
>> such file or directory
>> compilation terminated.
>>
>> I have the lasdefinitions.hpp file in the laslib directory, but it is
>> in ../lastools/laslib/inc/lasdefinitions.hpp
>>
>> How do I make configure aware of this file's location?  I know I'm
>> missing something obvious, but I just cant see it.
>>
>> Thanks,
>> Mark
>>
>> On Thu, Aug 23, 2012 at 6:18 AM, Berin Smaldon <besm at pml.ac.uk> wrote:
>>> As I gather, open source LAS viewers have been in short supply for some
>>> time now, and having been talked about for over a year, we're finally
>>> getting around to announcing a GPL licensed LAS viewer that Mike Grant
>>> has been promising since the dawn of time. For now, this only works on Linux, but
>>> I'm already working on the Windows port, the purpose here being to get
>>> people using the software to attract bug reports, ideas and development.
>>> So, feel free to try and get it working, I'll be interested to know how
>>> it co-operates with other systems.
>>>
>>> Here is the splash page: http://arsf.github.com/lag/
>>>
>>> The link explains what to do to build it for your Linux system if you're so inclined, the Windows port is a bit of a way off yet though, but in the pipeline. If it were useful to enough people, I could potentially be persuaded to work out how to build packages for some Linux package managers too.
>>>
>>> I acknowledge that the quality of the source code is poor in places.
>>> There have been a number of student programmers before me having pretty
>>> much free rein over how the program is structured and what conventions
>>> are used. Documentation and improving the quality of the code is high on
>>> my priority list, but not on the top of it. For now, my e-mail address
>>> and the github page are the best sources of information, and will help
>>> me work out how the github wiki pages could be more useful. In a few months when I'm no longer on the project, whatever e-mail address is on the splash screen or latest version of the software will have to do instead.
>>>
>>> Enjoy,
>>> Berin
>>>
>>>
>>> <br />
>>> <hr />
>>> <p><font face="Arial" size="1">
>>> Plymouth Marine Laboratory<br />
>>> Registered Office: <br />
>>> Prospect Place<br />
>>> The Hoe<br />
>>> Plymouth  PL1 3DH
>>> </font></p>
>>>
>>> <p><font face="Arial" size="1">Website: <a href="http://www.pml.ac.uk">www.pml.ac.uk</a>
>>> <br />
>>> <a href="http://www.pml.ac.uk/pdf/PML%20Annual%20Review%202011_2.pdf">Click here for the latest PML Annual Review</a>
>>> <br />
>>> Registered Charity No. 1091222<br />
>>> PML is a company limited by guarantee<br />
>>> registered in England & Wales<br />
>>> company number 4178503</font></p>
>>>
>>> <p><font face="Arial" size="1" color="green">Please think before you print.</font></p>
>>>
>>> <hr />
>>>
>>> <p><font face="Arial" size="1">This e-mail, its content and any file attachments are confidential.</font></p>
>>>
>>> <p><font face="Arial" size="1">If you have received this e-mail in error please do not copy, disclose it to any third party or use the contents or attachments in any way. Please notify the sender by replying to this e-mail or e-mail forinfo at pml.ac.uk and then delete the email without making any copies or using it in any other way.</font></p>
>>>
>>> <p><font face="Arial" size="1">The content of this message may contain personal views which are not the views of Plymouth Marine Laboratory unless specifically stated.</font></p>
>>>
>>> <p><font face="Arial" size="1">You are reminded that e-mail communications are not secure and may contain viruses. Plymouth Marine Laboratory accepts no liability for any loss or damage which may be caused by viruses.</font></p>
>>>
>>> <hr />
>>> <br />
>>> <br />
>>>
>>> _______________________________________________
>>> Liblas-devel mailing list
>>> Liblas-devel at lists.osgeo.org
>>> http://lists.osgeo.org/mailman/listinfo/liblas-devel
>
>
> <br />
> <hr />
> <p><font face="Arial" size="1">
> Plymouth Marine Laboratory<br />
> Registered Office: <br />
> Prospect Place<br />
> The Hoe<br />
> Plymouth  PL1 3DH
> </font></p>
>
> <p><font face="Arial" size="1">Website: <a href="http://www.pml.ac.uk">www.pml.ac.uk</a>
> <br />
> <a href="http://www.pml.ac.uk/pdf/PML%20Annual%20Review%202011_2.pdf">Click here for the latest PML Annual Review</a>
> <br />
> Registered Charity No. 1091222<br />
> PML is a company limited by guarantee<br />
> registered in England & Wales<br />
> company number 4178503</font></p>
>
> <p><font face="Arial" size="1" color="green">Please think before you print.</font></p>
>
> <hr />
>
> <p><font face="Arial" size="1">This e-mail, its content and any file attachments are confidential.</font></p>
>
> <p><font face="Arial" size="1">If you have received this e-mail in error please do not copy, disclose it to any third party or use the contents or attachments in any way. Please notify the sender by replying to this e-mail or e-mail forinfo at pml.ac.uk and then delete the email without making any copies or using it in any other way.</font></p>
>
> <p><font face="Arial" size="1">The content of this message may contain personal views which are not the views of Plymouth Marine Laboratory unless specifically stated.</font></p>
>
> <p><font face="Arial" size="1">You are reminded that e-mail communications are not secure and may contain viruses. Plymouth Marine Laboratory accepts no liability for any loss or damage which may be caused by viruses.</font></p>
>
> <hr />
> <br />
> <br />
>


More information about the Liblas-devel mailing list