Dear Dan, Just FYI. Today I tried
conda build spdlib -c conda-forge on another computer with Ubuntu 14.04 system. The error message is exactly the same as attached in the email yesterday. Hope it helps. Regards, Tiangang On Sun, Nov 27, 2016 at 7:14 PM, Tiangang Yin <tiangang.yin...@gmail.com> wrote: > Dear Dan, > > > Thank you very much for your reply. > I ran conda build spdlib after hg clone the conda-recipes repository. > Please find the file of build errors in the file enclosed. Do you have any > idea why the building failed? The problem seems to be not linked with any > external library but spdlib itself (or cmake). > > BTW, I managed to build the latest python binding folder from (hg clone > https://bitbucket.org/petebunting/spdlib) with path references to the > conda-installed dependency folders, but only with ubuntu 14.04... The > "import spdpy" error messages showed in the previous emails are from > building in ubuntu 16.04. However, another package, the 3D-point-viewer > would could only be built with ubuntu 16.04 but not ubuntu 14.04... I will > send you this information tomorrow... > > > Regards, > > Tiangang > > > > > > On Fri, Nov 25, 2016 at 6:38 PM, Daniel Clewley <daniel.clew...@gmail.com> > wrote: > >> Hi, >> >> The Python bindings for SPDLib aren't included in the most recent conda >> builds of SPDLib. They depend on Boost Python which was proving difficult >> to compile for Python 3 and I wasn't using the Python bindings so stopped >> including them within the builds. >> >> The easiest way to get the SPDLib Python bindings would be to compile >> using the conda build system, the most recent recipe for SPDLib is >> available from https://bitbucket.org/gillins/conda-recipes. We now use >> the Boost build from conda-forge, I'm not sure if this includes the Python >> libraries, if it doesn't you will need to build Boost in conda as well. If >> you manage to get it working and submit a pull request we can include >> Python bindings in future builds. >> >> As for the LASWave2UPD.py script, this is no longer needed as SPDLib can >> now import LAS 1.3 files natively so you just use spdtranslate, as with >> discrete LAS files. >> >> Thanks, >> >> Dan >> >> >> On 23 Nov 2016, at 21:08, sahar benhmida <sahar.ben.hm...@gmail.com> >> wrote: >> >> Dear Dr. Bunting, >> >> My name is Sahar from CESBIO laboratory of Toulouse. I managed with my >> collegue Tiangang to install the latest version of SPDlib. >> We tried then, to read LAS 1.3 LiDAR files with python script >> LASWaves2UPD.py: >> "python LASWave2UPD.py -waves file.las file.spd" >> but we got this message error : >> >> Starting to process 18430 points >> Traceback (most recent call last): >> File "LASWave2UPD.py", line 1262, in <module> >> obj.run() >> File "LASWave2UPD.py", line 1210, in run >> self.readLASWaves(lasHeaderData, inputFile, outputFile) >> File "LASWave2UPD.py", line 381, in readLASWaves >> wave_data = struct.unpack("=%db" %wave_size, wave_dat) >> struct.error: unpack requires a string argument of length 256 >> >> We wonder if you have any idea about this. >> We appreciate again all your help >> >> >> Sincerely, >> >> Sahar and Tiangang >> >> >> 2016-11-14 18:06 GMT+01:00 Tiangang Yin <tiangang.yin...@gmail.com>: >> >>> Dear Pete and Dan, >>> >>> Thank you very much for the above instructions. I did not succeed to >>> compile spdlib from source code, but I succeeded to install the executables >>> from conda. As far as I understand, conda would automatically install >>> all the dependencies that are needed by SPDlib. >>> >>> However, I can not find the python binding file "spdpy.so" from >>> anywhere. I suppose that conda would only install the compiled binaries >>> instead of python binding. Am I right? >>> >>> Therefore, I hg cloned the repository and compiled the python folder. It >>> compiles successfully, but when I >>> >>> import spdpy >>> >>> The following error message shows: >>> >>> ImportError: /usr/local/site-packages/spdpy.so: undefined symbol: >>> _ZN6spdlib13SPDFileReader14readHeaderInfoENSt7__cxx1112basic >>> _stringIcSt11char_traitsIcESaIcEEEPNS_7SPDFileE >>> >>> I wonder if you have any idea what happens? >>> >>> I also tried to compile spdlib source code after conda figured out all >>> the dependancies, and I got an error message for HDF5: >>> >>> src/libspdio.so.3.0.0: undefined reference to >>> `H5::H5Location::createAttribute(std::__cxx11::basic_string<char, >>> std::char_traits<char>, std::allocator<char> > const&, H5::DataType const&, >>> H5::DataSpace const&, H5::PropList const&) const' >>> src/libspdio.so.3.0.0: undefined reference to >>> `H5::H5File::H5File(std::__cxx11::basic_string<char, >>> std::char_traits<char>, std::allocator<char> > const&, unsigned int, >>> H5::FileCreatPropList const&, H5::FileAccPropList const&)' >>> src/libspdio.so.3.0.0: undefined reference to >>> `H5::CompType::insertMember(std::__cxx11::basic_string<char, >>> std::char_traits<char>, std::allocator<char> > const&, unsigned long, >>> H5::DataType const&) const' >>> src/libspdio.so.3.0.0: undefined reference to >>> `H5::CommonFG::createDataSet(std::__cxx11::basic_string<char, >>> std::char_traits<char>, std::allocator<char> > const&, H5::DataType const&, >>> H5::DataSpace const&, H5::DSetCreatPropList const&) const' >>> src/libspdio.so.3.0.0: undefined reference to >>> `H5::CommonFG::createGroup(std::__cxx11::basic_string<char, >>> std::char_traits<char>, std::allocator<char> > const&, unsigned long) const' >>> src/libspdio.so.3.0.0: undefined reference to >>> `H5::Attribute::write(H5::DataType const&, >>> std::__cxx11::basic_string<char, std::char_traits<char>, >>> std::allocator<char> > const&) const' >>> src/libspdio.so.3.0.0: undefined reference to >>> `H5::CommonFG::openDataSet(std::__cxx11::basic_string<char, >>> std::char_traits<char>, std::allocator<char> > const&) const' >>> collect2: error: ld returned 1 exit status >>> CMakeFiles/spdtileimg.dir/build.make:98: recipe for target 'spdtileimg' >>> failed >>> make[2]: *** [spdtileimg] Error 1 >>> CMakeFiles/Makefile2:142: recipe for target >>> 'CMakeFiles/spdtileimg.dir/all' failed >>> make[1]: *** [CMakeFiles/spdtileimg.dir/all] Error 2 >>> Makefile:149: recipe for target 'all' failed >>> make: *** [all] Error 2 >>> >>> It seems like that there is am version conflict with HDF5... >>> >>> I wonder how can I get python binding working with conda installation. >>> Otherwise I can not use the python importers to convert other files into >>> SPD format. >>> >>> BTW, I also would like to know if the point viewer is also compiled with >>> Conda. Do I need to install that from https://sourceforge.net/p >>> rojects/spdpointsviewer/ ? >>> >>> I appreciate again all your help. >>> >>> >>> >>> Sincerely, >>> >>> Tiangang >>> >>> >>> >>> >>> On Thu, Oct 27, 2016 at 7:02 PM, Daniel Clewley <d...@pml.ac.uk> wrote: >>> >>>> Hi Tiangang, >>>> >>>> I updated SPDLib to use LASlib in the latest version, see this pull >>>> request for more details and justification: >>>> https://bitbucket.org/petebunting/spdlib/pull-requests/1. As part of >>>> this the code was also updated for GDAL 2. >>>> >>>> To compile the latest version of SPDLib you need GDAL 2 or later and >>>> LAStools from https://github.com/LAStools/LAStools. The makefile for >>>> LAStools doesn't include an install command so you will need to manually >>>> copy the library and header files or pass their location to CMake. >>>> >>>> To get a version for SPDLib which works with LASlib you need to need to >>>> checkout the version tagged as 'Version_3_2'. This requires GDAL <= 1.11 >>>> and libLAS version 1.7, the code wasn't updated to work with libLAS 1.8. >>>> >>>> Hope this helps, >>>> >>>> Dan >>>> >>>> >>>> On 27/10/16 10:46, Tiangang Yin wrote: >>>> >>>> Dear Pete and Dan, >>>> >>>> >>>> Thank you very much for your prompt reply. Yesterday, I succeeded to >>>> compile the stable version of spdlib (20130504) by reverting the gdal and >>>> liblas to older versions. I would appreciate if I can get more instructions >>>> about laslib compilation and installation. At the same time, I will try to >>>> work with conda. >>>> >>>> >>>> >>>> Regards, >>>> >>>> Tiangang >>>> >>>> >>>> On Thu, Oct 27, 2016 at 3:36 PM, Pete Bunting <petebunt...@mac.com> >>>> wrote: >>>> >>>>> Dear Tiangang, >>>>> >>>>> We have moved SPDLib away from using LibLAS ( <http://www.liblas.org> >>>>> http://www.liblas.org) to using laslib (i.e., from lastools; >>>>> https://github.com/LAStools/LAStools) as it supports LAS 1.3 with >>>>> waveforms. >>>>> >>>>> Dan Clewley (cc’d), compete led this work so he might be able to >>>>> provide advice on the best way to compile laslib. >>>>> >>>>> Alternatively, we make binary versions available via conda. If you >>>>> install miniconda ( <http://conda.pydata.org/miniconda.html> >>>>> http://conda.pydata.org/miniconda.html) and the run: >>>>> >>>>> conda install -c conda-forge -c rios spdlib >>>>> >>>>> Then it will install the latest version of SPDLib. >>>>> >>>>> Many thanks, >>>>> >>>>> Pete >>>>> >>>>> >>>>> >>>>> On 26 Oct 2016, at 08:19, Tiangang Yin < <tiangang.yin...@gmail.com> >>>>> tiangang.yin...@gmail.com> wrote: >>>>> >>>>> Dear Dr. Bunting, >>>>> >>>>> >>>>> My name is Tiangang from CESBIO laboratory of Toulouse. I have several >>>>> questions related to the SPDlib installation, and I hope you could help >>>>> me. >>>>> >>>>> 2 years ago, I was using the SPDlib to process our simulated LiDAR >>>>> data. It was working fine. Recently, I tried to reinstall SPDlib on my new >>>>> computer using the latest commit from >>>>> >>>>> hg clone https://bitbucket.org/petebunting/spdlib spdlib >>>>> >>>>> The installation gives me several missing functions referring to >>>>> several functions and includes files from LAStools ( >>>>> <https://rapidlasso.com/lastools/>https://rapidlasso.com/lastools/), >>>>> or maybe libLAS. >>>>> >>>>> For example, the compilation error shows: >>>>> >>>>> In file included from /home/ctpp/GIT/spdlib/include/ >>>>> spd/SPDIOFactory.h:43:0, >>>>> from /home/ctpp/GIT/spdlib/src/spd/ >>>>> SPDIOFactory.cpp:24: >>>>> /home/ctpp/GIT/spdlib/include/spd/SPDLASFileImporter.h:33:25: fatal >>>>> error: lasreader.hpp: No such file or directory >>>>> #include <lasreader.hpp> >>>>> ^ >>>>> compilation terminated. >>>>> make[2]: *** [src/CMakeFiles/spd.dir/spd/SPDIOFactory.cpp.o] Error 1 >>>>> make[1]: *** [src/CMakeFiles/spd.dir/all] Error 2 >>>>> make: *** [all] Error 2 >>>>> >>>>> The lasreader.hpp has already been removed from libLAS 1.7.0, and the >>>>> latest version of libLAS is 1.8.1. >>>>> >>>>> I can imagine that SPDlib might need a specific version of libLAS to >>>>> compile in the latest version. However, I can not find any instructions on >>>>> how the installation of configuration of LAStools for >>>>> successful compilation of SPDlib. For libLAS, I think several functions >>>>> changes from the latest version of the library. Could you let me know what >>>>> version of libLAS are you using, or any instructions to install LAStools? >>>>> >>>>> I would also appreciate if you can suggest on the versions of all the >>>>> dependencies of spdlib, including: >>>>> >>>>> CGAL >>>>> gdal >>>>> gmp >>>>> gsl >>>>> hdf5 >>>>> laszip >>>>> libLAS >>>>> mpfr >>>>> proj >>>>> qt >>>>> xerces >>>>> zlib >>>>> >>>>> >>>>> Best Regards, >>>>> >>>>> -- >>>>> Tiangang >>>>> tiangang.yin...@gmail.com >>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> Tiangang >>>> tiangang.yin...@gmail.com >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> The Command Line: Reinvented for Modern Developers >>>> Did the resurgence of CLI tooling catch you by surprise? >>>> Reconnect with the command line and become more productive. >>>> Learn the new .NET and ASP.NET CLI. Get your free >>>> copy!http://sdm.link/telerik >>>> >>>> >>>> >>>> _______________________________________________ >>>> spdlib-develop mailing >>>> listspdlib-develop@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/spdlib-develop >>>> >>>> >>>> Please visit our new website at www.pml.ac.uk and follow us on Twitter >>>> @PlymouthMarine >>>> >>>> Winner of the Environment & Conservation category, the Charity Awards 2014. >>>> >>>> Plymouth Marine Laboratory (PML) is a company limited by guarantee >>>> registered in England & Wales, company number 4178503. Registered Charity >>>> No. 1091222. Registered Office: Prospect Place, The Hoe, Plymouth PL1 >>>> 3DH, UK. >>>> >>>> This message is private and confidential. If you have received this >>>> message in error, please notify the sender and remove it from your system. >>>> You are reminded that e-mail communications are not secure and may contain >>>> viruses; PML accepts no liability for any loss or damage which may be >>>> caused by viruses. >>>> >>>> >>> >>> >>> -- >>> Tiangang >>> tiangang.yin...@gmail.com >>> >> >> > > > -- > Tiangang > tiangang.yin...@gmail.com > -- Tiangang tiangang.yin...@gmail.com
------------------------------------------------------------------------------
_______________________________________________ spdlib-develop mailing list spdlib-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/spdlib-develop
