Free 2.0.0 build 45731 software for linux

PLCash project is a platform-independent personal financial program.
Main features:
- Create and manage personal financial accounts.
- Import and export data from/to Quicken and other financial programs.
- Create reports and analyze your transactions using a sophisticated report generator.
- Import prices to track the performance of your investments.
- Interface with many other programs intuitively, using an industry-standard, transparent data file format.
- Reconcile your records with bank statements.
- Print checks in a variety of ways.

Tete project is an ear trainer.

Tete allows you to select intervals, chords, or scales and play examples of the selected sounds in a random order.

As each is played, it is highlighted in the list. Once you think you can tell what is playing, you can test yourself.

A series of sounds will be played, again at random, and you attempt to identify what has been played.

You can control how each sound is played back by changing the MIDI instrument, the octave range allowable, the root note, and whether the sounds are played ascending or descending.

LundFXP provides a GUI FXP application.
lundfxp is an FXP (direct site-to-site FTP) application ideal for mirroring.
It uses wxWindows and features full queue management, local site (for normal FTPing), automatic resume and restart, etc.
Enhancements:
- This is a stable release.
- It includes internal SafeTP encryption support and support for Mac OS X.

Ivy project is a very powerful dependencies manager oriented toward java dependency management, even if it can be used to manage dependencies of any kind.
For sure, Ivy is integrated with the most popular build management system for java projects.
For simple cases, ivy is really simple to use. Declare your dependencies, and thats all. See the quick start tutorial to check yourself, it should take less than 5 minutes !
Ivy can thus be used to bring the dependency management feature of maven to ant build files, for those of you who already use ant and who do not want to setup a maven project. But Ivy does not stop here, and provides much more great features !
Ivy is able to produce mainly two kind of reports: html reports and graph reports. HTML reports gives you a good understanding of what ivy did, and which dependencies your project depends upon. The graph reports let you have a good overview of the transitive dependencies (see below) and conflicts in your project.
Ivy most common use is to resolve dependencies and copy them in the lib dir of your project. Once copied, your build does not depend on ivy any more. Thus you can easily migrate existing builds using the lib dir pattern to store dependencies. Moreover, you can easily deliver your project with its dependencies so that the build file does not depend on ivy.
With Ivy, you usually do not have to adapt your project to ivy structure, its ivy which can be adapted to your environment.
Even if Ivy comes with a lots of default values to work out of the box, you can change many things in ivy. For sure, the dependencies repositories possibilities covers a lot of uses (file system, url based, repository chaining, ...). But thats not all. You can change the way ivy finds latest versions of your dependencies, you can change of conflict manager, you can choose if you want ivy to copy deps in your project libs or to use them directly from ivy cache, ...
When ivy does not what you want out of the box, you can often extend it to solve your problem. For instance, you can plug your own repository (like scott haug did for a svn repository now available in ivy tools). But you can also defines your own latest strategy and your own conflict manager. See how to extend ivy in the reference doc.
Imagine you have a component that you often reuse in your software developments. Imagine that this component has itself dependencies. Then with classical dependencies management, each time you use this component in your software you have to declare it as a dependency, but also all its dependencies.
With ivy its different: you simply write a dependency file once for the component, declaring its own dependencies, then anytime you want to use this component you simply have to declare a dependency on it.
And this is even more powerful if the component your software depends on changes of dependencies during its own development. Then, without ivy, you have to maintain all your components dependencies declaration each time the dependencies of this component change. With ivy, you update the ivy file of the component and thats it !
If you want to quickly start using this feature or simply see it in action with real world examples, check the official repository: ivyrep
Enhancements:
- This release adds enhanced support for reading Maven2 POM files, cleaner code for easier developer participation, and minor bugfixes (as documented in Jira).

smtpproxy project is a proxy for SMTP e-mail. Latest additions are spam and virus scanning, with/without quarantining and RBL support.
Main features:
- Virus Scanning
- Spam Filter
- DNS Blacklisting
- Mail Quarantining
- DNS Blacklisting
- CPU load monitoring
- Session status files
- POP3 before SMTP
- Received path dropping
Enhancements:
- clamav virus scanning support
- spamassissin spam detection support
- quarantining
- DNS blacklisting
- CPU load monitoring

Boost.Build is a system for large project software construction, which is simple to use and powerfull. Boost.Build project is an onging project to rewrite Boost.Build, improving design and making it more extensible.
Main features:
- Simple and high level target description language. In most cases name of target and list of sources is enough.
- Variant builds. You can build with your choice of basic variants (e.g. debug, release, profile...), toolsets (e.g. gcc and msvc) and specific properties (e.g. inlining off) from a single command invocation.
- Portability. ``Feature Normalization allows to fine-tune targets independently from the toolset used, and modular toolset descriptions are employed to generate actual build instructions.
- Multi-project builds. Several projects can be combined and built together, with dependencies correctly tracked. Typically, the setting (like include paths and defines) needed to use other project will be handled automatically.
- Extensibility. New file types and tools can be easily added
Enhancements:
- Support was added for several new tools, including the Qt4 library.
- An "indirect requirement" feature was added.
- Several improvements were made in the "install" target.
- The --build-dir, --debug-building, and --clean-all command line options were added.
- Numerous bugs were fixed, and interface improvements were done.

KJam is a build tool like make. It uses a syntax similar to Jam, with more powerful features than the original Jam.
It has built-in very fast dependency scanning, per-target viewpathing, and C-like control flow. It is optimized for multi-processor machines. It can accelerate building by launching build actions on a distributed peer to peer network of build servers.
KJam Build Tool is designed to support large projects with thousands of targets, or projects requiring building on many target architectures.
KJam is designed to be:
Unintrusive and clean KJam is small. It has negligible CPU overhead, and it doesnt create or leave behind temporary files.
Scalable KJam is able to build large projects spread across many directories in a single pass and can manage and distribute build steps to multiple processors on one or more networked machines.
Highly portable KJam currently runs only on Windows, but it is designed to be easily portable. Ports to Linux and OSX are planned.
Multiplatform Platform independent rules and platform specific actions can be defined separately from dependency rules.
Customizable Developers can enhance and extend KJam by creating user defined rules to utilize other built-in directives.
Language KJam includes flow-control statements, variables, and a few other features of general purpose languages.
Automatic Dependencies KJam computes dependencies for its targets during building. There is no need for a separate off-line make depend step.
Enhancements:
- A new "immediate" action modifier keyword was added, which causes actions to be run as soon as they are parsed, instead of during the command phase.
- Output formatting was improved.
- Several bugs were fixed.