Flashing marauder 0.11 on esp32-c3 missing steps

[z1poc]

Hi kashmir54,

I have a spare esp32-c3 (is a variant of the board esp32-c3-devkitm-1) and I would like to compile marauder and upload it on it.
I saw your work on voyagerRF and seems the only example of compiling marauder for the esp32-c3 variant.

I found only another guy on reddit but he didnt release any info about the fine tuning for compiling it.
(see: https://www.reddit.com/r/flipperzero/comments/10efznh/finally_i_got_an_esp32c3_working_with_marauder/ )

I see that in the tutorial you wrote:
WARNING: This tutorial is valid for Marauder v0.10.7 or before, version v0.11.0 requires tricky configurations that won't be explained in this page. If you already have marauder firmware, use the update from micro SD card option, it will be painless. If you installed evilportal or other firmware and you don't have the possibility to update from the micro sd card, I suggest you install this v0.10.0 version and then update from the sd card. If you are going to flash the VoyagerRF's ESP32 or connect its USBC to your computer or to a power source, make sure to unplug the VoyagerRF from your flipper in order to avoid malfunctions or data corruption on your Flipper's micro SD card.

what are the missing steps to setup the environment and compile the latest version?
can you share it?
would be nice also to do some pull request to justmekoko repo to make it public.

thanks

[kashmir54]

Hello @z1poc

As you compile, you will see that there are some errors in the LinkedList class. That's because the library used on Marauder's Evilportal includes "ESPAsyncWebServer.h", which also has a class called LinkedList declared. In this case, both collide and they don't have the same methods. That is why the compiler fails to retrieve .get method.

I didn't share the process because I would need to upload the code with modifications, which is not fare for the original author. I didn't call for a pull request because I might have picked the wrong LinkedList lib at the beginning (judging from the comments on justcallmekoko discord). The solution is to implement namespaces to differentiate references to LinkedList.

I will go over it again when version v0.12.0 gets released, or as soon as I get time to check it again.