src/network-stubs.cpp

#include "configuration.h"

#if (HAS_WIFI == 0)

bool initWifi()
{
    return false;
}

void deinitWifi() {}

bool isWifiAvailable()
{
    return false;
}

#endif

#if (HAS_ETHERNET == 0)

bool initEthernet()
{
    return false;
}

bool isEthernetAvailable()
{
    return false;
}

#endif
first murmurs of ethernet support 2022-10-22 16:29:50 +02:00			`#include "configuration.h"`

			`#if (HAS_WIFI == 0)`

Revert "add a .clang-format file (#9154)" (#9172) I thought git would be smart enough to understand all the whitespace changes but even with all the flags I know to make it ignore theses it still blows up if there are identical changes on both sides. I have a solution but it require creating a new commit at the merge base for each conflicting PR and merging it into develop. I don't think blowing up all PRs is worth for now, maybe if we can coordinate this for V3 let's say. This reverts commit 0d11331d185a60adf84e64ec98642baf6a15a95a. 2026-01-04 12:15:53 +01:00			`bool initWifi()`
			`{`
			`return false;`
			`}`
first murmurs of ethernet support 2022-10-22 16:29:50 +02:00
			`void deinitWifi() {}`

Revert "add a .clang-format file (#9154)" (#9172) I thought git would be smart enough to understand all the whitespace changes but even with all the flags I know to make it ignore theses it still blows up if there are identical changes on both sides. I have a solution but it require creating a new commit at the merge base for each conflicting PR and merging it into develop. I don't think blowing up all PRs is worth for now, maybe if we can coordinate this for V3 let's say. This reverts commit 0d11331d185a60adf84e64ec98642baf6a15a95a. 2026-01-04 12:15:53 +01:00			`bool isWifiAvailable()`
			`{`
			`return false;`
			`}`
first murmurs of ethernet support 2022-10-22 16:29:50 +02:00
			`#endif`

			`#if (HAS_ETHERNET == 0)`

Revert "add a .clang-format file (#9154)" (#9172) I thought git would be smart enough to understand all the whitespace changes but even with all the flags I know to make it ignore theses it still blows up if there are identical changes on both sides. I have a solution but it require creating a new commit at the merge base for each conflicting PR and merging it into develop. I don't think blowing up all PRs is worth for now, maybe if we can coordinate this for V3 let's say. This reverts commit 0d11331d185a60adf84e64ec98642baf6a15a95a. 2026-01-04 12:15:53 +01:00			`bool initEthernet()`
			`{`
			`return false;`
			`}`
first murmurs of ethernet support 2022-10-22 16:29:50 +02:00
Revert "add a .clang-format file (#9154)" (#9172) I thought git would be smart enough to understand all the whitespace changes but even with all the flags I know to make it ignore theses it still blows up if there are identical changes on both sides. I have a solution but it require creating a new commit at the merge base for each conflicting PR and merging it into develop. I don't think blowing up all PRs is worth for now, maybe if we can coordinate this for V3 let's say. This reverts commit 0d11331d185a60adf84e64ec98642baf6a15a95a. 2026-01-04 12:15:53 +01:00			`bool isEthernetAvailable()`
			`{`
			`return false;`
			`}`
first murmurs of ethernet support 2022-10-22 16:29:50 +02:00
			`#endif`