All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ryan Wilkins <ryan@deadfrog.net>
To: buildroot@busybox.net
Subject: [Buildroot] Problem compiling local code
Date: Mon, 22 Jul 2013 16:38:39 -0400	[thread overview]
Message-ID: <6A282818-6448-427C-A748-B4FFC1934E7D@deadfrog.net> (raw)
In-Reply-To: <79A67ED1-220E-4FA4-BD5B-01A70D079C06@deadfrog.net>



On Jul 22, 2013, at 4:14 PM, Ryan Wilkins <ryan@deadfrog.net> wrote:

> 
> 
> On Jul 19, 2013, at 1:29 AM, Thomas De Schampheleire <patrickdepinguin+buildroot@gmail.com> wrote:
> 
>> Hi Ryan,
>> 
>> Is there any output regarding the hello package, like 'downloading',
>> 'extracting', 'building', etc. or nothing at all?
>> What is the name of the config option that you added, and are you sure
>> it's enabled in .config?
>> 
>> What happens if you explicitly run 'make hello' ?
>> 
>> Depending on what you did before, you may also need to clear previous
>> attempts from the output, for example with:
>> make hello-dirclean
>> 
>> If the hello package is seen correctly by buildroot, but the
>> compilation doesn't work correctly, you may want to add
>> KBUILD_VERBOSE=1 to the make command, to see the actual make command
>> executed.
>> 
>> Best regards,
>> Thomas
> 
> Thomas,
> 
> Thanks for the response.  After some digging around, I found that buildroot wasn't even trying to grab or compile my code.  What I discovered earlier today is that the variable names that I was using contained too many underscores.  My Config.in and hello.mk files were using variables set as BR2_PACKAGE_COMPANY_PROJECT_HELLO.  When I shortened it to just BR2_PACKAGE_HELLO then it started working properly.  Apparently the additional underscores confused some parsing of the buildroot and/or Kbuild system.  If that was mentioned in the documentation then I missed it.  Maybe it was assumed.  In any case, it's working now.
> 
> Thanks for your help on this.  I appreciate it.
> 

And I put the wrong variable names down in this email.  Was going from memory while my wife was driving the car. 

Config.in had BR2_PACKAGE_COMPANY_PROJECT_HELLO which changed to BR2_PACKAGE_HELLO.

hello.mk had COMPANY_PROJECT_HELLO_ variable names prefix which changed to HELLO_.

That solved the issues.

Best,
Ryan Wilkins

  reply	other threads:[~2013-07-22 20:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-19  4:11 [Buildroot] Problem compiling local code Ryan Wilkins
2013-07-19  5:29 ` Thomas De Schampheleire
2013-07-22 20:14   ` Ryan Wilkins
2013-07-22 20:38     ` Ryan Wilkins [this message]
2013-07-23  7:19       ` Thomas De Schampheleire
2013-07-23  7:27         ` Samuel Martin
2013-07-23 13:07           ` Thomas De Schampheleire
2013-07-23 20:43           ` Ryan Wilkins

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=6A282818-6448-427C-A748-B4FFC1934E7D@deadfrog.net \
    --to=ryan@deadfrog.net \
    --cc=buildroot@busybox.net \
    /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.