Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Added package v86d which provides a real-mode helper for uvesafb driver.
Date: Sat, 12 May 2012 16:30:52 +0200	[thread overview]
Message-ID: <4FAE741C.7090104@mind.be> (raw)
In-Reply-To: <CADiAo4KofjL+kb8RLbWRwHauYpgqtWefLi_4QwV50sMgf-M+VA@mail.gmail.com>

On 05/12/12 07:01, Dmitry Golubovsky wrote:
> Arnout,
>
> On Fri, May 11, 2012 at 6:39 PM, Arnout Vandecappelle<arnout@mind.be>  wrote:
[snip]
>>   When you use GENTARGETS, you must also specify the install commands.
>
> And if I don't then standard "cd $(@D); make install" or anything
> similar will be used? Somehow it works without explicit install
> command specification.

  No, with GENTARGETS the install commands are empty by default.  Or you sure
it's not the old binary from a previous compilation that you see in your
target dir?

  I tried it with a clean build and there's no v86d or testvbe in the target
dir.


>> However, you can probably keep using AUTOTARGETS.  Even when you use
>> AUTOTARGETS, it is possible to override the CONFIGURE_CMDS and BUILD_CMDS.
>
> Due to the way v86d configure is written GENTARGETS seems to be more
> proper - I got convinced.

  The non-existent MAKETARGETS would be even better :-)


>> But you don't even need to override the BUILD_CMDS.  Instead, you can
>> pass additional options to the MAKE call, by defining
>>
>> V86D_MAKE_OPT += CC="$(TARGET_CC) -D__i386__"
>
> What I have in the patch I provided, was tested build-wise on i386 and
> x86-64 targets (but the program itself was only tested in 32bit mode).
> I tried that Thomas suggested (redefine CFLAGS), it did not work. I
> don't see much sense in changing the working command from what is in
> my patch.

  Sure, it's OK as it is (except for the install target of course).
Merely pointing out an alternative.

  Regards,
  Arnout

-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
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

  reply	other threads:[~2012-05-12 14:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-09 10:41 [Buildroot] [PATCH] Added package v86d which provides a real-mode helper for uvesafb driver Dmitry
2012-05-11 22:39 ` Arnout Vandecappelle
2012-05-12  5:01   ` Dmitry Golubovsky
2012-05-12 14:30     ` Arnout Vandecappelle [this message]
     [not found]       ` <CADiAo4KYq_xVcstt8LTK5PtgdyVHfLguqq9Jfpi13aSC7FnATg@mail.gmail.com>
2012-05-14  3:54         ` [Buildroot] Fwd: " Dmitry Golubovsky
  -- strict thread matches above, loose matches on Subject: below --
2012-07-18 21:17 [Buildroot] " Dmitry
2012-07-17  3:17 Dmitry
2012-07-17  8:01 ` Thomas Petazzoni
2012-07-17  9:38   ` Dmitry Golubovsky
2012-05-14  3:50 Dmitry
2012-05-09 10:32 Dmitry
2012-05-09 10:35 ` Baruch Siach
2012-05-09  1:19 Dmitry
2012-05-09  3:45 ` Baruch Siach
2012-05-09  3:47   ` Dmitry Golubovsky
2012-05-09  4:32     ` Baruch Siach
2012-05-07  3:29 Dmitry
2012-05-07  3:58 ` Baruch Siach
2012-05-07 10:31   ` Dimitry Golubovsky

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=4FAE741C.7090104@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