title: Why would Buildroot not provide make target for a project-specific host package added to the build per procedure?
body: <p>I've used Buildroot quite a bit over the years, and I've always managed to find solutions to the obstacles I've hit.  But this one has me going in circles.</p>
  
  <p>I've added a git-sourced python tool as a host package to my Buildroot build for an ARM target.  I have completed the work on the package/Config.in.host and the package/toolname/Config.in.host as well as package/toolname/toolname.mk files.  Everything looks to be in order.  I have compared the work with what the add_new_package.wizard outputs.</p>
  
  <p>The new option DOES appear in the menuconfig.</p>
  
  <p>It is NOT available as a make target, although I do have target-side packages I have included that ARE valid make targets.  i.e. I can run:
  <strong>make target-side-package-name</strong>
  and those packages are built just fine.</p>
  
  <p>I cannot run:
  <strong>make host-side-package-name</strong> as I get the error "No rule to make target".</p>
  
  <p>So there must be something I'm doing incorrectly with the host package, although I clearly am doing the right things with the target packages.</p>
  
  <p>Everything points to Buildroot simply ignoring my host package, other than sticking it into the menuconfig.  My hours of searching on the webs have led to not one single post about someone having this same problem.  I'm missing something obvious I would think.</p>
  
  <p>My question is - what debugging can I do, where can I look to find out what is keeping Buildroot from properly recognizing my new package?</p>
  
  <p>EDIT: I believe I understand now that part of the problem is the build order, and perhaps I can fix one issue with dependency directives.  My target package that relies on the host package was being built first.  I had assumed as common sense would dictate that host packages would be dealt with first, but that is apparently not true.</p>
  
  <p>EDIT:  Posting the .mk file  </p>
  
  <pre><code>TOOLNAME_VERSION = 2
  TOOLNAME_SITE =  $(call github,devname,toolname,$(TOOLNAME_VERSION))
  TOOLNAME_SETUP_TYPE = setuptools  
  TOOLNAME_LICENSE = GPL-3.0  
  TOOLNAME_LICENSE_FILES = LICENSE  
  
  HOST_TOOLNAME_DEPENDENCIES = host-python-library  
  
  $(eval $(host-python-package))  
  
  TOOLNAME = $(HOST_DIR)/usr/bin/toolname  
  </code></pre>
  
  <p>As I hinted before, it is now running just fine so I know it's mostly set up correctly, the remaining problem is the make target is missing.  Per the Buildroot manual, I should have one available.</p>
  
  <p>I have now discovered that the missing make target is in fact making it impossible to build other packages dependent upon this one.  The build of the dependent package now fails because "No rule to make" on the toolname package it is made to depend upon through 
      TARGET_PACKAGE_DEPENDENCIES = toolname</p>