Hello Kenton,

many thanks for the fast reply and check-in. - I will give it a try and get 
back to you.
Three things are really near to my heart:
        1.) Please abstract the usage of commands
                - mkdir -> $(MKDIR)
                - touch -> $(TOUCH)
                - make -> $(MAKE)
                - ...
        This is really necessary since e.g. Yocto brings it very own 
environment including native tools along. Actually every build system does.
        Using bare commands is like the 80's hackers did.
        We just committed a fix to U-Boot recently abstracting "python".
        There should then be a file defining the commands such as:
                MKDIR ?= mkdir -p
                TOUCH ?= touch
                MAKE ?= make
        This also gives you the opportunity to define certain parameters along 
w/ the command. Please note the question mark. This enables any other make 
environment to override the commands.

        Apart, capnproto has got two build systems. - Which one shall be 
actually used and why are there two of it?

        2.) The second thing I would like to address is that there should be 
branches for Yocto. E.g. "krogoth" and "morty". We have already the openjdk 
maintainer convinced that this makes definitely sense.

        3.) Third, will you push the recipes to [1]? - I might remove the hack 
w/ the "src" directory before.

Many thanks
Eric

Von: Kenton Varda [mailto:[email protected]] 
Gesendet: Freitag, 26. Mai 2017 20:04
An: Schwarz, Eric
Cc: [email protected]
Betreff: Re: [capnproto] build w/ yocto

Hi Eric,

I don't know why the behavior would differ on your system (maybe automake 
changed?), but I imagine this should fix it:

https://github.com/sandstorm-io/capnproto/commit/5f20b5cc1032df29d830409433c7d7a0c71266e5

Let me know if that helps.

-Kenton

On Fri, May 26, 2017 at 3:08 AM, Schwarz, Eric <[email protected]> wrote:
Hello,

w/ Yocto's krogoth branch everything works fine. With Yocto's morty branch the 
"src" directory in the "build" directory is missing and "capnp compile" 
complains about that. Just creating a "src" directory is enough. Then 
everything works fine.
What would be the proper solution to fix this? Is there a configure option 
available?
We use capnproto 0.6.0 release. Please find the Yocto recipes attached. - Maybe 
someone may post it on [1].

Cheers
Eric

[1]... https://layers.openembedded.org/layerindex/branch/master/layers/
________________________________
 [http://www.arri.com/media/sign/2017_wvs_sign.jpg] 
<http://www.arri.com/camera/alexa/cameras/camera_details/alexa-sxt-w/>

Get all the latest information from www.arri.com<http://www.arri.com/>, 
Facebook<https://www.facebook.com/TeamARRI>, 
Twitter<https://twitter.com/ARRIChannel>, Instagram<http://instagram.com/arri> 
and YouTube<http://www.youtube.com/user/ARRIChannel>.

Arnold & Richter Cine Technik GmbH & Co. Betriebs KG
Sitz: München - Registergericht: Amtsgericht München - Handelsregisternummer: 
HRA 57918
Persönlich haftender Gesellschafter: Arnold & Richter Cine Technik GmbH
Sitz: München - Registergericht: Amtsgericht München - Handelsregisternummer: 
HRB 54477
Geschäftsführer: Franz Kraus; Dr. Jörg Pohlman; Stephan Schenk; Walter 
Trauninger

--
You received this message because you are subscribed to the Google Groups 
"Cap'n Proto" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
Visit this group at https://groups.google.com/group/capnproto.

-- 
You received this message because you are subscribed to the Google Groups 
"Cap'n Proto" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
Visit this group at https://groups.google.com/group/capnproto.

Reply via email to