All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wayne Witzke <wwitzke@asgrp.com>
To: yocto@yoctoproject.org
Subject: How and where does yocto find lighttpd-module-fastcgi?
Date: Thu, 8 Mar 2018 16:52:49 -0500	[thread overview]
Message-ID: <423f0425-653d-37ab-098d-088466ef280d@asgrp.com> (raw)

Hello everyone,

I'm very new to Yocto, and I'm currently building an embedded system 
with a web interface. As I worked through the process of creating a 
Yocto configuration and layer to configure the specific build I needed 
(based on core-image-minimal), I discovered that I could add packages to 
my image by adding it to the configuration file via 
CORE_EXTRA_IMAGES_INSTALL. In this way, I was able to add lighttpd, php, 
php-cgi, and lighttpd-module-fastcgi to my build. It worked great!

However, now I am attempting to determine if mod_openssl is installed on 
my server, and using "CORE_EXTRA_IMAGES_INSTALL += 
'lighttpd-module-openssl'" to simply add it does NOT magically work like 
it did with lighttpd-module-fastcgi. My original guess was that adding 
"CORE_EXTRA_IMAGES_INSTALL += 'lighttpd-module-fastcgi'" caused a 
configuration option to be matched in the lighttpd.bb file so that the 
appropriate build option was used when building lighttpd. However, 
fastcgi doesn't actually show up in that file at all, and openssl does, 
so that clearly isn't the option . . . furthermore, mod_fastcgi doesn't 
appear in *any* of the layers I'm using to build, except in the 
lighttpd.conf portion of the recipe-extended/lighttpd directory structure.

So, my question is, how does bitbake know what to do when I add 
lighttpd-module-fastcgi, and where in the world does it find the source 
for mod_fastcgi?

Thank you in advance for your help :)

Wayne


             reply	other threads:[~2018-03-08 22:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-08 21:52 Wayne Witzke [this message]
2018-03-08 23:13 ` How and where does yocto find lighttpd-module-fastcgi? Andre McCurdy
2018-03-09 14:18   ` Wayne Witzke
2018-03-09 22:35     ` Andre McCurdy
2018-03-11  1:52       ` Wayne Witzke

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=423f0425-653d-37ab-098d-088466ef280d@asgrp.com \
    --to=wwitzke@asgrp.com \
    --cc=yocto@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.