From: Francesco RUNDO <francesco.rundo@st.com>
To: naresh kamboju <naresh.kernel@gmail.com>
Cc: ltp-list@lists.sourceforge.net, maxin john <maxinbjohn@gmail.com>,
brinda_mn@yahoo.co.in, Manas Kumar Nayak <maknayak@in.ibm.com>,
Oleg Nesterov <oleg@redhat.com>,
rohit.170309@gmail.com
Subject: Re: [LTP] [FIX HTML PATCH] ltp-genhtml
Date: Fri, 19 Jun 2009 14:19:08 +0200 [thread overview]
Message-ID: <4A3B823C.8020009@st.com> (raw)
In-Reply-To: <f5a7b3810906190312l75735199k43df06045d6264be@mail.gmail.com>
Hi Naresh,
naresh kamboju wrote:
>Hi Francesco,
>
>Thanks for your comments.
>
>I have few questions
>1. Are you compiling LTP on Host Machine and running on target boards?
>
Yes, precisely, I cross-build LTP on the HOST and run it on a different
TARGET machine.
>
>2. Is it cross complication with different tool chains?
>
Yes. I cross-compile for SH based platforms. See
http://www.stlinux.com/drupal for more details.
>3. Do you export KERNEL_VERSION and MACHINE_ARCHITECTURE on Host or target?
>
On the HOST when I process the LTP-log to generate the corresponding
HTML file.
>
>At my end I am compile with cross tool chains and copy the LTP
>complied source on target and executing the “runltp”.
>In my case I don’t get any variables from Host.
>I am not exporting Any Macros on target.
>
>I guess. Most of our LTP users do same.
>
I'm not sure about LTP users use the above approach, but what I think
should be taken into account is """what is better for all the LTP users""".
Do you agree ?
Now, can I do an advantages/disadavantages analysis of the methods (mine
and yours) ?
Yours (with usage of "uname -x"):
=====================
ADVANTAGES:
*) Automatic generation of information (of course, more safe!).
DISADVANTAGES:
*) Need PERL on the TARGET machine;
*) No flexible (I can't modify the info by adding more info....I have to
keep what "uname -x" provides);
*) Can be executed only on the TARGET (on the HOST it provides wrong
information);
Mine(with usage of "env variables"):
========================
ADVANTAGES:
*) No PERL is needed on the TARGET;
*) Flexible (I could use the output provided by "uname -x" executed on
the TARGET or I can add more info if needed);
*) Can be run both on the HOST and on the TARGET;
DISADVANTAGES:
*) Is not automatic as the user can properly define/export the relaetd
env variables.
Now, from above analysis I think should be taken a final decision.
>
>Thanks for your info.
>
No problem.
Best Regards
Francesco Rundo
------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2009-06-19 13:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 20:17 [LTP] [FIX HTML PATCH] ltp-genhtml naresh kamboju
2009-06-18 9:10 ` Francesco RUNDO
2009-06-18 15:08 ` naresh kamboju
2009-06-19 9:02 ` Francesco RUNDO
2009-06-19 10:12 ` naresh kamboju
2009-06-19 12:19 ` Francesco RUNDO [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=4A3B823C.8020009@st.com \
--to=francesco.rundo@st.com \
--cc=brinda_mn@yahoo.co.in \
--cc=ltp-list@lists.sourceforge.net \
--cc=maknayak@in.ibm.com \
--cc=maxinbjohn@gmail.com \
--cc=naresh.kernel@gmail.com \
--cc=oleg@redhat.com \
--cc=rohit.170309@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