Hi Bruce > -----Original Message----- > From: Bruce Ashfield [mailto:[email protected]] > Sent: Freitag, 6. April 2018 15:48 > To: Bach, Pascal (BT CPS R&D ZG FW CCP) <[email protected]> > Cc: [email protected] > Subject: Re: [meta-virtualization] [PATCH 1/2] docker-proxy: add recipe for > docker-proxy > > On Fri, Apr 6, 2018 at 9:41 AM, Pascal Bach <[email protected]> > wrote: > > Before docker-proxy was built as part of the docker-recipe but there > > in some situations when built for x86_64 under x86_64 it incorrectly > > linked against host libraries. > > This puts it into a separate recipe that makes use the go.bbclass to > > build the binary properly. > > > > As I hinted, I'm going to figure out how to integrate / fix this in the main > docker recipe. > > Having the various SRCREVs managed in multiple recipes is a maintenance > pain and recipe for runtime errors. > > I'll dig into what the go class is doing that is so different from what I've > been > trying. > > Can you provide the output of your properly linked docker-proxy, so I can > use it as a reference ?
I'm not sure what you mean by output? Pascal BTW you can also ping me on IRC #yocto as bachp might be quicker to clarify -- _______________________________________________ meta-virtualization mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-virtualization
