Field3D | A library for storing voxel data on disk and in memory | Storage library

by imageworks C++ Version: Current License: Non-SPDX

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | Field3D Summary

Field3D is a C++ library typically used in Storage applications. Field3D has no bugs, it has no vulnerabilities and it has low support. However Field3D has a Non-SPDX License. You can download it from GitHub.

Field3D is an open source library for storing voxel data. It provides C++ classes that handle in-memory storage and a file format based on HDF5 that allows the C++ objects to be written to and read from disk. The majority of the documentation is available in the project Wiki at

Support

Quality

Security

License

Reuse

Support

Field3D has a low active ecosystem.

It has 284 star(s) with 65 fork(s). There are 47 watchers for this library.

It had no major release in the last 6 months.

There are 35 open issues and 32 have been closed. On average issues are closed in 52 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of Field3D is current.

Quality

Field3D has 0 bugs and 0 code smells.

Security

Field3D has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

Field3D code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

Field3D has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

Field3D releases are not available. You will need to build from source code and install.

Installation instructions are available. Examples and code snippets are not available.

It has 241 lines of code, 12 functions and 3 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of Field3D

Get all kandi verified functions for this library.

Field3D Key Features

No Key Features are available at this moment for Field3D.

Field3D Examples and Code Snippets

No Code Snippets are available at this moment for Field3D.

Community Discussions

Trending Discussions on Field3D

How to figure out where linking to static library of Boost's thread component is postulated when building Field3D?

QUESTION

How to figure out where linking to static library of Boost's thread component is postulated when building Field3D?

Asked 2018-Jul-13 at 10:18

I am building Field3D which links to Boost's thread library. The building environment is listed as follows:

Windows 10 version 1803 64bit
Visual Studio 2015 Update 3
CMake 3.11.4
Release x64 DLL mode in VS
Field3D source package is downloaded from master branch of https://github.com/imageworks/Field3D
Boost is pre-compiled binary of version 1.67.0 for VS2015 (v14.0) 64bit, downloaded from https://sourceforge.net/projects/boost/files/boost-binaries and installed under C:\local\boost_1_67_0 directory.
Doxygen and HDF5 installed properly.

The CMake command line to set up VS2015 is:

cmake -DCMAKE_CONFIGURATION_TYPES=Release -DBUILD_SHARED_LIBS=ON -DCMAKE_INSTALL_PREFIX=C:...\Field3D-master\install -DDOXYGEN_EXECUTABLE="C:\Program Files\doxygen\bin\doxygen.exe" -DHDF5_ROOT="C:\Program Files\HDF_Group\HDF5\1.10.2" -DBOOST_ROOT=C:\local\boost_1_67_0 -DBOOST_INCLUDEDIR=C:\local\boost_1_67_0\boost -DBOOST_LIBRARYDIR=C:\local\boost_1_67_0\lib64-msvc-14.0 -DIlmbase_Base_Dir=C:...\openexr-develop\IlmBase\install_ -G"Visual Studio 14 2015 Win64" ..

Then I open the generated field3d.sln in VS2015 and try to build Field3D project. Errors are reported as below:

...

ANSWER

Answered 2018-Jul-13 at 10:18

After another bunch of hours to check Field3D's building process, I believe the problem is Field3D's failure to make use of Boost's mechanism to disable automatic linking and to enable dynamic linking on Windows. An issue ticket is submitted in hope that the developers of Field3D can fix it in future: https://github.com/imageworks/Field3D/issues/96. Briefly, add the following two commands to copy INTERFACE_COMPILE_DEFINITIONS property of Boost::disable_autolinking and Boost::dynamic_linking import targets to Field3D project

Source https://stackoverflow.com/questions/51302664

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install Field3D

Field3D will look in your platform's standard directories for include files and libraries. If you need to add further library paths, include paths etc., add a "Site.py" file in the root directory. The file ExampleSite.py can be used for reference.

Support

For questions and/or comments, please join the field3d-dev discussion group at Google Groups. http://groups.google.com/group/field3d-dev. The project web page URL is: https://sites.google.com/site/field3d/.

Find more information at: