Hello Kenton, I tried "5f20b5cc1032df29d830409433c7d7a0c71266e5" and "bd15dd218910d48df13209546e3767a9daa8e8da" on top and now it works w/ Yocto's morty branch. Thanks! Please find the adapted Yocto recipes attached for documentation reason. May it help the one or the other out there.
> Yocto provides a custom mkdir? Why?
Well, I am not sure about "mkdir" but about "make" and "python" (if dependency
is set) and so on ...
$ bitbake -c devshell capnproto
$ which <command>
Yocto tries to be as much independent from the host Linux distribution as
possible.
>> Using bare commands is like the 80's hackers did.
> This ad hominem insult isn't helpful.
To make it more political correct, I refer here to the "software crisis" [2].
> Sorry, I don't understand what you're asking for here.
Well, there exist different branches for Yocto which bring along different
versions of tools needed to build the stuff e.g. autotools. Obviously the
versions are not compatible as it is in the case of e.g. LaTeX (always the same
behaviour for existing features). Thus, the build behaviour changes and there
might be patches necessary which may exclude each other for different branches.
Thus, having a "krogoth" and "morty" branch for the 0.6.0 release where just
those build fixes and nothing else gets pushed on top would make life a lot
easier. Only if things build smoothly and are easy to integrate people will use
it.
> I'm happy with my solution, thanks.
Just right after sending my response I saw that you had already pushed a patch
"bd15dd218910d48df13209546e3767a9daa8e8da" on top. Thanks ;)
> No, I don't plan to do this. You are welcome to do it, if you'd like.
Okay, I will do.
Cheers
Eric
[2]... https://en.wikipedia.org/wiki/Software_crisis
Von: Kenton Varda [mailto:[email protected]]
Gesendet: Freitag, 26. Mai 2017 21:01
An: Schwarz, Eric
Cc: [email protected]
Betreff: Re: [capnproto] build w/ yocto
Hi Eric,
On Fri, May 26, 2017 at 11:37 AM, Schwarz, Eric <[email protected]> wrote:
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.
Yocto provides a custom mkdir? Why?
Using bare commands is like the 80's hackers did.
This ad hominem insult isn't helpful.
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.
Defining MKDIR to "mkdir -p" would be wrong as -p changes the behavior.
It looks like automake already provides a MKDIR_P binding, so I guess I'll use
that.
https://github.com/sandstorm-io/capnproto/commit/bd15dd218910d48df13209546e3767a9daa8e8da
Apart, capnproto has got two build systems. - Which one shall be
actually used and why are there two of it?
You can use either. The automake build is canonical but a lot of developers
prefer cmake, especially when integrating Cap'n Proto into a cmake project.
cmake also supports Visual Studio.
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.
Sorry, I don't understand what you're asking for here.
3.) Third, will you push the recipes to [1]? - I might remove the hack
w/ the "src" directory before.
No, I don't plan to do this. You are welcome to do it, if you'd like.
On Fri, May 26, 2017 at 11:48 AM, Schwarz, Eric <[email protected]> wrote:
the more elegant way would be:
DEPS_DIRS := src
$(DEPS_DIRS):
$(MKDIR) $@
test_capnpc_middleman: $(test_capnpc_inputs) | $(DEPS_DIRS)
test_capnpc_middleman: capnp$(EXEEXT) capnpc-c++$(EXEEXT)
$(test_capnpc_inputs) | $(DEPS_DIRS)
I'm happy with my solution, thanks.
-Kenton
________________________________
[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.
capnproto_0.6.0.bb
Description: capnproto_0.6.0.bb
capnproto-native_0.6.0.bb
Description: capnproto-native_0.6.0.bb
