Hello,
I am working at embedding libltdl inside our project (hwloc, an Open MPI
subprojet). Our plugins are not expected to be enabled in the most
common cases. So I am trying to see if the libltdl sub-configure could
be skipped entirely unless really needed (when plugins are enabled, and
libltdl
On Wed, 22 Aug 2012, Brice Goglin wrote:
Hello,
I am working at embedding libltdl inside our project (hwloc, an Open MPI
subprojet). Our plugins are not expected to be enabled in the most
common cases. So I am trying to see if the libltdl sub-configure could
be skipped entirely unless really
On 2012-08-22 15:12 +0200, Brice Goglin wrote:
I am working at embedding libltdl inside our project (hwloc, an Open MPI
subprojet). Our plugins are not expected to be enabled in the most
common cases. So I am trying to see if the libltdl sub-configure could
be skipped entirely unless really
Le 22/08/2012 16:32, Nick Bowler a écrit :
On 2012-08-22 15:12 +0200, Brice Goglin wrote:
I am working at embedding libltdl inside our project (hwloc, an Open MPI
subprojet). Our plugins are not expected to be enabled in the most
common cases. So I am trying to see if the libltdl sub-configure
On 2012-08-22 20:26 +0200, Brice Goglin wrote:
Le 22/08/2012 19:44, Nick Bowler a écrit :
On 2012-08-22 18:32 +0200, Brice Goglin wrote:
Le 22/08/2012 16:32, Nick Bowler a écrit :
[...]
Other than adding -I$(top_builddir) to CPPFLAGS, as a workaround you
could probably add something like
Le 22/08/2012 21:05, Nick Bowler a écrit :
[...]
Indeed, it looks like LT_CONFIG_H is set using AC_CONFIG_COMMANDS_PRE,
so it does in fact get set inside AC_OUTPUT. I guess you could write
AC_CONFIG_COMMANDS_PRE([LT_CONFIG_H=`expr $LT_CONFIG_H : '.*/\(.*\)'`])
and hope that it runs after
