This fixes all the issues I identified when trying to build the ANARI SDK in a Windows environment, and should close #2. Most of the issues were related to symbol exporting.

Hello,

When compiling the Anari SDK on Windows 11 Visual Studio 2019 I get this build error:

8>Generating Code... 8>Done building project "anari_library_example.vcxproj" -- FAILED. 12>------ Build started: Project: anariTutorialDirectLink, Configuration: Release x64 ------ 12>Building Custom Rule C:/Users/Cameron/Downloads/ANARI-SDK/examples/direct_linking/CMakeLists.txt 12>anariTutorialDirectLink.c 12>LINK : fatal error LNK1181: cannot open input file '..\..\Release\anari_library_example.lib' 12>Done building project "anariTutorialDirectLink.vcxproj" -- FAILED. 13>------ Build started: Project: ALL_BUILD, Configuration: Release x64 ------ 13>Building Custom Rule C:/Users/Cameron/Downloads/ANARI-SDK/CMakeLists.txt ========== Build: 8 succeeded, 5 failed, 0 up-to-date, 0 skipped ========== I attempt to continue the build:

1>C:\Users\Cameron\Downloads\ANARI-SDK\examples\example_device\scene\bvh/SweepSAHBuilder.h(294,3): error C2059: syntax error: '{' 1>C:\Users\Cameron\Downloads\ANARI-SDK\examples\example_device\scene\bvh/SweepSAHBuilder.h(294,3): error C2143: syntax error: missing ';' before '{' 1>C:\Users\Cameron\Downloads\ANARI-SDK\examples\example_device\scene\bvh/SweepSAHBuilder.h(301,31): warning C4267: '=': conversion from 'size_t' to 'uint32_t', possible loss of data 1>C:\Users\Cameron\Downloads\ANARI-SDK\examples\example_device\scene\volume\../SceneObject.h(84,9): error C3001: 'declare': expected an OpenMP directive name 1>C:\Users\Cameron\Downloads\ANARI-SDK\examples\example_device\scene\volume\../SceneObject.h(88,9): error C3036: 'bbox_extend': invalid operator token in OpenMP 'reduction' clause 1>C:\Users\Cameron\Downloads\ANARI-SDK\examples\example_device\scene\volume\../SceneObject.h(88,1): error C3016: 'i': index variable in OpenMP 'for' statement must have signed integral type 1>Generating Code... 1>Done building project "anari_library_example.vcxproj" -- FAILED. ========== Build: 0 succeeded, 1 failed, 3 up-to-date, 0 skipped ==========

Am I missing prerequisites? I hope this is helpful.

Kind regards,

Cameron

Is the code ported to Windows ?

I tried building it but came across this error

3>Generating Code...
3>   Creating library C:/Users/yueni/projects/ANARI-SDK/build/Release/anari_library_example.lib and object C:/Users/yueni/projects/ANARI-SDK/build/Release/anari_library_example.exp
3>ExampleDeviceDebugFactory.obj : error LNK2019: unresolved external symbol "public: void __cdecl anari::debug_device::GenericDebugObject::unknown_parameter(struct ANARIDataType,char const *,char const *,struct ANARIDataType)" ([email protected]@[email protected]@@[email protected]@[email protected]) referenced in function "public: virtual void __cdecl anari::debug_device::`anonymous namespace'::array1d::setParameter(char const *,struct ANARIDataType,void const *)" ([email protected]@[email protected][email protected]@@[email protected]@[email protected])
3>ExampleDeviceDebugFactory.obj : error LNK2019: unresolved external symbol "public: void __cdecl anari::debug_device::GenericDebugObject::check_type(struct ANARIDataType,char const *,char const *,struct ANARIDataType,struct ANARIDataType *)" ([email protected]@[email protected]@@[email protected]@[email protected]@Z) referenced in function "public: virtual void __cdecl anari::debug_device::`anonymous namespace'::array1d::setParameter(char const *,struct ANARIDataType,void const *)" ([email protected]@[email protected][email protected]@@[email protected]@[email protected])
3>ExampleDeviceDebugFactory.obj : error LNK2019: unresolved external symbol "public: void __cdecl anari::debug_device::ObjectFactory::unkown_subtype(struct anari::debug_device::DebugDevice *,struct ANARIDataType,char const *)" ([email protected]@[email protected]@@[email protected]@[email protected]@[email protected]) referenced in function "public: virtual struct anari::debug_device::DebugObjectBase * __cdecl anari::debug_device::ExampleDeviceDebugFactory::new_camera(char const *,struct anari::debug_device::DebugDevice *,struct anari::api::Object *,struct anari::api::Object *)" ([email protected]@[email protected]@@[email protected]@[email protected]@[email protected]@[email protected]@Z)
3>C:\Users\yueni\projects\ANARI-SDK\build\Release\anari_library_example.dll : fatal error LNK1120: 3 unresolved externals
3>Done building project "anari_library_example.vcxproj" -- FAILED.
16>------ Build started: Project: anariTutorialDirectLink, Configuration: Release x64 ------
16>anariTutorialDirectLink.c
16>anariTutorialDirectLink.vcxproj -> C:\Users\yueni\projects\ANARI-SDK\build\Release\anariTutorialDirectLink.exe
17>------ Skipped Build: Project: INSTALL, Configuration: Release x64 ------
17>Project not selected to build for this solution configuration 
========== Build: 9 succeeded, 1 failed, 15 up-to-date, 7 skipped ==========

Hi there, Building with intel compilers generates a whole lotta errors related to glm. For example:

