I have a Buffalo WZR-HP-G300NH running rc4 that I need to build newer freeswitch packages for.
Looking through the forum, I see whats needed to properly compile freeswitch and choose the modules needed, but is it possible to use the Imagebuilder for not only rc4, but for a recent checkout of freeswitch as well?

Thanks!

Why not check out from SVN repository to build from scratch?

Hey Mazi,
I'm not sure I follow you, in other words do not use Imagebuilder?
I had issues a while ago when I once attempted to build with my Fedora x64 wkst, so I thought the Imagebuilder would eliminate any guess work.

Also, openwrt rvn doesn't necessarily contain trunk for freeswitch, it still references the 1.0.6 tarball on the openwrt website, doesn't it?

Thanks!

ImageBuilder is old name for ImageGenerator. This tool does not compile anything.

To build = compile/cross compile stuff you need to utilize gcc. And to make life simpler you should use the Toolchain. http://wiki.openwrt.org/doc/howto/user.advanced

Thanks for clarifying that Orca, I'll hold off as the risk in making the unit non functional would be worse than accounting for a few quirks in the older freeswitch release.

How does one follow the status of packages, are there any automated means to know when the source used for a package gets updated, versus just the release of openwrt getting updated but using the same source for the specific package?

Thanks!

This contain only little information: http://wiki.openwrt.org/doc/howto/user.advanced

If you take a look at OpenWrt source repository downloads page, there are several SVN branches you can choose to download the whole source tree to compile from scratch, including building the GCC compilers to compile an OpenWRT firmware. (For me, I use the Development branch which is updated on a daily base.) There are many other ways to download from any OpenWRT SVN repositories. The way I did this is as follows:

1. Create and change into an empty directory, i.e. /opt/openwrt-svn-trunk
2. svn co svn://svn.openwrt.org/openwrt/trunk .
3. svn up
4. make package/symlinks
5. make defconfig
6. make menuconfig
7. make

In item #1 above, you can create and name the directory anyway you want. Just make sure the partition that you will be using to create the directory to contain OpenWRT source tree for compilation is big. If you just want to compile an OpenWRT firmware with a single build environment, perhaps a 10+ GB space should be sufficient. In my case, it easily uses up my 40+ GB with at least four different build environments.

In Item #6, you can configure how to (parallel) build OpenWRT firmware. This includes what to add in the firmware as well as which compiler/libraries to use.

In item #7, if you enable Global build settings -> Compile certain packages parallelized in make menuconfig (Item #6) and you have a multi-core computer system, you can make use of some (if not all) cores to speed up the build/compile of OpenWRT through the -j switch. In my case with an AMD64 PhantomII X3, I execute ionice -c3 nice -n20 make -j10 to build an OpenWRT firmware from scratch. For more information on this, please read Building OpenWrt in section Building Images. Parallel option may break compilation!

Mazi,
I appreciate your thorough response very much! I will give this a try. I noticed you were set as maintainer for the fs packages, and that it has been, or is going to be set to pull from trunk, nice. I take it since your response never indicated a known issue, https://dev.openwrt.org/ticket/9242 is fixed?

Again, thank you *very* much!

That ticket was assigned to someone else and I can't close it.