From: Michal Simek <michal.simek@petalogix.com>
To: Garrett Cooper <yanegomi@gmail.com>
Cc: ltp-list@lists.sourceforge.net, Mike Frysinger <vapier@gentoo.org>
Subject: Re: [LTP] [PATCH 3/4] Make system enhancements, Draft 3
Date: Tue, 21 Jul 2009 15:01:04 +0200 [thread overview]
Message-ID: <4A65BC10.8000908@petalogix.com> (raw)
In-Reply-To: <364299f40907200032x28cc62cdn73ebb42f31d80361@mail.gmail.com>
Garrett Cooper wrote:
> On Sun, Jul 19, 2009 at 10:25 PM, Michal
> Simek<michal.simek@petalogix.com> wrote:
>
>> Garrett Cooper wrote:
>>
>>> Version 3 of the epic saga: [PATCH 3/4] Make system enhancements.
>>>
>
> [...]
>
>
>> I cross compile LTP all the time and Mike do the same for BlackFin.
>> cross-compilation was possible.
>> CROSS_COMPILE=mb-linux-
>> make
>>
>
> Yes, as Mike corrected me, what I was looking for was `out-of-tree
> build support', where a group (say Montevista) could build more than
> one architecture, or build with more than one compiler / toolchain /
> sys-root using the same source directory.
>
out-of-tree compilation is nice.
> Well, that and a few Makefiles were broken as far as cross-compilation
> was concerned, in particular library generation on some architectures,
> and hardcoded paths to libraries, host based file scanning heuristics,
> you name it.
>
> This is the first leap forward in correcting all of these things, and
> it will not be the last step that must be made as this project is
> large and the changes / test stimuli are as well.
>
> [...]
>
>
>>> +LIBOBJS := $$(addprefix $$(builddir)/,$$(patsubst %.c,%.o,$$(LIBSRCS)))
>>>
>>>
>> long line.
>>
>
> I try my best to do two things with makefile code:
> 1. align Makefile code with single tab, then spaces.
> 2. compress as many statements as possible to reduce the number of
> required evaluation steps, because that can result in interesting
> behavior from make with define blocks...
>
> I will try and compress the space further (that line was tab
> separated) in a style cleanup commit after this is all said and
> committed, if I don't get to it sooner. It's just easier to add and
> delete tabs for now :).
>
make no sense to send a patch with coding style violation and then send
next patch
which fixed that bad coding style. It is better to do it properly in
first time.
We have to clean whole LTP source code not pollute it.
Michal
> Thanks!
> -Garrett
>
--
Michal Simek, Ing. (M.Eng)
PetaLogix - Linux Solutions for a Reconfigurable World
w: www.petalogix.com p: +61-7-30090663,+42-0-721842854 f: +61-7-30090663
------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2009-07-21 13:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-18 21:19 [LTP] [PATCH 3/4] Make system enhancements, Draft 3 Garrett Cooper
2009-07-20 5:25 ` Michal Simek
2009-07-20 7:32 ` Garrett Cooper
2009-07-21 13:01 ` Michal Simek [this message]
2009-07-21 13:57 ` Garrett Cooper
2009-07-21 14:01 ` Michal Simek
2009-07-30 18:28 ` Subrata Modak
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=4A65BC10.8000908@petalogix.com \
--to=michal.simek@petalogix.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=vapier@gentoo.org \
--cc=yanegomi@gmail.com \
/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