All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [Question] How do I build source code at source folder?
Date: Sat, 4 Apr 2020 13:41:34 +0200	[thread overview]
Message-ID: <20200404114134.GD22325@scaer> (raw)
In-Reply-To: <CAF6vTZZctgOOnqcseZ5-UVGQbg2baC8Le4qazOZ2rFpdH_3tcw@mail.gmail.com>

Psychesnet, All,

On 2020-04-04 14:52 +0800, Psychesnet Hsieh spake thusly:
> Thanks and yes, I know I can use _OVERRIDE_SRCDIR to define local folder as source.
> But what I need is directly build source code at source folder without copy/rsync.

That is not possible.

Regards,
Yann E. MORIN.

> And eventually the target object will install into output/fakeroot folder.
> Do you have any idea to get it done? Thanks.
> Heiko Thiery < [1]heiko.thiery@gmail.com> ? 2020?4?3? ??
> ??5:51???
> 
>   Hi Eric,
> 
>   Am Fr., 3. Apr. 2020 um 11:07 Uhr schrieb Eric Hsieh < [2]psychesnet@gmail.com>:
>   >
>   > Hi everyone,
>   >
>   > Now, Im trying to create a special mode which can help me to build source
>   > code at source folder instead of output/build folder. I checked the makefile
>   > at package, looks like there is no directly way to be done.
>   > So, I would like to ask is it possible to be done? If yes, please give me
>   > some tips. Thanks.
> 
>   If you want to build a package from an external source folder you can
>   specify the source directory by creating the? $(CONFIG_DIR)/ [3]local.mk
>   file and set the <pkg>_OVERRIDE_SRCDIR varialbe. But this will
>   copy/rsync your sources and build your package at output/build.
> 
>   Please check "8.13.6. Using Buildroot during development" in the
>   buildroot user manual for more information about that.
> 
>   --
>   Heiko
> 
> Links:
> 1. mailto:heiko.thiery at gmail.com
> 2. mailto:psychesnet at gmail.com
> 3. http://local.mk

> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot


-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

      parent reply	other threads:[~2020-04-04 11:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-03  9:07 [Buildroot] [Question] How do I build source code at source folder? Eric Hsieh
2020-04-03  9:50 ` Heiko Thiery
2020-04-04  6:52   ` Psychesnet Hsieh
2020-04-04  6:57     ` Heiko Thiery
2020-04-04 13:24       ` Psychesnet Hsieh
2020-04-06 11:59         ` Heiko Thiery
2020-04-04 11:41     ` Yann E. MORIN [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=20200404114134.GD22325@scaer \
    --to=yann.morin.1998@free.fr \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.