uCommon Telephony Libraries
The Make system is a refined replacement for the Make ruleset provided with the Axis cris system. Mostly this was done to make it easier to drop in Make rules for other and different embedded target development systems and cross-compiler environments in the future.
One unpacks the uCommon tarball into a directory like most other free software. You should also install the cris compiler and tools. I assume the procedure would be similar for other eLinux-based target development systems, but so far I have worked primarily with only the Axis tools.
Once the tarball is extracted, you should look into the master ``rules'' file. This file holds definitions for use with your compile target environment and may have to be altered based on your cross-compiler arrangement. The values provided are based on my personal configuration. I choose to put the cris system in /arch/cris rather than the more common /usr/local/cris, for example.
If you are using something other than the ETRAX, you may need to refine the rules file further for your use. If you do, please send an e-mail explaining what you changed and why. I would like to incorporate rules configurations for other embedded target development environments as part of the standard distribution of uCommon.
If you are using a standard GNU/Linux host and just wish to build and/or use uCommon to build GNU/Linux applications on your host machine directly, you should not need to modify any files in the distribution. Simply enter make host followed by make. You can also do a make install.
To use uCommon in your projects, simply include the appropriate headers, found in the uCommon header directory, and add -luCommon in your list of link libraries.
The new DBS Server is, of course, being written using the uCommon library. In addition, uMedia library is planned to deal with network audio and rtp, and uScript library, based on my ccscript, will offer a small and easily embedded script-language interpreter.
David Sugar is a maintainer for several GNU packages, including Bayonne and Common C++, as well as the author of numerous other lesser known free software packages. David is an active member of the Embedded Linux Consortium, the public's elected representative to the International Softswitch Consortium and acting CTO of Open Source Telecom Corp.
|Non-Linux FOSS: libnotify, OS X Style||Jun 18, 2013|
|Containers—Not Virtual Machines—Are the Future Cloud||Jun 17, 2013|
|Lock-Free Multi-Producer Multi-Consumer Queue on Ring Buffer||Jun 12, 2013|
|Weechat, Irssi's Little Brother||Jun 11, 2013|
|One Tail Just Isn't Enough||Jun 07, 2013|
|Introduction to MapReduce with Hadoop on Linux||Jun 05, 2013|
- Containers—Not Virtual Machines—Are the Future Cloud
- Non-Linux FOSS: libnotify, OS X Style
- Linux Systems Administrator
- Validate an E-Mail Address with PHP, the Right Way
- Lock-Free Multi-Producer Multi-Consumer Queue on Ring Buffer
- Senior Perl Developer
- Technical Support Rep
- UX Designer
- RSS Feeds
- Introduction to MapReduce with Hadoop on Linux
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?