build t2 7.0 x86 desktop target installcd with gnome

[eazy24]

Hi,could anyone please explain me how can i build t2 7.0 x86 desktop
target installcd with gnome
,i want minimal gnome+ programs(if this is possible)
I tried it two times but filed because of deps,i dont understand how
can i mark gnome programs i want to be included,i tried it like:
added example alacarte->marked all alacarte deps on packages file,but
still some of deps have also deps and my build still fails
because of missing deps.
Please explain,how i can choose what i want!
I have build generic minimal with x.org
and default generic minimal successfully,but i dont understand how to
move on and build more userend system with gnome windowmanager.
thank you

--
Lugupidamisega
Jüri Izberg
http://www.ji-disain.pri.ee


-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
lists@... with a subject of: unsubscribe t2

[Mike N]

eazy24 wrote:

Hi,could anyone please explain me how can i build t2 7.0 x86 desktop
target installcd with gnome
still some of deps have also deps and my build still fails
because of missing deps.
Please explain,how i can choose what i want!

Hi,

My "answer" is probably not what you want to hear, but in the same situation I have done it this way

- Select packages in the packages template based on my "best guesses" (marking X or - or commenting out lines from existing "full featured" package list)
- ./scripts/Build-Target -cfg myConfigName
- Fails to compile some app because of missing dependency (error can be seen from src.xxxx/ERROR-LOG file)
- Modify package list based on the error and re-trying :-)

Well, this is the hard way to do it, but I dont know any automagical way to list all dependencies recursively. There probably is some script command to do it, but I don't know it. Fortunately my configuration is not changing all the time so this "hard way" was almost-once-in-a-life-time case.

mike n

[Rene Rebe]

Hi,

Mike N wrote:

>
>
> eazy24 wrote:
>  
>> Hi,could anyone please explain me how can i build t2 7.0 x86 desktop
>> target installcd with gnome
>> still some of deps have also deps and my build still fails
>> because of missing deps.
>> Please explain,how i can choose what i want!
>>
>>    
>
> Hi,
>
> My "answer" is probably not what you want to hear, but in the same situation
> I have done it this way
>
> - Select packages in the packages template based on my "best guesses"
> (marking X or - or commenting out lines from existing "full featured"
> package list)
> - ./scripts/Build-Target -cfg myConfigName
> - Fails to compile some app because of missing dependency (error can be seen
> from src.xxxx/ERROR-LOG file)
> - Modify package list based on the error and re-trying :-)
>
> Well, this is the hard way to do it, but I dont know any automagical way to
> list all dependencies recursively. There probably is some script command to
> do it, but I don't know it. Fortunately my configuration is not changing all
> the time so this "hard way" was almost-once-in-a-life-time case.
>
> mike n
>  

Yes, there is no other helper, except the package pre-selection
templates of the generic target.

We mostly delayed the implementation of more magic dependency
selection because embedded targets usually manage to build
even more minimal packages without normally hard enforced
deps by patching them - more automatic selection would usually
contradict this.

But we plan to implement more automatic selection in the future,
and also differentiate between build time and run-time deps
(currently the automatic dependency .cache files only contain
build-time deps).

Have fun,

--
  René Rebe - ExactCODE GmbH - Europe, Germany, Berlin
  http://exactcode.de | http://t2-project.org | http://rene.rebe.name



-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
lists@... with a subject of: unsubscribe t2

[William Tracy]

On Wed, Apr 1, 2009 at 12:46 AM, René Rebe <rene@...> wrote:
> We mostly delayed the implementation of more magic dependency
> selection because embedded targets usually manage to build
> even more minimal packages without normally hard enforced
> deps by patching them - more automatic selection would usually
> contradict this.

How about adding --track-dependencies flag to Built-Target, such that
target developers who want to manually handle dependencies can still
do so?

--
William Tracy
afishionado@... -- wtracy@...
Vice President, Cal Poly Linux Users' Group
http://www.cplug.org

"I disapprove of what you say, but I will defend to the death your
right to say it."
    -- Evelyn Beatrice Hall, frequently mis-attributed to Voltaire


-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
lists@... with a subject of: unsubscribe t2