[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop
Subject:    [Fwd: ACE/TAO with KDevelop?]
From:       Ralf Nolden <Ralf.Nolden () post ! rwth-aachen ! de>
Date:       2000-04-03 22:23:45
[Download RAW message or body]

Could someone answer this mail ?  I could do it but I=B4m really short on=

time this week and I guess he wants an answer within days.
Volunteers ?

;-)

Ralf

PS: send answers via private email, his question was on a kde newsgroup
and he obviously isn=B4t subscribed to kdevelop@ mailinglists

Donald Dade wrote:
> =

> >Hi Don,
> >
> >could you contact us about the issue and what=B4s the problem ? ( I do=
n=B4t
> >know what ACE and TAO are ;-)
> >
> >Ralf
> =

> Hi Ralf, thank you for getting back to me, and so quickly too :).
> =

> Well, ACE is the Adaptive Communication Environment, which is a highly
> portable framework for socket programming. TAO is a CORBA implementatio=
n
> written using ACE, and so is itself highly portable. It is quickly beco=
ming
> the implementation of choice for Linux because it is under the GNU lice=
nse,
> and it is extremely well designed and implemented.
> =

> The problem that I am having is that while I do not understand KDevelop=
's
> project directory structure, nor how KDevelop manages the Makefile.am,
> Makefile.in, and Makefile files.
> =

> What I would like to do is the following: My project is called kde_cm. =
So I
> have directories called ./kde_cm, ./kde_cm/kde_cm, and ./kde_cm/po. I w=
ould
> like to have another directory ./kde_cm/tao that holds my custom makefi=
le
> which knows how to build my CORBA server object. The CORBA server objec=
t
> will produce an object file that will have to be linked by the main KDE=
 app
> in the ./kde_cm/kde_cm directory, and it requires 2 shared libraries,
> libtao.so and liborbsvcs.so, so the main app will have to link those as=

> well. Any source file in the main app that references the CORBA server
> object has a whole slew of include files, compile flags, and link flags=
 that
> it needs.
> =

> I suppose that I can change the Makefiles to force them to work, but
> KDevelop can and will overwrite my changes the next time the Makefile i=
s
> generated. So my problem is that I do not know how to tell KDevelop to
> incorporate my customizations into any Makefiles that it generates. Whi=
le I
> understand the value of automake, autoconf, and configure, does this re=
quire
> that we sacrifice the ability to exercise precise control over the buil=
d
> process?
> =

> I greatly appreciate your help, and the work of the KDevelop team,
> =

> Don Dade
> ddade@digitalstatecraft.com

-- =

**********************************
Ralf Nolden

Ardennenstr. 41 =

52355 D=FCren

Tel. 02421/502758

The KDevelop Project
http://www.kdevelop.org

Email: rnolden@kdevelop.de
**********************************

[prev in list] [next in list] [prev in thread] [next in thread]