This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
| Other format: | [Raw text] | |
Hi folks,
some ideas for making the configuration some bit easier and
more comfortale:
#1: Introduce a new target kernelconfig
* it fetches and decompresses the kernel (if not done yet)
* copies the kernel configfile to the kerneltree
* fixes some options coming from ct-ng config (ie. arch, cpu, ...)
* runs kernel's make menuconfig
* checks for conflicts between kernel config and ct-ng config
* (if changed) copy back the kernel config file
#2: The same process could be done w/ uclibc config (and maybe
others too)
#3: A new target target "initconfig" which creates config files
for ct-ng, kernel, uclibc and set proper pathes to them.
#4: Automatically fix uclibc config, ie. set the kernel include
dir to something like :
${CT_SRC_DIR}/${CT_KERNEL}-${CT_KERNEL_VERSION}/include
cu
--
---------------------------------------------------------------------
Enrico Weigelt == metux IT service - http://www.metux.de/
---------------------------------------------------------------------
Please visit the OpenSource QM Taskforce:
http://wiki.metux.de/public/OpenSource_QM_Taskforce
Patches / Fixes for a lot dozens of packages in dozens of versions:
http://patches.metux.de/
---------------------------------------------------------------------
--
For unsubscribe information see http://sourceware.org/lists.html#faq
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |