From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] changing sources before patching
Date: Sun, 13 Mar 2016 22:53:42 +0100 [thread overview]
Message-ID: <56E5E166.7090403@mind.be> (raw)
In-Reply-To: <56E5BF43.90507@lespocky.de>
On 03/13/16 20:28, Alexander Dahl wrote:
> Hei hei,
>
> in the fli4l [1] project, we use buildroot as build system, a little
> custom stuff on top, but basically it's buildroot. Now Carsten wanted to
> make a package for sfftools [2], especially sfftobmp3. The source is
> only available from subversion and we need to patch it. The problem we
> face is: some files we need to patch (e.g. configure.ac) have CRLF aka
> DOS line endings and patch fails then. So we want to convert the line
> endings to LF aka unix before patching. Is this possible with buildroot
> and how? Or does anyone else has a good idea for an elegant solution to
> this problem?
As Bernt wrote, you can have a patch containing the correct CRLF.
Alternatively, you can run a conversion in the _PRE_PATCH_HOOKS.
Regards,
Arnout
>
> (please keep Carsten and Christoph in Cc)
>
> Greets
> Alex
>
> [1] http://www.fli4l.de/
> [2] https://sourceforge.net/projects/sfftools/
>
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
--
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: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
prev parent reply other threads:[~2016-03-13 21:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-13 19:28 [Buildroot] changing sources before patching Alexander Dahl
2016-03-13 19:45 ` Bernd Kuhls
2016-03-13 21:53 ` 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=56E5E166.7090403@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