From: Emeric Vigier <emeric.vigier@savoirfairelinux.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/1] Makefile: add target to clean targetfs
Date: Thu, 16 Jul 2015 11:15:49 -0400 [thread overview]
Message-ID: <55A7CAA5.5020502@savoirfairelinux.com> (raw)
In-Reply-To: <55A5859B.2010809@savoirfairelinux.com>
>> Another problem that showed up was that some of the package install
>> steps dont seem separated very well. E.g. qt5 examples copies everything
>> from a certain staging-dir/* to target/..
>> A later qt5 module also creates files in that staging-dir, so next round
>> there's more files in target.
>>
>> I realize this is due to my way of not deleteing the staging dir any
>> longer - I used to in the beginning. If I recall correctly this is
>> because I noticed some packages copy files into staging/ during compile
>> and these files are then missing after a reinstall. I'm not entirely
>> sure though.
>
> I enabled qt4 and compare the targetfs after a target-clean, no
> differences:
>
> $ rsync -rvncl --delete --exclude '*.pyc' --exclude '*.pyo' --exclude
> 'tmp/ldconfig/aux-cache' output/target/ output/target.orig.qt4/
> sending incremental file list
>
> sent 15,095 bytes received 62 bytes 30,314.00 bytes/sec
> total size is 16,028,992 speedup is 1,057.53 (DRY RUN)
>
> With what QT configs did you meet problems specifically?
Qt4 showed no difference in the targetfs.
I disabled Qt4 and enabled Qt5 with several modules and saw no
differences in targetfs either. Here is my Qt5 config:
http://pastie.org/10296840
I had to switch from a buildroot toolchain to a Linaro-gcc-4.9 toolchain
to build Qt5. I haven't enabled Qt5-webkit because I fell into this
GCC-4.9 bug: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61207.
>> So my question is, in your approach, are you certain the re-installed
>> staging/ is the same as the original for all packages? Maybe you can run
>> some comparison like my rsync line for staging as well.
I only delete staging symlink, not the sysroot content. This patch does
not aim at fixing the black magic that some packages may be doing
between the staging dir and the target dir, just recreating the targetfs.
So the only improvement I have in mind for this patch is this:
rm -rf $(TARGET_DIR) $(STAGING_DIR) $(BUILD_DIR)/.root \
- $(BUILD_DIR)/*/.stamp_target_installed
$(BUILD_DIR)/*/.stamp_staging_installed
+ $(BUILD_DIR)/*/.stamp_target_installed
$(BUILD_DIR)/*/.stamp_staging_installed \
+ $(BUILD_DIR)/host-gcc-final-*/.stamp_host_installed
Do you have other things in mind?
>> regards,
>> Andreas
>
> thanks,
> --
> Emeric
Emeric
next prev parent reply other threads:[~2015-07-16 15:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 0:25 [Buildroot] [PATCH 1/1] Makefile: add target to clean targetfs Emeric Vigier
2015-03-10 4:45 ` Baruch Siach
2015-03-10 14:56 ` Emeric Vigier
2015-03-10 15:17 ` Baruch Siach
2015-03-10 19:28 ` [Buildroot] [PATCH v2 " Emeric Vigier
2015-03-10 23:41 ` Ryan Barnett
2015-03-11 5:06 ` Baruch Siach
2015-03-11 8:22 ` Angelo Compagnucci
2015-03-11 8:58 ` Baruch Siach
2015-03-12 8:32 ` Angelo Compagnucci
2015-03-12 14:56 ` Emeric Vigier
2015-03-12 14:44 ` Emeric Vigier
2015-03-12 14:46 ` Ryan Barnett
2015-03-12 8:36 ` Angelo Compagnucci
2015-03-12 15:59 ` Jérôme Oufella
2015-04-27 0:45 ` [Buildroot] [PATCH v3 " Emeric Vigier
2015-04-27 4:11 ` Baruch Siach
2015-04-28 14:36 ` Emeric Vigier
2015-04-27 8:28 ` Andreas Naumann
2015-04-28 15:06 ` Emeric Vigier
2015-07-14 21:56 ` Emeric Vigier
2015-07-16 15:15 ` Emeric Vigier [this message]
2015-07-23 20:51 ` Andreas Naumann
2015-10-04 16:56 ` Arnout Vandecappelle
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=55A7CAA5.5020502@savoirfairelinux.com \
--to=emeric.vigier@savoirfairelinux.com \
--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