Hi Alex,
I'm using KDevelop under SuSE 8.2 and it works fine. I only changed in the
KDevelop/Options/Kdevelop Settings the Compiler. Now I'm useing mpiCC for
C-Compiler and C++Compiler. (it a Wrapper around GCC - and you don't need
any Linkerfiles or other stuff).
For your MPI-Project only make a little C/C++ Project and include only
"mpi.h" - thats all - and it works absolutly fine.
I'm using LAM/MPI 7.0
cu
Bernd Klein
----------------------------------------------------------
LogicaCMG
Financial Services, GB 21
Faulenstraße 31-35
28195 Bremen
Phone : +49 421 30 96-121
Fax : +49 421 30 96-118
Email : bernhard.klein_at_[hidden]
----------------------------------------------------------
> -----Ursprüngliche Nachricht-----
> Von: Alex Krouglov [mailto:alexkrouglov_at_[hidden]]
> Gesendet: Freitag, 22. August 2003 18:30
> An: General LAM/MPI mailing list
> Betreff: RE: LAM: LAM/MPI and KDevelop
>
>
> Jeff,
>
> Before I added libraries for KDevelop, which came with Red Hat 7.2.
>
> KDevelop, which came with Red Hat 9, looks like have some
> bugs unmanageable
> for me. Possible I will have to go back to Red Hat 7.2 for development
> process.
>
> Which development tools do you use for LAM/MPI applications?
>
> Thanks.
>
> Alex Krouglov
>
>
> -----Original Message-----
> From: lam-bounces_at_[hidden]
> [mailto:lam-bounces_at_[hidden]]On Behalf
> Of Jeff Squyres
> Sent: Friday, August 22, 2003 10:53 AM
> To: General LAM/MPI mailing list
> Subject: Re: LAM: LAM/MPI and KDevelop
>
>
> I've been told off the list that KDevelop does not support per-project
> compiler specifications, and even overrides the environment
> variables for
> $CC and whatnot (even though it uses standard GNU autoconf,
> etc.). That
> seems somewhat strange to me (I don't know why they allow you
> to change it
> globally but not on a per-project basis), but I guess I see
> the following
> options for you:
>
> 1. Change the global compiler specification to mpicc/mpiCC/mpif77
> 2. Run "mpicc -showme foo.c" and note the output. These are the
> respective flags that are required for the compiler and linker. BE
> WARNED: these flags may change with any version of LAM and with any
> different configuration of LAM (e.g., if you have Myrinet support,
> you'll need -lgm, and so on)
>
> I don't know which is the lesser evil. :-)
>
>
> On Fri, 22 Aug 2003, Jeff Squyres wrote:
>
> > On Thu, 21 Aug 2003, Alex Krouglov wrote:
> >
> > > What do I need to put into KDevelop Compiler and Linker
> options to be
> > > able to program the LAM/MPI applications?
> > >
> > > If I use the native i386-linux-g++ compiler what
> libraries do I have to
> > > include? I don't see what place I can put the mpicc there.
> >
> > I don't think that you want to do that (put in the
> libraries manually);
> > they may change, depending on how your LAM is configured/installed.
> >
> > I'm not familiar with KDevelop, but I'd be greatly
> surprised if there
> > isn't a place to substitute in a different compiler
> somewhere (mpicc,
> > mpiCC/mpic++, or mpif77).
> >
> >
>
> --
> {+} Jeff Squyres
> {+} jsquyres_at_[hidden]
> {+} http://www.lam-mpi.org/
> _______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
>
> _______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
>
This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.
|
