[omniORB] Running Example Echo for omniORB-4.1.1

Duncan Grisby duncan at grisby.org
Thu Jan 17 10:15:12 GMT 2008


On Thursday 10 January, charles bartlett wrote:

> When I do what you suggest, after the final make command - I get a
> message asking me to make a selection in "../../../config/config.mk to
> select the appropriate platform" and the build stops.

You haven't done what I suggest. You are executing make in the source
tree, not a suitably configured build tree.

[...]
> A suggestion: it seems natural to derive programs using omniORB from the
> examples. For the Python case, it is very easy to do so. For C++, one
> most likely would like to quickly divorce from your build system.

Indeed. The omniORB build system is over-complex and convoluted, but it
has the advantage that it works on all platforms that omniORB builds on.
Replacing it with something simpler is really hard because there are so
many platform differences to cope with.

> However, the set of make files is fairly involved. Perhaps you could add
> a comment to your documentation where you state how to easily extract
> the build steps for any given example, including switches, libraries
> used etc. One can dig it out, as I did, but it took me a few hours. You
> make some comments along these lines in your installation notes, but a
> user would really like a quick and easy way to duplicate the commands to
> build any of the examples.

The problem is that the options required are different for each
platform, and there are a lot of platforms. The easiest way to work out
the options for your platform is to build the examples (properly, in the
build tree), and see the options that are used.

If you come up with some simple makefiles for your platform, why don't
you contribute them to the project by putting them on the Wiki?

Duncan.

-- 
 -- Duncan Grisby         --
  -- duncan at grisby.org     --
   -- http://www.grisby.org --



More information about the omniORB-list mailing list