The library project I am maintaining has various language bindings
generated by the Swig package. Each of the language bindings are
enabled by an Automake conditional. As there were various files being
generated no matter if a language binding was enabled or not, I've set
about trying to correct
* On 2012 19 Nov 11:37 -0600, Diego Elio Pettenò wrote:
> On 19/11/2012 08:55, Nate Bargmann wrote:
> > Is there a way to use the python_PYTHON primary but not distribute the
> > file(s) in its list?
>
> nodist_python_PYTHON should do the trick
Thanks, Diego.
That works jus
* On 2013 12 Feb 03:08 -0600, Vincent Torri wrote:
> in our project, we append _beta and _rc (or _rc1, _rc2 etc...) for
> beta and release candidate. It's sufficiently explicit. For example,
> 1.14.0_beta
I was advised by a Debian maintainer to use tilde '~' as the separator
as any text following
* On 2013 27 Feb 04:32 -0600, Stefano Lattarini wrote:
> It also stated:
>
> I also propose the following change to the branching scheme currently
> implemented in the Automake Git repository:
>
> * The 'maint' branch will be reserved to cut of the next micro
> release; so it will just
This is a long-standing bug in our project and I've yet to figure out
how to address it.
The project is primarily a library that once installed has a "front end"
installed in libdir and N "back ends" (linked by libtool with the
'-module' option and using libltdl for dlopen) installed in pkglibdir.
* On 2013 06 Apr 20:33 -0500, NightStrike wrote:
> Looks like the link path isn't set right for the test programs
I can agree with that. I chose to look at this again yesterday and
configured a work-around.
As the test programs are started with a generated shell script to pass
parameters, it w
Perhaps this is more of a GNU Make question than of Automake.
The prjoect I work with uses Swig and while there is no provision for
turning off all warnings, certain warnings can be quelled. While I can
add the needed option to the Makefile.am, I would like to place a
variable in that position th
* On 2013 08 Jun 07:59 -0500, Diego Elio Pettenò wrote:
> On 08/06/2013 12:58, Nate Bargmann wrote:
> >
> > As 'make V=1' can be used to override the silent rules created from
> > 'configure', is it possible to write the variable with the ability to b
* On 2013 08 Jun 09:48 -0500, Stefano Lattarini wrote:
> On 06/08/2013 02:58 PM, Diego Elio Pettenò wrote:
> > On 08/06/2013 12:58, Nate Bargmann wrote:
> >>
> >> As 'make V=1' can be used to override the silent rules created from
> >> 'configure&
* On 2013 15 Sep 13:18 -0500, Jules Colding wrote:
> So, how do I tell the top-level Makefile.am that it should traverse all
> sub-directories building only the libraries, and then traverse the
> sub-directories again building only the test applications?
Would it work to break the test program
Some advice I received from a Debian developer (packager) was that it
works better when upstream projects refrain from using the hyphen '-' in
their version string. The packaging software will consider "1.0-rc1" to
be more recent than "1.0" as the packaging system appends '-*' to the
end of the up
I am dealing with this in the Hamlib project. We are using the Autoconf
macro from the macro archive and by default it identifies Python2 which
is then passed to Swig to build the Python bindings. The same macro
also supports Python3 with a bit of care and a couple of extra steps
such as running
* On 2021 20 Jan 17:33 -0600, Bob Friesenhahn wrote:
> Autotools is in great danger of becoming irrelevant, at least for new
> software development. A lot of people feel hostile toward it.
This is quite true.
As a co-maintainer of a library project that uses Autoconf, Automake,
and Libtool, I've
13 matches
Mail list logo
