Manuel.FAUX at frequentis.com
Fri Nov 13 15:53:31 CET 2015
The example you've mentioned actually deals with run-time dependencies. I'm
looking for something like build-dependencies. How can I best refer to a different
app within an app's Makefile? I think calling "$(dir $@)../../Python/Python/python_host"
is not really elegant... ;)
Also I would need to force, that Python gets built before my app...
From: nard-bounces at arbetsmyra.dyndns.org [mailto:nard-bounces at arbetsmyra.dyndns.org] On Behalf Of Ronny Nilsson
Sent: Freitag, 13. November 2015 13:39
To: Nard SDK mailing list
Subject: Re: Build Dependencies
This can be done in the product recipe. Read the comments in
There you can find an example.
> Would would be the correct way to use build dependencies in Makefiles
> of apps?
> In my case I want to build a Python module, which obviously requires a
> Python interpreter to be compiled. So in my Makefile at some point I need
> to call "$(HOST_PYTHON) setup.py", where HOST_PYTHON would be a
> reference to the Python interpreter in the same version as the nard
> Python/Python-3.5.0 app (but compiled for the compiling system
> architecture, not for ARM). This Python interpreter actually was compiled
> by the python app (since building Python also requires a Python binary).
> What's the best way to refer to that (already compiled) Python binaray?
More information about the Nard