[  6%] Building CXX object libs/anari/CMakeFiles/anari.dir/anari_cpp_glm_defs.cpp.o
In file included from /work2/01197/semeraro/frontera/ANARI/external/glm/include/glm/./ext/../detail/type_mat2x2.hpp(6),
                 from /work2/01197/semeraro/frontera/ANARI/external/glm/include/glm/./ext/matrix_double2x2.hpp(5),
                 from /work2/01197/semeraro/frontera/ANARI/external/glm/include/glm/mat2x2.hpp(5),
                 from /work2/01197/semeraro/frontera/ANARI/libs/anari/include/anari/anari_cpp/ext/glm.h(7),
                 from /work2/01197/semeraro/frontera/ANARI/libs/anari/anari_cpp_glm_defs.cpp(5):
/work2/01197/semeraro/frontera/ANARI/external/glm/include/glm/./ext/../detail/type_vec2.hpp(93): error: cannot overload functions distinguished by return type alone
                GLM_FUNC_DECL GLM_CONSTEXPR T const& operator[](length_type i) const;

Using the compiler:

login4.frontera(1091)$ which icc
/opt/intel/compilers_and_libraries_2020.1.217/linux/bin/intel64/icc 

Builds under gcc/9.1.0. (Ya I know, then use gcc...)

Hi,

I'd like to learn more about developing back end for ANARI with a specific interest in targeting offline CPU renderers.

I have built ANARI and toy around with the viewer.

My main development environment will be Ubuntu.

What example code should I start focusing on ? I have watched the OSPray back end development video from the ANARI Webinar 2022

Cheers

For a project I'm working on, I noticed that most of the introspection methods (anariGetObjectSubtypes, anariGetObjectParameters, and anariGetParameterInfo) aren't fully implemented for the example library and device. I've added in preliminary support for the first two introspection methods (but not the last method) for all the objects within the example device that I can find.

In total, this PR adds support for the example device objects: Geometry, Material, Volume, Camera, and Spatial Field. It also fixes support for Renderer (anariGetObjectParameters always returned the same thing for every Renderer subtype despite differences between the subtypes).

This PR does not add support for Sampler or Light (both objects are implemented in the example library as placeholder objects).

In cornell box scene (cornell_box.cpp) there's a possible mistake. There's a check of ANARI_KHR_DEVICE_SYNCHRONIZATION feature (line 275), but it looks like that it should check ANARI_KHR_AREA_LIGHTS

Would you be willing to merge this PR which adds a dedicated subclass for the matte material? It's mostly that currently, with matte being used as an alias for OBJ, one has to set the color parameter via "kd", not "color", and my own sample code then not being compliant with the standard.

FWIW, the only use of matte that I can see in the SDK is found in anariTuturial.cpp, where the diffuse color parameter is not set on the material; i.e., the change set shouldn't break existing behavior.

When build on VS2017, the following error triggers:

Severity Code Description Project File Line Suppression State Error C2100 illegal indirection anari_library_example d:\opensource\anari-sdk\examples\example_device\scene\bvh\SweepSAHBuilder.h 308

The error is a bit vague and did not give the correct fail reason in fact. Since SAHTaskWorkItem is a struct and no constructor provided, a common used initialization method of struct is provided. After the fix, the project build successfully on VS2017.

Trying to set the inTransform parameter for Samplers results in an error since there is no type specialization for ANARI_FLOAT32_MAT4 to float[16] as defined in the spec.

Update json to reflect current spec and extensions

fix debug mode in viewer

Add device json for example and generic devices

Change to offline generation of headers

Need to move the anariGetObjectFeatures and anariGetInstanceFeatures definitions from the header file (anari_feature_utility.h) to the appropriate implementation file (API.cpp??). Having the definitions in the header file causes a multiple definition error when trying to #include <anari/anari_cpp.hpp> as the definitions will appear in multiple places and the linker doesn't like it.

In the spec we have (bold from me)

The ANARI API is specified as a C99 API in order to provide compiler-independent linkage

and

ANARI back-end devices are created by standard implementors and are expected to be distributed, installed, or upgraded independently of the standard API header and front-end library.

I fear this cannot hold when using C++ for the backend API (i.e., implementation directly deriving from the SDK anari::Device): there is no C++ ABI even on the same platform. For example, MSVC has the opposite ordering in the vtable than gcc. MSVC even is not compatible to itself (across versions, thought it seems to be better since 2015). Besides vtable ordering another issue to consider is exception propagation (which we currently use to catch exceptions thrown in backends centrally in the front-end lib).

Furthermore, current SDK implementation is mixing concepts: Device uses virtual functions and implementations derive from it, while Library uses "getProcAddress" and dispatches via function pointers.

This PR proposes an alternative (which is hopefully not that inelegant):

• define two C99 structs of function pointers (one for Device, one for Library), the "vtables"
• on loadLibrary in the init code (a single "getProcAddress") the "vtable" of the backend lib is populated and returned by the implementation
• on newDevice the "vtable" is populated and returned by the implementation
• implementations don't need a wrapper, the addresses of the member functions of their C++ objects can directly be used
• example base classes and utility code to populate those vtables (header only) can be provided by the ANARI SDK for convenience for implementers
• implementations will need to catch exceptions themselves and already use the ANARI error mechanisms (status callback), though utility functions and macros can be provided by the SDK

This is only a proof of concept to facilitate discussion, implementing the interface for Library (except not implemented (un-)loadModule). Implementation for Device would be analogous.

When building the project statically and then installing to CMAKE_INSTALL_PREFIX, on Unix the anchoring logic that determines where to search for libanari_device_XXX.so will base the search path off the folder that the executables are located in (i.e., bin) and thus won't find the actual device library (which is installed to lib). Therefore, static builds currently only work when being used from the build tree.