Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] problem to configure to make helloworld program and helloworld module be compiled and added to the tartget with a local external source
Date: Tue, 19 Nov 2013 23:03:29 +0100	[thread overview]
Message-ID: <528BE031.5010100@mind.be> (raw)
In-Reply-To: <3258CDB0922447C482F9DCD445EEFB36@NKDELL>

On 19/11/13 15:01, Nils Koehler wrote:
>
>>> Hi,
>>>
>>> I have goggled a lot the last three days to find out how to implement a
>>> own program and device driver, which is compiled and added to the target
>>> due buildroot make command, but I did not had success to solve it.
>>>
>>> Actually my problems is that:
>>>
>>> HELLOWORLD_SOURCE_DIR = /home/koehler/Desktop/Kernel/ldt/
>>
>>    Where did you get this variable from? We don't use SOURCE_DIR.
>
> mhh... I think, I mixed up some things, I have no idea where I did found it.
> I have changed now to the right keywords thank you...
>
> But after...
> make helloworld-rebuild all
>
> It is compiling and I can see that the compiled code is updated and present
> in the directory /buildroot-2013.08/Build/helloworld-1.0/
> So far so fine, but it is missing in the /buildroot-2013.08/target/bin/
> directory.
>
> What may be the problem right now?
> This is my actual .mk file:
>
> HELLOWORLD_VERSION = 1.0
> HELLOWORLD_SITE = /home/koehler/Desktop/Kernel/helloworld-1.0/
> HELLOWORLD_SITE_METHOD = local
> HELLOWORLD_LICENSE = GPLv3+
> HELLOWORLD_INSTALL_TARGET = YES
>
> define HELLOWORLD_BUILD_CMDS
>      $(MAKE) CC="$(TARGET_CC)" LD="$(TARGET_LD)" -C $(@D) all
> endef
>
> define HELLOWORLD_INSTALL_TARGET_CMDS
>      $(INSTALL) -D -m 0755 $(@D)/helloworld $(TARGET_DIR)/bin
> endef
>
> define HELLOWORLD_DEVICES
>      /dev/ldt  c  666  0  0  42  0  -  -  -
> endef
>
> define HELLOWORLD_PERMISSIONS
>      /bin/helloworld  f  4755  0  0  -  -  -  -  -
> endef
>
>
> #$(eval $(generic-package))

  Do you really have this line commented out? Without it, there will be 
no helloworld package, so 'make helloworld-dirclean' would give an error...


  Regards,
  Arnout


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

      parent reply	other threads:[~2013-11-19 22:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-18 16:00 [Buildroot] problem to configure to make helloworld program and helloworld module be compiled and added to the tartget with a local external source Nils Koehler
2013-11-19  8:26 ` Arnout Vandecappelle
2013-11-19 14:01   ` Nils Koehler
2013-11-19 14:29     ` Thomas Petazzoni
2013-11-19 16:59       ` Nils Koehler
2013-11-19 17:05         ` Thomas Petazzoni
2013-11-19 17:56           ` Nils Koehler
2013-11-19 22:17         ` Arnout Vandecappelle
2013-11-19 22:30           ` Yann E. MORIN
2013-11-19 22:33             ` Arnout Vandecappelle
2013-11-20  8:32           ` Nils Koehler
2013-11-19 22:03     ` Arnout Vandecappelle [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=528BE031.5010100@mind.be \
    --to=arnout@mind.be \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox