[ace-users] Auto-generating dependencies in ACE Makefile usin g MINGW and MSYS

[ace-users] Auto-generating dependencies in ACE Makefile usin g MINGW and MSYS

Post by Townsend, » Sun, 04 Jul 2004 02:19:25


gt; Hi,

Great! I always wanted to be a guinea pig.


The problem is that we can't afford hardware for all the developers that need to
develop and test software. At least 95% of our software is not dependant on the
target system and we need to develop it on PCs. Unfortunately Linux is not an
option.

I have developed this way many times without ACE and it works fine. ACE itself
is built in this exact same manner. Flip a few options here or there and rebuild
on a new target. We are just trying to reuse the ACE make facilities instead of
starting from scratch.

Is there anyone who knows the makefiles well enough to point me to where the
'depend' target and .default target reside? I think the ACE makefiles is where
the problem lies. I can build and execute just fine. I just need to get make
depend working before the project gets too big.

TTFN,

Matthew Townsend






































































































































































 
 
 

[ace-users] Auto-generating dependencies in ACE Makefile usin g MINGW and MSYS

Post by Don Hinto » Sun, 04 Jul 2004 02:35:17

i Matthew:

On Fri, 2 Jul 2004, Townsend, Matthew wrote:


Which version are you using again?

thanks...
don












































































































































































































 
 
 

[ace-users] Auto-generating dependencies in ACE Makefile usin g MINGW and MSYS

Post by Townsend, » Wed, 07 Jul 2004 04:26:42

> Hi,
...


I've haven't played with Cygwin in years. I found MinGW and Msys to be much
easier to install and use. I'll have to try Cygwin again some time. Do you know
if it is tested better than the MinGW builds?

I've usually insisted on regular cross builds and testing when using a windows
target as the test build to prevent the Windows things from creeping in.
Although most of the development is done in windows, we usually assign someone
to integrate the product on the target routinely to double check that we aren't
getting ourselves in trouble.


Interesting. I have only briefly noted the change to MPC. I have never used it
before.

I did run a quick test on a CORBA test program I have. I've downloaded code for
the "Advanced CORBA Programming with C++" and manually (by copying a ACE
example) built a makefile for ACE for the Chapter 3 example. I also generated
the makefiles using the perl script mentioned above, but the corresponding make
fails. The test program contains an idl file that the MPC makefiles don't
contain rules for.

Using the hand built makefile, 'make depend' on a clean directory expands the
idl file first. The MPC makefiles ignore the idl file. Running make with the MPC
makefiles also fails as there is no rule to make the idl file.


TTFN,

Matthew A. Townsend
Government Communications Systems Division
XXXX@XXXXX.COM
321-729-7025