darknet VS efficientdet-pytorch

YoloV3/4 is C based if that counts: https://github.com/AlexeyAB/darknet

This is all well-known information, see any (and all!) previous discussions when YOLOv5 comes up. For details: https://github.com/AlexeyAB/darknet/issues/5920

2) YOLOv5 is both slower and less precise than YOLOv4. Why use YOLOv5? Source: https://github.com/AlexeyAB/darknet/issues/5920

So my recommendation is you stuck with Darknet/YOLO and use v4 of YOLO. The Darknet framework license is definitely suitable for commercial use: https://github.com/AlexeyAB/darknet/blob/master/LICENSE

Still to long. Here's my favourite license: https://github.com/AlexeyAB/darknet/blob/master/LICENSE

When YOLOv7 was out, I built a web app to test it against the classic YOLOv4 and shared it with my team, then deployed it online to share with the community.

If you're worried about performance, you shouldn't be using YOLOv5 since it is slower (and less accurate!) than YOLOv4. Source: https://github.com/AlexeyAB/darknet/issues/5920

I looked around online but I only found this post discussing a related issue, leading me to think there seems to be some sort of compatibility issue going on here. And I think this is the most recent version of the file I am trying to compile located on the exact same folder where my copy is and when I opened it it shows CUDA 11.1 in line 307.

However, there are papers on oriented object detectors (see https://arxiv.org/pdf/1911.07732.pdf) for example. In that paper, they do achieve better results using oriented bounding boxes. If you want to go down that route, I would suggest using the EfficientDet model, because the PyTorch code that you'll find for it is quite easy to understand and modify. For example, I've taken https://github.com/zylo117/Yet-Another-EfficientDet-Pytorch, and modified it to include a "thing-ness" logit, and this was pretty easy to do. Classic EfficientDet models only include logits (aka output neurons that get softmax-ed) for each class, and if any one of these class neurons is greater than 0.5, then it is considered "a thing". Anyway - that's digression, but my point is that I've thought about adding oriented box support to an EfficientDet model, and it didn't seem to be too hard, although I haven't actually done it. If I was to start now, I would probably go with https://github.com/rwightman/efficientdet-pytorch, since Ross Wightman's models are becoming a de-facto standard in the PyTorch world for all things image-related.