Hi @lleachii Manufacturers of OpenWRT devices would love to tell their potential customers where to get their products, which the extra field on the ToH is for. And, of course, the producers will be okay with filling that additional column in the ToH's DataEntry form.
So my question remains unanswered: who should I contact for suggestions or questions about the "Table of Hardware" when you mentioned that "tmomas no longer has an account on the Forum"?
Hi @lleachii, Please correct me if my understanding of OpenWRT is incorrect: OpenWRT is like the Android to cell phones - I can run my apps on any smartphone if labelled as "Android" phones. So I can ensure the apps I build on OpenWRT are runnable on any OpenWRT-compatible router without worrying about who made that router.
Note: I'm assuming you meant 'build for', not 'build on'.
That might work, if your app is built using only components/languages built into all OpenWrt flavors.
I believe, that reduces your choices down to POSIX Shell script and UCode, since both are interpreted on-target using built-in (+ difficult-to-remove) binaries.
Hi @lleachii, Please correct me if my understanding of OpenWRT is incorrect: OpenWRT is like the Android to cell phones - I can run my apps on any smartphone if labelled as "Android" phones.
Your understanding is incorrect.
Thank you for pointing out the discrepancies in my understanding.
Regarding my comparison of OpenWRT to Android, I realize now that my analogy might not fully capture the nuances. Could you please clarify where my understanding of OpenWRT is incorrect? I’m keen to understand the distinctions better.
So I can ensure the apps I build on OpenWRT are runnable on any OpenWRT-compatible router without worrying about who made that router.
This is not the case with OpenWrt.
Additionally, I’d appreciate it if you could elaborate on why the statement about ensuring app compatibility across all OpenWRT-compatible routers might not hold true. I’m interested in learning more about OpenWRT's use cases and how it differs from the Android model in terms of application compatibility.
There are other detailed explanations on other pages in the Developer Guide section of the Wiki as well; but since I'm unsure if your inquiry is regarding:
compatibility with manufacturers that call their firmware "OpenWrt"; or
compatibility of non-processor-specific official OpenWrt packages
The later is supported on devices running official OpenWrt already - but in general, packages are processor-specific.
Lastly, unlike Android, there's not a concept of self-contained applications versus: dependencies and conflicting packages of software - so that also makes your query not analogous to Androids.
Thank you for the explanation, @lleachii. I’m still trying to wrap my head around the concept.
In my experience, I usually place my source code folder in the OpenWrt package directory and build the system using make menuconfig (to select the hardware) and then make to compile the system. My concern is that I don’t have to modify my code when switching devices, which makes me wonder why application compatibility wouldn’t be consistent across different routers running OpenWrt.
compatibility with official OpenWrt for the same CPU/target
This is also supported officially.
The first is unknown and hence unsupported. You won't clarify it's difficult to provide a clear answer.
Are your questions in reference to a device running a firmware built from an official OpenWrt SDK downloaded at a CPU/target from https://downloads.openwrt.org - or a new device firmware built using some other official OpenWrt development method?
I’m glad we had a discussion about OpenWrt compatibility, but it seems we’ve been off the original topic of this post. I apologize if I missed any response regarding my previous question.
Could you please clarify who has replaced "tmomas" on the forum when you mentioned:
tmomas no longer has an account on the Forum.
Additionally, I need to know whom I should contact to update the information on the contact page.