From: Scott Garman <scott.a.garman@intel.com>
To: "Yu, Ke" <ke.yu@intel.com>
Cc: "poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: [PATCH 1/1] screenshot: change the order of LDADD arguments
Date: Tue, 01 Mar 2011 22:56:49 -0800 [thread overview]
Message-ID: <4D6DEA31.1050008@intel.com> (raw)
In-Reply-To: <20110302011709.GE23315@kyu3-hedt>
On 03/01/2011 05:17 PM, Yu, Ke wrote:
> Interesting fix. Could you elaborate a bit more why changing the
> order of *.la and libs has the effect? it should be a good learning
> to me.
Hi Ke,
The order of linker arguments does matter when dependencies exist. In
this case, libshot.la depends on GTK_LIBS, so it needs to be listed first.
Scott
--
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center
next prev parent reply other threads:[~2011-03-02 6:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 21:27 [PATCH 0/1] screenshot bugfix Scott Garman
2011-03-01 21:27 ` [PATCH 1/1] screenshot: change the order of LDADD arguments Scott Garman
2011-03-02 1:17 ` Yu Ke
2011-03-02 6:56 ` Scott Garman [this message]
2011-03-03 19:11 ` [PATCH 0/1] screenshot bugfix Saul Wold
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=4D6DEA31.1050008@intel.com \
--to=scott.a.garman@intel.com \
--cc=ke.yu@intel.com \
--cc=poky@yoctoproject.org \
/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