Hi Paul,

Oh yeah, definitely. If that is what you are trying to accomplish, it makes 
perfect sense. Some poor folks actually start down that road of trying to 
create an image from sources, just wanting to make an image from the published 
repos and add a couple of things. Then it is way more than what they need to do 
to get a basic, bootable image. Ugh.

In light of that, though, perhaps I misunderstood what you meant by thinking 
the build would get any sources that were missing. Do you mean pulling them 
from the published Tizen repos, or do you mean cloning any missing projects 
automagically? I have to profess I don't know the ins-and-outs of using gbs to 
build images from locally built sources. The tools team or some other folks 
would have more actual experience with using that, and the pitfalls there. 
Unfortunately I haven't had the time to really play with that functionality 
yet. :|

Tracy



From: <Hanchett>, Paul 
<[email protected]<mailto:[email protected]>>
Date: Tuesday, August 20, 2013 11:34 AM
To: Tracy Graydon <[email protected]<mailto:[email protected]>>
Cc: "Ylinen, Mikko" <[email protected]<mailto:[email protected]>>, 
UM-PD-Engineering-Electrical-Infotainment-Portland 
<um-pd-engineering-electrical-infotainment-portl...@jaguarlandrover.com<mailto:um-pd-engineering-electrical-infotainment-portl...@jaguarlandrover.com>>,
 "[email protected]<mailto:[email protected]>" 
<[email protected]<mailto:[email protected]>>
Subject: Re: Process for bare metal build of IVI?

Tracy--

There are multiple perspectives; if I'm a developer trying to create a test 
image, then you're undoubtedly correct.  Probably no need to rebuild.

>From a product verification point of view, a corporate user will want to be 
>able to verify that they can build the target system from the sources they 
>have.  This is required so that product defects can be corrected once the 
>design team has moved on to other projects.

I've worked on projects that had "lost" sources.  It's a *very* uncomfortable 
place to be.  It is also impossible to evaluate the quality or security of a 
system if you can't both examine the source and replicate the build!

Paul

Kind Regards

Paul Hanchett

-------------------
Infotainment Engineer
MSX on behalf of Jaguar Land Rover
One World Trade Center, 121 Southwest Salmon Street, 11th Floor, Portland, 
Oregon, 97204

Email: [email protected]<mailto:[email protected]>
-------------------

Business Details:
Jaguar Land Rover Limited
Registered Office: Abbey Road, Whitley, Coventry CV3 4LF
Registered in England No: 1672070


On Tue, Aug 20, 2013 at 10:51 AM, Graydon, Tracy 
<[email protected]<mailto:[email protected]>> wrote:
Apparently one can also use gbs to create an image. I just tried it and it does 
work. It's obviously just a wrapper around mic itself. "gbs cr -K <kickstart 
file>" can be used to generate an image.

"Gbs build" will build a package from source. I suppose one could use it to 
build everything and then generate an image from it, but that sounds a lot like 
torture to me. ;) It is far easier, and likely much more reliable, to use mic 
and the existing repos to generate an image. If you need to include packages of 
your own, you can do that from a local repo easy enough.

Tracy





From: <Ylinen>, Mikko 
<[email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>>>
Date: Monday, August 19, 2013 10:13 PM
To: "Hanchett, Paul" 
<[email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>>>
Cc: UM-PD-Engineering-Electrical-Infotainment-Portland 
<um-pd-engineering-electrical-infotainment-portl...@jaguarlandrover.com<mailto:um-pd-engineering-electrical-infotainment-portl...@jaguarlandrover.com><mailto:um-pd-engineering-electrical-infotainment-portl...@jaguarlandrover.com<mailto:um-pd-engineering-electrical-infotainment-portl...@jaguarlandrover.com>>>,
 
"[email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>>"
 
<[email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>>>
Subject: Re: Process for bare metal build of IVI?

Hi Paul,

On Tue, Aug 20, 2013 at 12:51 AM, Hanchett, Paul 
<[email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>>>
 wrote:
I'm brining up my build of Tizen:IVI for the first time.  So I'm learning a lot 
as I go.  :-)

My current problem is that when I issue

gbs build -A i586

to build the image (I think!), I get an error:

[Inline images 1]

I'd expected that the build would get any sources I was missing but I guess not?

So then I tried to follow the wiki article "Creating a Tizen Image from 
Scratch..." and downloaded the source code.  Now, I can see source code on my 
machine but I still get the same build error when I issue the command above.

How do I do a top level rebuild of the entire tizen project, and should I have 
to download sources separately from the gbs build?

Why is a full local build needed? We have everything build for you in the 
download repositories.

If you want to build (read: create) a bootable image, you don't build sources 
into RPM
packages using gbs but you use mic (image creator) tool.

-- Mikko

_______________________________________________
IVI mailing list
[email protected]
https://lists.tizen.org/listinfo/ivi

Reply via email to