17-02-2023, 12:15 PM
15-03-2023, 11:28 AM
Hi,
I skipped the concept of "one-tool-for-all" which I had in the EmBlocks days.
Nowadays 99% is using ARM devices so it's a lot of maintenance for just a few use cases.
I think it's better to switch to code::blocks for non-ARM devices if you want to have the same look-and-feel as EB.
I skipped the concept of "one-tool-for-all" which I had in the EmBlocks days.
Nowadays 99% is using ARM devices so it's a lot of maintenance for just a few use cases.
I think it's better to switch to code::blocks for non-ARM devices if you want to have the same look-and-feel as EB.
25-04-2023, 02:12 PM
(15-03-2023, 11:28 AM)embitz Wrote: [ -> ]Hi,
I skipped the concept of "one-tool-for-all" which I had in the EmBlocks days.
Nowadays 99% is using ARM devices so it's a lot of maintenance for just a few use cases.
I think it's better to switch to code::blocks for non-ARM devices if you want to have the same look-and-feel as EB.
Hi Gerald,
For me just add the possibility to add more custom toolchain empty slot will be perfect, I have at job different project using different GCC toolchain version. It will be nice to have this possibility instead of just one custom toolchain.
thank!