From: "Mark Gollahon" <golly@stellarwerx.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: QA issues with pkgconfig files
Date: Thu, 22 Feb 2007 12:06:34 -0500 (EST) [thread overview]
Message-ID: <1172163994.7729@gatekeeper.stellarwerx.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1112 bytes --]
Koen:
If it is the "correct" way of doing things and not a "hack" just to make things work, then do it. All of the other options you proposed did seem "hack-ish" to me - but I don't know the intricacies of bitbake/OE.
Regards,
-Mark Gollahon
Koen Kooi wrote ..
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Koen Kooi schreef:
> > Koen Kooi schreef:
> >
> >> Possible solutions:
> >
> >> 1) set PKG_CONFIG_PATH to ${STAGING_LIBDIR}/pkgconfig
> >> +easy fix
> >> -requires to re-run do_pupulate_staging for all packages
> >
> > This seems to fix it in a clean way. Any objections to this going in
> today?
>
> Speak now or be silent forever....
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Darwin)
>
> iD8DBQFF3bM0MkyGM64RGpERAj+6AKCMDxx8a7wKvUTT90kr84En2R4HXQCgqfkX
> YnxlmEKeyQBQ8stwIVw/YHs=
> =ZvIf
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
next reply other threads:[~2007-02-22 17:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-22 17:06 Mark Gollahon [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-02-21 22:27 QA issues with pkgconfig files Koen Kooi
2007-02-21 22:42 ` Koen Kooi
2007-02-22 7:43 ` Paul Sokolovsky
2007-02-22 7:47 ` Koen Kooi
2007-02-22 8:41 ` Koen Kooi
2007-02-22 11:24 ` Koen Kooi
2007-02-22 15:13 ` Koen Kooi
2007-02-22 15:37 ` Holger Freyther
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=1172163994.7729@gatekeeper.stellarwerx.com \
--to=golly@stellarwerx.com \
--cc=openembedded-devel@lists.openembedded.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