4 ms·

For a while I worked with Bada, the Korean smartphone OS pushed by Samsung which nobody has ever heard of. (It was actually not bad; apps written in C++ with a

For a while I worked with Bada, the Korean smartphone OS pushed by Samsung which nobody has ever heard of. (It was actually not bad; apps written in C++ with a Java-like class library which all ran inside a single process, targeted at fairly small devices. Our test hardware was this massive plastic brick with daughterboards poking out in all directions all wrapped round this utterly gorgeous curved OLED screen.) You developed on it using a custom IDE which totally wasn't Eclipse (despite being Eclipse) which used gcc as the backend compiler and a bunch of custom tools to generate the deployment packages. Naturally, we ignored the IDE and just used makefiles, so that we could integrate the Bada build into our existing build automation. ...then one update they removed the custom tools and moved their functionality into Eclipse. This meant that the only way to create applications was to open Eclipse, load the project, and then manually press the 'build' button. Naturally, we complained, along with everyone else who used it, and never got an answer. The platform died soon after.

jschwartzi 10y ago
I use CCS and the TI compilers for a processor at work. It's not bad. I was able to move us to a Make-based build system for the pile of artifacts that we use that compiler and gcc for in less than a week. TIs command line tools are pretty useful. (Yes, I have tried CMake, and it is entirely the wrong kind of cross-platform.)
ArkyBeagle 10y ago
"...This meant that the only way to create applications was to open Eclipse"... Surely not. Now, this may have been much more trouble than it was worth, but I very nearly guarantee there was a way to do it from a command line. It's been a while since I Eclipsed, but I (probably erroneously) recall a "generate Makefile" option on most adaptations of it.
- yitchelle 10y ago
  I was also intrigue after reading that. I wondering if gcc and friends were integrated directly into Eclipse? It is possible, but it would be a complete waste of engineering resource.
  - Gibbon1 10y ago
    I think a problem is with a lot of eclipse based embedded studio's is the driver and board support package code is generated from templates via an eclipse plugin written in Java. Also good luck trying to figure out an Eclipse project file without retching. Eclipse + Embedded => Cancer
    - luca_ing 10y ago
      Currently doing that. Retch indeed.
- david-given 10y ago
  We could run gcc fine. The problem was (from memory, this was a while ago) the bespoke tool which bundled up the binary and resource data and signed it to create the installable package. Previously it had been an external binary; but they rewrote it in Java and linked it into the Eclipse binary, and the only hooks were from the Eclipse project build system. The generated makefiles didn't call this because there was nothing to call. However --- good news! I've just found references from 2012 to a thing called MakePackage.jar, which seems to do exactly what we wanted. There certainly wasn't any such thing while I was working on it, so it looks like they changed their mind later. Which would be great, but we'd abandoned the platform by then. Here's what seems to be left of the Bada documentation. http://static.bada.com/contents/tutorials/bada_SDK_1.0.0/badaTutorial.DevelopmentEnvironment.pdf http://static.bada.com/contents/tutorials/bada_SDK_1.0.0/bad...
contingencies 10y ago
I visited Samsung HQ in Suwon, Korea during that period. As I entered I recall being shown "that building is Bada OS", "that building is Windows", "that building is Android". (We were preparing the flagship application for the Galaxy device series launch in the US market, an on-device DRM'd digital video market with pre-loaded/licensed content and carrier billing integration). I guess that was 2010.
Philipp__ 10y ago
Hey I used Samsung Wave, because it came with Bada OS which looked pretty nice (and run much better) compared to Android on similar hardware! Too bad it was pretty much DOA as ecosystem. Interesting story anyway. :)

jschwartzi 10y ago

I use CCS and the TI compilers for a processor at work. It's not bad. I was able to move us to a Make-based build system for the pile of artifacts that we use that compiler and gcc for in less than a week. TIs command line tools are pretty useful. (Yes, I have tried CMake, and it is entirely the wrong kind of cross-platform.)

ArkyBeagle 10y ago

"...This meant that the only way to create applications was to open Eclipse"... Surely not. Now, this may have been much more trouble than it was worth, but I very nearly guarantee there was a way to do it from a command line. It's been a while since I Eclipsed, but I (probably erroneously) recall a "generate Makefile" option on most adaptations of it.

yitchelle 10y ago
I was also intrigue after reading that. I wondering if gcc and friends were integrated directly into Eclipse? It is possible, but it would be a complete waste of engineering resource.
- Gibbon1 10y ago
  I think a problem is with a lot of eclipse based embedded studio's is the driver and board support package code is generated from templates via an eclipse plugin written in Java. Also good luck trying to figure out an Eclipse project file without retching. Eclipse + Embedded => Cancer
  - luca_ing 10y ago
    Currently doing that. Retch indeed.
david-given 10y ago
We could run gcc fine. The problem was (from memory, this was a while ago) the bespoke tool which bundled up the binary and resource data and signed it to create the installable package. Previously it had been an external binary; but they rewrote it in Java and linked it into the Eclipse binary, and the only hooks were from the Eclipse project build system. The generated makefiles didn't call this because there was nothing to call. However --- good news! I've just found references from 2012 to a thing called MakePackage.jar, which seems to do exactly what we wanted. There certainly wasn't any such thing while I was working on it, so it looks like they changed their mind later. Which would be great, but we'd abandoned the platform by then. Here's what seems to be left of the Bada documentation. http://static.bada.com/contents/tutorials/bada_SDK_1.0.0/badaTutorial.DevelopmentEnvironment.pdf http://static.bada.com/contents/tutorials/bada_SDK_1.0.0/bad...

contingencies 10y ago

I visited Samsung HQ in Suwon, Korea during that period. As I entered I recall being shown "that building is Bada OS", "that building is Windows", "that building is Android". (We were preparing the flagship application for the Galaxy device series launch in the US market, an on-device DRM'd digital video market with pre-loaded/licensed content and carrier billing integration). I guess that was 2010.

Philipp__ 10y ago

Hey I used Samsung Wave, because it came with Bada OS which looked pretty nice (and run much better) compared to Android on similar hardware! Too bad it was pretty much DOA as ecosystem. Interesting story anyway. :)