[omniORB] omniORB build enviroment

[Lars Immisch]

Dear Duncan,

[...]
> make veryclean is already there in theory. It just doesn't quite
> manage to clean everything...

Yes, and it doesn't work from the toplevel, because some directories don't  
understand the rule (I'm claiming this from memory).

> > For NT and autoconf, a fairly typical approach is to supply a
> > config.h.nt and a global.mk.nt or rather config.mk.nt and people on
> > Windows have to copy them to config.h and config.mk instead of
> > running configure.
>
> It would be nice to avoid this step, and have a "configure" which
> worked on all platforms, not just Unix. That's why I'm considering
> other things.

Well, you could have a configure.bat that just copied the two files.

> The last time this discussion came up, people mentioned that one of
> the things which encouraged them to port omniORB to exotic platforms
> was that it _doesn't_ use autoconf.

If autoconf was just used to generate a config.h and a config.mk, the new  
build system wouldn't be any harder for them than it is now - they'd have to  
write custom config.h and config.mk files.

[...]

> > > 3. A Python script which builds everything
>
> [...]
> > But you'd still need /bin/sort instead of sort.exe on Windows, wouldn't
> > you?
>
> No -- it's easy to implement a sort command in Python.

Of course it is - don't let me stop you doing that!

And you might be able to phase out omkdepend and maybe some other wrappers.

But I'll shut up now.

- Lars