[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gentoo-dev
Subject:    [gentoo-dev] Re: golang-build.eclass usage
From:       Dirkjan Ochtman <djc () gentoo ! org>
Date:       2015-07-26 14:55:28
Message-ID: CAKmKYaAgGd8m2hAXJg-jK=Sj-jT=sVMXh+eP3KiMxUwAU9CjGg () mail ! gmail ! com
[Download RAW message or body]

On Thu, Jul 23, 2015 at 12:14 AM, William Hubbs <williamh@gentoo.org> wrote:
> I broke the thread, because usage should be discussed in a different
> thread than working on the eclass itself.
>
> On Wed, Jul 22, 2015 at 10:17:19PM +0200, Dirkjan Ochtman wrote:
>> On Wed, Jul 22, 2015 at 7:36 PM, William Hubbs <williamh@gentoo.org> wrote:
>> > Let me know what you think.
>>
>> I tried to use your eclass recently, but it failed with this error:
>>
>>  * Call stack:
>>  *            ebuild.sh, line 765:  Called __ebuild_main 'compile'
>>  *   phase-functions.sh, line 968:  Called __dyn_compile
>>  *   phase-functions.sh, line 447:  Called die
>>  * The specific snippet of code:
>>  *           die "The source directory '${S}' doesn't exist"
>>
>> Do you have any minimal examples of how to use the eclass? I've been
>> experimenting with a syncthing package, but that's a bit different
>> from the go-text or go-crypto packages you've converted so far.
>
> How is it different, does it have its own build system, or do you just
> use the go commands to build it?

It just uses the go commands, plus a sprinkling of godep:

https://github.com/djc/djc-overlay/blob/master/net-p2p/syncthing/syncthing-0.11.6.ebuild

I'd think that that was standard enough that it'd just work with your
golang eclass.

> The updates I'm working on are going to make more of the variables the
> eclass uses visible to ebuilds so they can inherit it and override the
> phase functions if the packages have their own build systems.

[prev in list] [next in list] [prev in thread] [next in thread]