Hello Glenn,
* Schrader, Glenn wrote on Thu, Jun 12, 2008 at 07:54:59PM CEST:
>
> I am creating a library that is built with automake. The way that I
> >think< this should work is:
> The problem I'm having is that the programs installcheck uses to test
> the library can only be build after the '
Hello,
I've little to add to Brian's detailed reply, except that ...
* Mar Loh wrote on Thu, Jun 12, 2008 at 06:07:23PM CEST:
> +topdir
> --+libsrcdir
> --+libsrcsubdir1
> --+libsrcsubdir2
there is no need to have configure scripts in each of those directories.
Just have one at the top,
Hello,
* Deborah Nicholson via RT wrote on Wed, Jun 11, 2008 at 11:36:38PM CEST:
> I maintain the directory, but not the projects. I'm cc'ing the official
> Automake email address so they can incorporate your patch.
Thank you.
> > [EMAIL PROTECTED] - Mon Jun 09 23:52:05 2008]:
> >
> > I tired
Hello,
* Kamaljit Singh wrote on Fri, Jun 13, 2008 at 12:17:12AM CEST:
> I maintain my build tree separate to src tree which has all the
> Makefile.am's. Is it possible that all generated files (including
> the Makefile.in's and the various cache) be in the build tree ?
No, sorry. The Mak
Hi,
I maintain my build tree separate to src tree which has all the Makefile.am's.
Is it possible that all generated files (including the Makefile.in's and the
various cache) be in the build tree ?
kamaljit
Mar Loh wrote:
> Q1: Every time I run ./configure from the topdir, the system checks
> (checking for BSD-compatible) are re-run every time it gets to a new
> subdirectory, making the configure take a long time. How do I remove these
> checks when going to a new subdirectory (these are clearly
I am creating a library that is built with automake. The way that I
>think< this should work is:
Build the library with the command: make
Check the build with the command: make check
Install the library to the prefix:make install
Check the installation with the command: mak
My apologies for the novice nature of my question, but I'm quite unfamiliar
with autotools, and I'm failing a bit at filling the gap in documentation
between "hello world" and the full gnu manuals.
I'm trying to get an autobuild system working for a fairly large codebase,
and the recursion and tar
Hi,
I maintain the directory, but not the projects. I'm cc'ing the official
Automake email address so they can incorporate your patch.
You may also want to try contacting the project through its homepage,
http://sources.redhat.com/automake/
Cheers,
Deborah
> [EMAIL PROTECTED] - Mon Jun 09 23:
failures still occur when i put all the .cpp in EXTRA_DIST, it still does not
include all my files.
so i followed your suggestion, putting them into ..._SOURCES. this will
expose unnecessary things, but it does not hurt.
Ralf Wildenhues wrote:
>
> * A117 wrote on Wed, Jun 11, 2008 at 08:15:13AM
* A117 wrote on Wed, Jun 11, 2008 at 08:15:13AM CEST:
> problem is, stdafx.* and targetver.* etc. should not go into this library,
> since they are to be used by VC project only.
> I guess they have to go to EXTRA_DIST.
Yes you can put them in EXTRA_DIST (which will do nothing except put
them in t
11 matches
Mail list logo