[FS#1427] SDK doesn't add a directory to PATH (compiling po2lmo binary with SDK)

[LEDE Bugs]

A new Flyspray task has been opened.  Details are below. 

User who did this - Stan (stangri) 

Attached to Project - OpenWrt/LEDE Project
Summary - SDK doesn't add a directory to PATH (compiling po2lmo binary with SDK)
Task Type - Bug Report
Category - Toolchain
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Low
Priority - Very Low
Reported Version - lede-17.01
Due in Version - Undecided
Due Date - Undecided
Details - This is a reminder to @neoraider:

After:
./scripts/feeds install luci-base
make package/luci-base/host/compile

the po2lmo binary is available (in my case) at ./staging_dir/target-arm_cortex-a9+vfpv3_musl-1.1.16_eabi/host/bin/po2lmo. Looks like it's being used by the SDK just fine, but according to @neoraider: "it seems the SDK only adds staging_dir/host/bin to the PATH".  

I'll quote the full exchange:

07:06 neoraider: stangri: in a normal OpenWrt build from source, po2lmo is installed to staging_dir/hostpkg/bin/po2lmo (on master) or staging_dir/target-*/host/bin (lede-17.01); it seems the SDK only adds staging_dir/host/bin to the PATH
07:06 neoraider: stangri: were you able to build package/luci-base/host/compile using the SDK?
07:07 neoraider: stangri: and if you were, did it install the binary to one of the directories I listed?
07:07 stangri: neoraider: yes I was. also could get the binary made by: cd feeds/luci/modules/luci-base/src; make po2lmo
07:07 stangri: neoraider: yes, I was confused by the long-ass target directory: ./staging_dir/target-arm_cortex-a9+vfpv3_musl-1.1.16_eabi/host/bin/po2lmo
07:08 neoraider: stangri: Okay, in that case the SDK is not setting PATH correctly
07:08 neoraider: stangri: Can you file a ticket, so I don't forget about it?
07:08 stangri: neoraider: I will, not sure if it's not the user error tho.
07:22 stangri: neoraider: looks like the po2lmo in the target directory is being used just fine. do you want me to still file a ticket in flyspray? I can't see how can I assign it to you directly.


More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1427