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.
Practical Task Scheduling Deployment
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.View Now!
|The Firebird Project's Firebird Relational Database||Jul 29, 2016|
|Stunnel Security for Oracle||Jul 28, 2016|
|SUSE LLC's SUSE Manager||Jul 21, 2016|
|My +1 Sword of Productivity||Jul 20, 2016|
|Non-Linux FOSS: Caffeine!||Jul 19, 2016|
|Murat Yener and Onur Dundar's Expert Android Studio (Wrox)||Jul 18, 2016|
- Stunnel Security for Oracle
- The Firebird Project's Firebird Relational Database
- SUSE LLC's SUSE Manager
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Doing for User Space What We Did for Kernel Space
- SuperTuxKart 0.9.2 Released
- Google's SwiftShader Released
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide