Author Topic: Compilers for development on ecomstation  (Read 2778 times)

PAUL555

  • Jr. Member
  • **
  • Posts: 60
    • View Profile
Compilers for development on ecomstation
« on: 2008.04.22, 18:18:46 »

 Which compilers are used for the following : 

          (1) Ecomstation operating system development.   
          (2) Applications which run on ecomstation.   

 Paul   


RobertM

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2034
    • View Profile
    • A.I.BuiltPC - using OS/2 Warp Server & eComStation for Custom Web and Database Solutions
Re: Compilers for development on ecomstation
« Reply #2 on: 2008.04.22, 22:29:28 »
Paul555,

In addition to Eugene's list, various parts of eComStation (and OS/2) were compiled using IBM C-Set/2, VAC++ v3 and v4, and MS C Compiler.

None of which, in the proper state (ie: able to compile OS/2 code) is available. MS dropped OS/2 support entirely with their new packages, and C-Set/2 was replaced with VAC++ which IBM no longer maintains except for internal needs.

Robert
|
|
Kirk's 5 Year Mission Continues at:
Star Trek New Voyages
|
|


NNYITGuy

  • Jr. Member
  • **
  • Posts: 94
  • IT Consultant - eCS & W32 Solutions for Businesses
    • View Profile
Re: Compilers for development on ecomstation
« Reply #3 on: 2008.04.23, 04:27:26 »
Paul555,

I am using WDSibyl.  Although I am fairly new to WDSibyl, I have experimented and built prototypes for different project ideas.  I really like what I see.  The demos are good at explaining and demonstrating WDSibyl's capabilities.  I will be building several vertical market apps in the near future.

Regards,
Todd
Todd J Simpson (IT Consultant)
Business Automation Technologies
(Professional Products and Services.  Business to Business...)

Paul Smedley

  • Sr. Member
  • ****
  • Posts: 322
    • View Profile
Re: Compilers for development on ecomstation
« Reply #4 on: 2008.04.23, 05:33:00 »

 Which compilers are used for the following : 

          (1) Ecomstation operating system development.   
          (2) Applications which run on ecomstation.   

I'm using:
- GCC 3.3.5CSD3 for porting applications
- OpenWatcom 11 for Uniaud

Cheers,

Paul

Terry

  • Jr. Member
  • **
  • Posts: 73
    • View Profile
Re: Compilers for development on ecomstation
« Reply #5 on: 2008.04.23, 15:19:13 »
Paul555,

I am using WDSibyl.  Although I am fairly new to WDSibyl, I have experimented and built prototypes for different project ideas.  I really like what I see.  The demos are good at explaining and demonstrating WDSibyl's capabilities.  I will be building several vertical market apps in the near future.

Regards,
Todd

There are two OS/2 eZine articles that also help explain Sibyl as pre-WDSibyl...

Sibyl, a Visual Development Environment for OS/2...
http://www.os2ezine.com/20001216/sibyl.html

ODBC on OS/2 Part 12...
http://www.os2ezine.com/20020416/page_7.html

Pete

  • Hero Member
  • *****
  • Posts: 865
    • View Profile
Re: Compilers for development on ecomstation
« Reply #6 on: 2008.04.23, 21:30:37 »
Hi Paul


WDSibyl provides a fairly good RAD package very similar to Borland's Delphi (somewhere around Delhpi2/3 time period). I used it to put together a USB configuration tool that I think I can claim has been of help/use to a few people http://hobbes.nmsu.edu/pub/os2/system/usbcfgb7a.zip

However, it does seem that WDibyl has some limitations. The main 1 I find is that currently the documentation is (mainly) in German which means a few problems with interpretation for non-German speakers like myself. Yes, translation websites can help a little but often introduce a lot of confusion (and nonsense) due to technical terms involved.

Also larger projects can run into problems where when adding new items to existing forms it becomes impossible to give those new items a meaningful name ie I recently looked at adding a RadioGoup containing 2 Radio buttons to the USBcfg app and found that I was stuck with RadioButton1 and RadioButton2 as names - the system would not let me change those to anything else...

To overcome that means starting a new project with a blank form and building each page of the app again - and then hooking up the existing code to that new project. A bit frustrating and time consuming...


However, having had a moan about the WDSibyl drawbacks I also ought to add that I would not know where/how to start building the app in c/c++ despite having qualified as a c programmer years ago; must admit that I have not really used that skillset "in anger" at all since the last exam of the c course  :-)

I am probably just being a bit lazy but the visual building of an application interface is very easy with WDSbyl - bearing in mind the possible problems that you could encounter at a later date when trying to add/change an existing application's interface.

Regards

Pete