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
--
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.
