From: "Jürgen Beisert" <jbe@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Pat Murray <PMurray@data-display.com>
Subject: Re: [ptxdist] additional c file in a src-autoconf-proglib package
Date: Mon, 11 Nov 2013 14:05:08 +0100 [thread overview]
Message-ID: <201311111405.08130.jbe@pengutronix.de> (raw)
In-Reply-To: <4ECD7F7A0B03E64BA50DA3C6FC2464FD075B0FA4@KRUSTY.ddisplay.com>
Hi Pat,
On Monday 11 November 2013 13:32:12 Pat Murray wrote:
> I created a package using "ptxdist test src-autoconf-proglib" , this
> allowed me to create a shared library libtest.so and a binary test. That's
> all ok, it created two files libtest.c and test.c and I build it
> successfully.
>
> I then wanted to add another file uart.c , so that it would be built &
> linked with the Binary "test".
>
> I tried the following changes to Makefile.am (highlighted in green), but it
> fails to build.
>
> #
> # library
> #
> Libtest_la_SOURCES = \
> libtest.c
>
>
> #
> # binary
> #
> test_SOURCES = \
> test.c uart.c \
This is the correct way. Just by adding more *.c files to this symbol. After
the last source file name you must not add a trailing '\'.
> How can a ptxdist package using src-autoconf-proglib have two .c files for
> the Binary ( not the shared library .so)
How does it fail? Can you show us the error messages?
Regards,
Juergen
--
Pengutronix e.K. | Juergen Beisert |
Linux Solutions for Science and Industry | http://www.pengutronix.de/ |
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2013-11-11 13:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 12:32 Pat Murray
2013-11-11 13:05 ` Jürgen Beisert [this message]
[not found] ` <4ECD7F7A0B03E64BA50DA3C6FC2464FD075B1FC4@KRUSTY.ddisplay.com>
2013-11-11 15:35 ` Jürgen Beisert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201311111405.08130.jbe@pengutronix.de \
--to=jbe@pengutronix.de \
--cc=PMurray@data-display.com \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox