forked from Ninoh-FOX/toolchain
-
Notifications
You must be signed in to change notification settings - Fork 0
toolchain for RG350 and PG2 rogue cfw
License
Shut3n/toolchain
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
====================================================== ============= RG350 BUILD INSTRUCTIONS =============== ====================================================== ### Pre-Build Steps ### $ sudo apt-get update $ sudo apt-get install bison flex gettext texinfo wget cpio python unzip mercurial subversion libncurses5-dev libc6-dev-i386 bzr libssl-dev ## you need a javac compiler, (i.e. sudo apt-get install gcj-4.9-jdk) Make the folder /opt and download http://www.gcw-zero.com/files/opendingux-gcw0-toolchain.2014-08-20.tar.bz2 how superuser move the bz2 file in /opt folder and type /opt$ sudo tar jxvf ./opendingux-gcw0-toolchain.2014-08-20.tar.bz2 /opt$ sudo rm -rf ./opendingux-gcw0-toolchain.2014-08-20.tar.bz2 the next step is add the GCW0 Path in .bashrc file in your home folder, type this in the last line in the file: export PATH="/opt/gcw0-toolchain/usr/bin:${PATH}:/opt/gcw0-toolchain/usr/mipsel-gcw0-linux-uclibc/sysroot/usr/bin" ### Build Steps ### ## Enter the directory where you want to clone the git repo $ git clone https://github.com/Ninoh-FOX/toolchain.git $ cd toolchain $ make rg350_defconfig $ make ====================================================== To build and use the buildroot stuff, do the following: 1) run 'make menuconfig' 2) select the packages you wish to compile 3) run 'make' 4) wait while it compiles 5) Use your shiny new root filesystem. Depending on which sort of root filesystem you selected, you may want to loop mount it, chroot into it, nfs mount it on your target device, burn it to flash, or whatever is appropriate for your target system. You do not need to be root to build or run buildroot. Have fun! Offline build: ============== In order to do an offline-build (not connected to the net), fetch all selected source by issuing a $ make source before you disconnect. If your build-host is never connected, then you have to copy buildroot and your toplevel .config to a machine that has an internet-connection and issue "make source" there, then copy the content of your dl/ dir to the build-host. Building out-of-tree: ===================== Buildroot supports building out of tree with a syntax similar to the Linux kernel. To use it, add O=<directory> to the make command line, E.G.: $ make O=/tmp/build And all the output files (including .config) will be located under /tmp/build. More finegrained configuration: =============================== You can specify a config-file for uClibc: $ make UCLIBC_CONFIG_FILE=/my/uClibc.config And you can specify a config-file for busybox: $ make BUSYBOX_CONFIG_FILE=/my/busybox.config To use a non-standard host-compiler (if you do not have 'gcc'), make sure that the compiler is in your PATH and that the library paths are setup properly, if your compiler is built dynamically: $ make HOSTCC=gcc-4.3.orig HOSTCXX=gcc-4.3-mine Depending on your configuration, there are some targets you can use to use menuconfig of certain packages. This includes: $ make HOSTCC=gcc-4.3 linux-menuconfig $ make HOSTCC=gcc-4.3 uclibc-menuconfig $ make HOSTCC=gcc-4.3 busybox-menuconfig Please feed suggestions, bug reports, insults, and bribes back to the buildroot mailing list: [email protected]
About
toolchain for RG350 and PG2 rogue cfw
Resources
License
Stars
Watchers
Forks
Releases
No releases published
Packages 0
No packages published
Languages
- Makefile 56.9%
- Shell 16.0%
- C 12.5%
- Python 8.6%
- M4 2.2%
- C++ 1.7%
- Other 2.1%