Ralf Wildenhues wrote:
You make the other libraries into `convenience archives'. These are
documented in both
*snip*
Oh, I've overlooked that.. Actually I though that the way objects are
packed into particular library is defined in the target library rules
and not in dependent ones.
Ye
Hi,
* netman (sent by Nabble.com) wrote on Tue, Dec 06, 2005 at 05:42:57PM CET:
>
> I wanted to use automake so I started with autoheader and every thing was ok
> until I used
>
> automake that I saw this error:
>
> ./compile is needed
Try
automake --add-missing
and it will install the `c
Hi Daniel,
* Daniel Kraft wrote on Tue, Dec 06, 2005 at 05:12:38PM CET:
>
> I'm new at developing with the GNU build system (automake), and now I've tried
> to "port" an existing project to use an automake-based build system;
> therefore I
> read some tutorials I found on the WWW, and I also loo
Bruce Korb <[EMAIL PROTECTED]> writes:
> Ed Hartnett wrote:
>> Howdy all!
>> I am using automake to build my library, and I have a slew of test
>> programs:
>> # These programs are all built for make check in this directory.
>> check_PROGRAMS = tst_h_files tst_h_atts tst_h_vars tst_h_grps
Ed Hartnett wrote:
Howdy all!
I am using automake to build my library, and I have a slew of test
programs:
# These programs are all built for make check in this directory.
check_PROGRAMS = tst_h_files tst_h_atts tst_h_vars tst_h_grps \
tst_h_compounds tst_h_wrt_cmp tst_h_rd_cmp tst_h_
Hi
I wanted to use automake so I started with autoheader and every thing was ok
until I used
automake that I saw this error:
./compile is needed
but I didn't see any thing about ./compile in the doc of using automake.
I read in doc that automake needs automake.am
so would you please guide
Howdy all!
I am using automake to build my library, and I have a slew of test
programs:
# These programs are all built for make check in this directory.
check_PROGRAMS = tst_h_files tst_h_atts tst_h_vars tst_h_grps \
tst_h_compounds tst_h_wrt_cmp tst_h_rd_cmp tst_h_vl tst_h_opaques
Hi!
I'm new at developing with the GNU build system (automake), and now I've tried
to "port" an existing project to use an automake-based build system; therefore I
read some tutorials I found on the WWW, and I also looked at Makefile.am's for
existing projects.
My problem is that my project conta
Ralf Wildenhues wrote:
> > Yes. I think only the strong names of dependencies are hardcoded into
> > .dlls and .exes, not the paths where to find them.
>
> So people rely on installed paths being default-findable by the engine?
Yes. People install all libraries into $prefix/lib.
> Hmm. This soun
