[Migrated content. Thread originally posted on 26 March 2011]

Hi!

I am currently evaluating MFNE 5.1 and am particularly interested in compiling COM components written in OO COBOL. There is no problem with building these using the IDE but I can't make it work properly using cbllink -d from a command line.

I spent some time looking at how the process works and was hoping it might be possible to use a Make file that could include the TypeLib. It looks to me that the process doesn't do that, compiling the Typelib into a resource file and linking it that way instead.

I don't want to have to manually set up a project for every COM component I want to build. I don't really understand why it forces the extension to be .CBL (my existing legacy is all .COB), and I can't see what this "trigger file" is all about. It doesn't appear to do much. All of my COM stuff is In Process server .DLLs. I wouldn't expect to have to trigger them; just instantiate the Class as an object and then invoke the methods on that object (just like using Server.CreateObject on a web page.)

I guess what I'd really like is a sample batch script I can edit and run from a command line that will let me compile and link my COM Objects, so I don't have to do it through the IDE.

Can anyone help with this, please?

Thanks,

Pion.