thx for answering… but it’s not the answer I expected.
I did check the samples. And as I wrote it is not obvious which parts are really part of the API and which belongs to the samples and have to be build.
So when the Documentation tells me I can use the elements directly I expect them to be included in an existing library, rather then figuring out which one I have to build on my own as e.g. the mentioned NvJPEGEncoder-class.
On the other Hand there is also a NvBuffer-class listed in the API and inside the samples include/common classes… but NvBuffer-related stuff is usable via libnvbuf-utils.so (well… unless it is not a special same-named-samples NvBuffer-class)
Documentation → Jetson Linux API Reference: Main Page
NvJPEGEncoder → Jetson Linux API Reference: NvJPEGEncoder Class Reference
NvBuffer → Jetson Linux API Reference: NvBuffer Class Reference
Also the samples aren’t really a help here cause every single sample compiles with every class from the common class folder (via samples/Rules.mk) and links against every library listed in the Rules.mk… so it’s more guessing/filtering what is really essentially needed than a dedicated help…
in samples 05_jpeg_encode Makefile:
SRCS := ... $(wildcard $(CLASS_DIR)/*.cpp)
@echo "Linking: $@"
$(CPP) -o $@ $(OBJS) $(CPPFLAGS) $(LDFLAGS)
and in samples/Rules.mk:
CLASS_DIR := $(TOP_DIR)/samples/common/classes
LDFLAGS += \
-lpthread -lv4l2 -lEGL -lGLESv2 -lX11 \
-lnvbuf_utils -lnvjpeg -lnvosd -ldrm \
-lcuda -lcudart \
-lnvinfer -lnvparsers -lnvonnxparser \
... other lib folders ...
Well I think it is quiet obvious that every thing should/may work when I link it to the world and compile every class I can find… but I won’t call it a strategy or solution ;)
So once again I would reference to my previous Questions:
What is really part of the documented API and directly usable…? (btw. what is the meaning of directly usable in this case?)
And when the stated classes are part of the API… why do they come with the samples-code and are build via/inside them as if thy where little unimpressive helping classes?
And when everything in common classes is build anyway (regardless of it’s use) with every single sample-code, why there is not just an precompiled/existing or via JetPack installed library containing the documented API elements?