From: Jeff S. <jef...@gm...> - 2007-06-05 16:10:39
|
oh geez trying to follow wpa_supplicant.mk with the patch was a nightmare. and make is creating the .config I was totally unfamiliar with the workings everytime in the past building wpa_supplicant I had to create .config myself I'm not sure what the line (cd $(WPA_SUPPLICANT_DIR); QUILT_PATCHES=$(BASE_DIR)/package/wpa_supplicant $(QUILT) push -a) does I undersatnd the first part "cd $(WPA_SUPPLICANT_DIR);" but what does QUILT_PATCHES=$(BASE_DIR)/package/wpa_supplicant $(QUILT) push -a do? I don't know where QUILT is getting populated and push? isn't push for mail? thats what the man page is talking about. I tried editing the patch and adding my stuff there but I'm just not good at editing patches. I add a line under it with (cd $(WPA_SUPPLICANT_DIR); patch -p0 < $(BASE_DIR)/package/wpa_supplicant/patch_wpa_supplicant-0.5.7-MSCHAP) and my patch has the following *** Makefile.org 2007-06-05 09:26:16.000000000 -0600 --- Makefile 2007-06-05 09:27:33.000000000 -0600 *************** *** 36,41 **** --- 36,44 ---- echo CONFIG_EAP_TTLS=y >> .config echo CONFIG_EAP_LEAP=y >> .config echo CONFIG_EAP_PEAP=y >> .config + echo CONFIG_EAP_MSCHAPV2=y >>.config + echo CONFIG_EAP_GTC=y >> .config + echo CONFIG_EAP_OTP=y >> .config echo CONFIG_CTRL_IFACE=y >> .config echo CONFIG_EAP_SIM=y >> .config @if [ "$(ARCH)" == "ARM" ]; then \ but this was rather ugly I'd like to clean up wpa_supplicant it looks like with the patches that its getting far from wpa_supplicant's default build procedure. Wouldn't it be more elegant putting .config in the $(BASE_DIR)/package/wpa_supplicant and just copying it from there? I don't think the Makefile should be recreating .config as its doing it just doesn't seem good to me. |
From: Craig H. <cr...@gu...> - 2007-06-05 17:19:36
|
On Jun 5, 2007, at 9:10 AM, Jeff Sadowski wrote: > I'm not sure what the line > (cd $(WPA_SUPPLICANT_DIR); > QUILT_PATCHES=$(BASE_DIR)/package/wpa_supplicant $(QUILT) push -a) > does quilt is a patch "stack" manager. If you look in the QUILT_PATCHES directory, you'll see a bunch of *.patch files plus a file called "series". series is the order in which the patches should be applied. QUILT is set to the path to the quilt binary, which is something like buildroot/toolchain/quilt/bin/quilt or such. "push - a" is an argument to the quilt command, which says "push all the patches on the stack" -- ie apply all patches mentioned in the series file. In order to add a new patch, you just add a new file in the QUILT_PATCHES directory, and then add the name of that patch file to the end of the series file. The QUILT_PATCHES directory, I normally write into build_arm_nofpu/ packagename/.patched so that after building, you can easily use quilt to manage the patches and update the package you want to work on... I have the following alias set up: alias qp='export QUILT_PATCHES=`cat .patched`' So I can do, eg: $ cd /path/to/buildroot/build_arm_nofpu/wpa_supplicant $ qp $ quilt new somenewpatch.patch $ quilt edit somefile $ quilt refresh $ cd ../.. $ svn add packages/wpa_supplicant/somenewpatch.patch $ svn commit -m 'Added some new patch to fix stuff' I'm slowly migrating all the packages I work on to using quilt instead of the buildroot patch-kernel.sh which is a lot less flexible. When you're dealing with something like the kernel which currently applies 41 different patches, not using quilt is pretty much impossible. C |
From: Jeff S. <jef...@gm...> - 2007-06-05 17:49:08
|
Oh I just got to try wpa_suppllicant after my horrable patching job it works :-) I'd like to request MSCHAP and the other authentications be put in thanks. On 6/5/07, Craig Hughes <cr...@gu...> wrote: > On Jun 5, 2007, at 9:10 AM, Jeff Sadowski wrote: > > > I'm not sure what the line > > (cd $(WPA_SUPPLICANT_DIR); > > QUILT_PATCHES=$(BASE_DIR)/package/wpa_supplicant $(QUILT) push -a) > > does > > quilt is a patch "stack" manager. If you look in the QUILT_PATCHES > directory, you'll see a bunch of *.patch files plus a file called > "series". series is the order in which the patches should be > applied. QUILT is set to the path to the quilt binary, which is > something like buildroot/toolchain/quilt/bin/quilt or such. "push - > a" is an argument to the quilt command, which says "push all the > patches on the stack" -- ie apply all patches mentioned in the series > file. > > In order to add a new patch, you just add a new file in the > QUILT_PATCHES directory, and then add the name of that patch file to > the end of the series file. > > The QUILT_PATCHES directory, I normally write into build_arm_nofpu/ > packagename/.patched so that after building, you can easily use quilt > to manage the patches and update the package you want to work on... > I have the following alias set up: > > alias qp='export QUILT_PATCHES=`cat .patched`' > > So I can do, eg: > > $ cd /path/to/buildroot/build_arm_nofpu/wpa_supplicant > $ qp > $ quilt new somenewpatch.patch > $ quilt edit somefile > $ quilt refresh > $ cd ../.. > $ svn add packages/wpa_supplicant/somenewpatch.patch > $ svn commit -m 'Added some new patch to fix stuff' > > I'm slowly migrating all the packages I work on to using quilt > instead of the buildroot patch-kernel.sh which is a lot less > flexible. When you're dealing with something like the kernel which > currently applies 41 different patches, not using quilt is pretty > much impossible. > > C > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |