Hello CPP fails fix:
replace -std=c++14 with -std=c++17 in project.json
Hello Java builds OK
Hello MicroPython fails no fix yet
EmBitz
… in progress
requires deselecting GNU C++ 14 from options and passing -std=c++17 in Build options / C++ flags / others
requires copying newer version of GCC from Femto to EmBitz
– from: \IDE-windows-v0.1.5\windows\arm
– to: \EmBitz\1.11\share\em_armgcc
But still fails to create hex file (problem with objcopy, investigating)
arm-none-eabi-objcopy.exe: .\build\hello.hex 64-bit address 0x4b4fa300000000 out of range for Intel Hex file
arm-none-eabi-objcopy.exe:.\build\hello.hex: bad value
I was saying we should depricate the getting started tutorials that use EmBitz not EmBitz it self.
Right now our best option for new commers is femto, FManga did a great job making it
In that case, I think we should still keep the tutorials,
but ‘lock’ them and move them to a designated ‘archive’ section to make it clear that they are only kept for reference purposes.
Which reminds me…
Rather than completely removing the information about the deprecated screen modes,
I think it would be better to move them to a ‘deprecated’ section (in a ‘details’ block) so that the information is still available for historical purposes,
but it is clear that that functionality is no longer available.
If nothing else, these things are an important part of the Pokitto’s story (or history),
so it would be nice to keep a remnant of them rather than allowing them to degrade to word-of-mouth stories.
Being a bit of a newcomer to the community and pokitto development I went through all the various tutorials using the various IDE options (back before my windows machine started having issues) and when @FManga suggested trying FemtoIDE due to my issues with the SD card access it was the only one I hadn’t tried and ended up being by far the simplest and easier setup. Download the appropriate zip file and run it. The best part is (coming from mostly Arduino development) it seems perfectly content to let you use an external editor and jump back to it for building. The only real improvement needed is the compile output history getting cropped with all the lengthy warning messages, any warnings/errors in your project’s code could easily get buried, so -1 for that.
I give it a +10 for built in debugging support using the emulator and gdb, with the option of also using j-link for hardware debugging. I’ll give it another +20 for the detailed breakdown of Flash and RAM usage when clicking on the elf file (that alone is what convinced me to not look back on the CLI build method).
That doesn’t mean it should be the only option (much like people are also free to not use the Arduino IDE at all), but it does greatly simplify the development process from creation to full release. The simplicity, features, and benefits of FemtoIDE seems like it would be the best bet for centering all future tutorials around, especially since there’s very little involved with the setup and use of the IDE which allows the tutorials to focus more on the actual coding. This in turn makes it easier for people to use the environment of their choosing, and there’ll always be help from the community to get any particular setup working.
All in all it’s definitely another amazing product from @FManga. Now if we can just convince him to make a game.
While the emulator environment should be the final goal for developing programs for Pokitto,
PokittoSim is currently the most productive way to make programs. That is mostly due the excellent debugging features in CodeBlocks. It is also the only environment where audio works correctly outside HW.
I think that’s probably subject to opinion,
which is why I’d ideally like to do a public vote to gather people’s opinions.
Does the simulator not work in FemtoIDE?
If so, that’s another good reason for being rid of it.
Requiring people to use more than one IDE if they want to compile their game for both hardware and simulation is a bit much.
