[omniORB] make files -- a suggestion

[Mikhail Soukhanov]

Hello!

As I am trying to make omniORB make on some other platform that is not
officially supported (BCB for that thing), I found it very hard to
remember which make (dir.mk) files were modified in the process without
grep'ing them or going into my CVS. So, I ended with a scheme which I
would like to suggest to others, especially omniORB maintainers.

What about adding in all dir.mk files the following lines, somewhere
between make variables and rules common to all platforms:

> #############################################################################
> #    Make variables and rules specific for a given platform, if any         #
> #############################################################################
> ifneq ($(wildcard $(platform).dir.mk),)
> include $(platform).dir.mk
> endif

Then, one can simply define a new platform in $(TOP)/config/config.mk
file (in my case, I used platform=x86_win95_bcc32) and then place all
the platform-specific stuff in the (e.g.) x86_win95_bcc32.dir.mk file.

This will also clear up make files somewhat, because they are such a
mess now (I think).

The same can be applied to $(TOP)/include/omniORB2/CORBA_sysdep.h by
inserting certain include statements at its top, e.g.:

  #ifndef __CORBA_SYSDEP_H__
  #define __CORBA_SYSDEP_H__

> #ifdef __BCPLUSPLUS__
> #include <omniORB2/CORBA_sysdep_bcc32.h>
> #endif

Also, can some in-depth information on omniORB's make file structure (is
it called Development Environment?) be found somewhere?

Any comments will be appreciated.

Best regards,
		Mikhail
-- 
Mikhail Soukhanov <mailto:mik@astra.relline.ru.>

Laboratory of Geoinformatics, VNIIgeosystem
Warszawskoje chaussee 8, Moscow M-105, 113105 Russia
Tel.: +7(095) 954-00-31, fax.: +7(095) 958-35-22
W.W.W.: <http://astra.relline.ru./>