Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ptp-user] Issue with synchronized Autotools project

On Monday, March 14, 2016 12:00:13 PM Dr. Markus Geimer wrote:
> Christoph, all,
> 
> >> To (hopefully only temporarily) work around this limitation,
> >> I was thinking of specifying something like
> >>
> >>    module purge && module load intel openmpi && configure
> >>
> >> as the configure command (likewise for autogen).
> 
> First of all, this hack does not work because Eclipse tries to be
> smart and starts quoting stuff.

Markus,

perhaps I was too sloppy in describing my work around. I am describing it
for cmake; it should go similar for autotools.

The key ingredient - other than PTP synchronized projects - is that
I disregard any genuine cmake (or autotools) support. I am rather
configuring my project as an ordinary Makefile project, but then
specify a wrapper shell around cmake and make as external make
command.

Then, for each (remote) build host, prior to each build, the build process
for PTP synchronized projects loads the required modules (including cmake)
and runs cmake/configure and build on the  (remote) build host.

The wrapper script is a bit more involved as just "cmake &&make", as it tries
to decide automatically, whether only make or cmake && make should be called.

It is clearly a work around, but it is doing precisely what I want. In 
particular, cmake is called on the (remote) build host whenever I want it to
be called --- not just once to create the Makefiles. 

> 
> > I am frequently using cmake with PTP. I guess this is a similar situation
> > as for configure/autotools.
> 
> Well, according to http://wiki.eclipse.org/PTP/new_and_noteworthy/8.0.0
> synchronized Autotools projects should be supported.  And in principle
> they are, i.e., configure options can be specified and are passed
> correctly, autogen.sh and configure are run automatically or can be
> triggered via the project context menu, etc.
> 
> The issue is that specified environment modules are only loaded before
> the *build*.  In my case, I need to use a specific version of Autotools,
> loaded via a module, and the configure script tries to identify the
> compiler and MPI, both also loaded via modules.  But unfortunately,
> the modules are not loaded by PTP before executing the autogen.sh and
> configure commands.
> 

As noted by Greg Watson in an earlier post, the way to go for official 
support is by filing a bug report. I will do that for the cmake side, as soon
as I have some free cycles for that.
-- 

Mit freundlichen Grüßen / Kind regards

Dr. Christoph Pospiech
High Performance & Parallel Computing
Phone: +49-351 86269826
Mobile: +49-171-765 5871
E-Mail: cpospiech@xxxxxxxxxx

Lenovo (Deutschland) GmbH
Meitnerstr. 9
D-70563 Stuttgart

Geschäftsführung: Bernhard Fauser
Sitz der Gesellschaft: Stuttgart
HRB-Nr.: 25189, AG Stuttgart
WEEE-Reg.-Nr.: DE79679404

Back to the top