Mike

> alright that works now. Don't you think that those errors should be more readable to the user? Agreed. I've had a dig into exactly what's going on here using...

I think the issue could be `SMING_HOME`, final 'sming' directory should be 'Sming', i.e. `/Users/ianaber/documents/projects/ESP8266-VSCode/sming/Sming` NOT `/Users/ianaber/documents/projects/ESP8266-VSCode/sming/sming`

@IanAber I had similar issues migrating from Windows to GNU/Linux development, as Windows filesystems have historically also been case insensitive. If you take a look at `util.mk` (in the main...

> > > Why is it important to have an ESP_VARIANT ? Are you expecting the same variant in more then one architecture. From a SMING user perspective, If I...

Not just beginners actually. It should help with maintainability for both the framework and user projects. At present, if I build the `Basic_Serial` sample then I'd expect it to just...

@kpishere Thank you for this. It's an interesting sample, and as you mention in the README does raise some issues with the framework (memory, mDNS). I've got the sample running...

@kpishere I've pushed some commits to your repo. as a review, hopefully helpful.

Thanks, that is helpful to see, and certainly a lot simpler than adopting a whole separate system for it. Perhaps here we can discuss how Sming presents these options to...

For PR #2171 I propose that the information provided by some build variables (see below) is placed instead in a hardware configuration file attached to the project (and under revision...

Here is an example to show the general structure of the hardware configuration file. I'll update this as things progress: ``` { "name": "Standard hardware config", "arch": "Esp8266", "flash-size": "4M",...