Custom application cannot be compiled

[Ronny Nilsson]

Hi Manuel
You are correct, the tarfile should have the same name as the directory. In 
your case it would be /apps/python3/python3-3.5.0.tar.gz where
	PKG_VER = python3-3.5.0
	PKG_NAME = python3
By using a common scheme all Makefiles can share large parts (which are in the 
top Rules.mk as a lib).

I hope you get it to work. However, should you not I can reveal that there is 
help on the way. I've created a Raspbian compatibility layer which enables to 
pull in small pieces from Raspbian Wheezy and put it "on top" of Nard. It 
will act as a complement if one need something specific which is not yet 
available in Nard. I'm doing testing of it now and hope to release it in a 
few weeks. Python 2.7 is tested and works, haven't tried Python 3 yet though.

BR
/Ronny



---------------------------------------------------
> Hi,
>
> After struggling very much time, I found the error: the tar.* file
> containing the sources is required to contain the *complete* name of the
> application directory. I created a directory called "ptyhon3" and the tar.*
> file was called Python-3.5.0.tar.gz.
>
> What's actually the content of $(PKG_VER)?
>
> BR,
> Manuel
>
> -----Original Message-----
> From: nard-bounces at arbetsmyra.dyndns.org
> [mailto:nard-bounces at arbetsmyra.dyndns.org] On Behalf Of FAUX Manuel Sent:
> Mittwoch, 11. November 2015 16:57
> To: nard at arbetsmyra.dyndns.org
> Subject: Custom application cannot be compiled
>
> Hi,
>
> I'm trying to add a customized application to nard, but my Makefile always
> fails with "No rule to make taget Python-3.5.0", even I've defined the
> target as mentioned in the example on the nard webpage:
>
> .PHONY: all $(PKG_VER)
> all: $(PATH_FS)/usr/sbin/$(PKG_NAME)
> $(PKG_VER): $(PATH_FS)/usr/sbin/$(PKG_NAME)
>
>
> .PHONY: install
> install: $(PATH_FS)/usr/sbin/$(PKG_NAME)
> $(PATH_FS)/usr/sbin/$(PKG_NAME): $(PKG_VER)/.nard-build
>         install -m 0755 -d "$(dir $@)"
>         $(CP) -uavf "$(PKG_VER)/$(PKG_NAME)" "$@"
>
>
> $(PKG_VER)/.nard-build: $(std-deps)
>         cd $(dir $@) && ./configure CFLAGS="$(CROSS_CFLAGS)" \
>                 --prefix=/usr --host=$(CROSS_TUPLE)
>         $(MAKE) -C "$(PKG_VER)"
>         touch "$@"
>
> Without diving too deep into the Rules.mk provided by nard, I guess
> $(PKG_VER) is being set to the second part of PKGS_APPS after the slash; so
> I've set
> PKGS_APPS += python3/Python-3.5.0 and so there should be a rule for
> $(PKG_VER), which is some lines below...
>
> What am I missing?
>
>
> Thanks,
> Manuel