ltib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Ltib] Porting asterisk to ltib


From: Stuart Hughes
Subject: Re: [Ltib] Porting asterisk to ltib
Date: Wed, 16 Jul 2008 08:32:31 +0100

Hi Vadim,

Both these are set as environment variables inside the ltib script.

SCB_WANT_CF is set when you pass the option -c (--configure) to ltib.
PKG_BUSYBOX_WANT_CF is set when the corresponding option is turn on
during a configuration session in ltib:

$ ./ltib -m config
[ ]   Configure busybox at build time

This prompt is set in config/userspace/packages.lkc:

config PKG_BUSYBOX_WANT_CF
    depends PKG_BUSYBOX
    bool "Configure busybox at build time"
    help
      Select this if you want to interactively configure busybox during
      the build.  A copy of the configured value will be put back
      into the platforms configuration directory, with the suffix .dev


Note that -c is available so that you can do:

$ ./ltib -p <pkg> -c

This lets you drop to the config screen in your package without having
to fiddle with the main config.

Regards, Stuart



On Tue, 2008-07-15 at 18:21 +0200, Vadim Lebedev wrote:
> Stuart 
> Thanks a lot for info and pointers
> 
> Looking into busybox.spec i've one more question how the vars like
> "$PKG_BUSYBOX_WANT_CF" or  "$SCB_WANT_CF"
> 
> set during the build process?
> 
> Thanks
> Vadim
> 
> 
> Stuart Hughes wrote: 
> > Hi Vadim,
> > 
> > Take a look at dist/lfs-5.1/busybox/busybox.spec which needs something
> > similar.
> > 
> > Basically you need a clause in the build section of the spec file like
> > (sub busybox for zaptel):
> > 
> > if [ -n "$PKG_BUSYBOX_WANT_CF" -o -n "$SCB_WANT_CF" ]
> > then
> >     make menuconfig HOSTCC="$BUILDCC"
> >     cp .config $PLATFORM_PATH/$PKG_BUSYBOX_PRECONFIG
> > else
> >     yes "" | make config HOSTCC="$BUILDCC"
> > fi
> > 
> > The in config/userspace/packages.lkc you need to add your package.  Look
> > at busybox again to get the idea.  Finally you need to add a mapping for
> > your package name to spec file names in config/userspace/pkg_map.  All
> > this is described in the faq (see bitshrine.org or the doc directory).
> > 
> > The group depends on what it does, the list you can chose from is
> > defined in /usr/share/doc/rpm-<ver>/GROUPS, but basically something from
> > this list:
> > 
> > Amusements/Games
> > Amusements/Graphics
> > Applications/Archiving
> > Applications/Communications
> > Applications/Databases
> > Applications/Editors
> > Applications/Emulators
> > Applications/Engineering
> > Applications/File
> > Applications/Internet
> > Applications/Multimedia
> > Applications/Productivity
> > Applications/Publishing
> > Applications/System
> > Applications/Text
> > Development/Debuggers
> > Development/Languages
> > Development/Libraries
> > Development/System
> > Development/Tools
> > Documentation
> > System Environment/Base
> > System Environment/Daemons
> > System Environment/Kernel
> > System Environment/Libraries
> > System Environment/Shells
> > User Interface/Desktops
> > User Interface/X
> > User Interface/X Hardware Support
> > 
> > Also, if you're package is kernel drivers, you'll need to add the
> > clause:select PKG_KERNEL_LEAVESRC to your entry in packages.lkc.  For an
> > example of how to build kernel modules outside the kernel tree, look at:
> > config/userspace/package.lkc : PKG_HELLOWORLD_MOD and the corresponding
> > spec file: dist/lfs-5.1/helloworld/hello_mod.spec
> > 
> > Regards, Stuart
> > 
> > 
> > On Tue, 2008-07-15 at 17:02 +0200, Vadim Lebedev wrote:
> >   
> > > Hi Stuart,
> > > 
> > > Thanks for your help offer
> > > 
> > > Here is first question:
> > > 
> > > In order to build asterisk i need to build zaptel package which
> > > includes various drivers
> > > Zaptel package provides an interactive 'menuselect'  utility allowing
> > > for selection of drivers
> > > to be built, which is 1) built uisng $(HOSTCC)  compiler and supposed
> > > to be run using 'make menuconfig' command
> > > 
> > > I'm trying understand how to hook the OPTIONAL activation of this
> > > utility into the build
> > > 
> > > Another question what would be the correct group for asterisk and
> > > drivers?
> > > 
> > > Thanks
> > > Vadim  
> > > 
> > > 
> > > Stuart Hughes wrote: 
> > >     
> > > > Hi Vadim,
> > > > 
> > > > I've not heard of anyone having done this, but I'd help if you have
> > > > questions.
> > > > 
> > > > Regards, Stuart
> > > > 
> > > > On Tue, 2008-07-15 at 15:30 +0200, Vadim Lebedev wrote:
> > > >   
> > > >       
> > > > > Hello,
> > > > > 
> > > > > I'm trying to port asterisk to ltib environment
> > > > > 
> > > > > I wonder if somebody already did it  and  will be willing to share 
> > > > > info 
> > > > > and/or .spec files and/or advice.
> > > > > 
> > > > > Thanks
> > > > > Vadim
> > > > >     
> > > > >         
> > > > 
> > > >   
> > > >       
> > 
> > 
> >   
>     





reply via email to

[Prev in Thread] Current Thread [Next in Thread]