I have encountered the following problems while compiling images: After make kernel menuconfig i was i not able to fully revert the changes with svn revert -R target/linux/ and even tho svn diff target/linux/ does not output anything some previous selected options still persist when doing make menuconfig and i am unable to revert them even after doing make defconfig. Only make distclean solved the issue
When adding my own templates to the final image and placing them inside <buildroot dir>/files/ the only ones the image ends up by being compiled with, are <buildroot dir>/files/bin. All the other files in <buildroot dir>/files/etc and so on do not get added. I thought it had to do with file permissions but they are the same as the ones i have with an older buildroot. All files have the shell user's permissions. I also have a question regarding the use of custom templates. By trial and error i noticed that i cannot use the following configuration files for all my images - wireless - network - system The reason being is for example that the network configuration file for a dlink is not fully the same as for example tp-link. Having any of these config files in <buildroot dir>/files/config/ will eventually "brick" routers that for example have a different switch configuration; will fail working properly for wireless and have functioning problems with system. These files exist in <buildroot dir>/package/base-files/files/etc/ and while building the image they get merged with the specifics of the hardware. My question is if we can have the same "merging" task done while having <buildroot dir>/files/ . For example; having the network file in <buildroot dir>/files/config/network with all the settings we need which then will be merged with the switch specifics of the hardware that it is being compiled for. -- Site: http://wirelesspt.net Mesh: http://tinyurl.com/wirelesspt Admin: http://wirelesspt.net/wiki/Cmsv Twitter: http://twitter.com/wirelesspt Suporte técnico via sms: 91 19 11 798 Donativos/Paypal: http://tinyurl.com/doar-verba Chave publica PGP/SSH: http://wirelesspt.net/arquivos/pk Email assinado digitalmente pelo emissor assegurando autenticidade
0x782BF73E.asc
Description: application/pgp-keys
signature.asc
Description: OpenPGP digital signature
_______________________________________________ openwrt-users mailing list [email protected] https://lists.openwrt.org/mailman/listinfo/openwrt-users
