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/
|
