On Tue, Jul 26, 2016 at 10:47 PM, TJF <[email protected]> wrote:
> > > Am Mittwoch, 27. Juli 2016 07:11:24 UTC+2 schrieb William Hermans: >> >> Additionally you may wish to start reading about, and understanding what >> a "web appliance" *is*. >> > > Didn't you read the initial post? This isn't the issue here. The Question > is > > Device should be controlled via Web interface. Control includes simple >> configuration >> (few tens parameters), collection of logs, statuses, alarms and simple >> statistics. >> > > I beg to differ. This is the "issue" here. If it is understood what a web appliance *is*, and how they work through the different software stacks. This question then answers it's self. As to how one should work on such a project. Windows, Linux, cross compile, etc ,etc. This is a matter of taste that will come with experience. One of my favorite ways to develop something of this nature however is to create a complete Linux virtual machine mock-up system. Then once I get the mock-up working how I want, I migrate the code to the target platform, and compile natively there. This way there is a very minimal chance of ABI conflicts. But one does need to be wary of potential ABI conflicts. e.g. just do not use anything that requires a specific hardware platform to work ;) -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALHSORoJaSAAzE6%3DEZ-_0OnOYo3qavkHrswtavWeMk1EVnBopQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
