FreeCLX source code available on SourceForge

By: John Ray Thomas

Abstract: FreeCLX, the Open Source project for Borland's CLX Component Library for Linux, is now available for collaboration.

Have you ever been in the position of wishing a certain feature would be implemented in your component library of choice? Or found a bug that you wished you could simply fix rather than waiting for the vendor to release a patch? Often developers using closed source libraries are stuck at this point and are at the mercy of their vendors.

The Open Source development model allows a developer using a libary to make any modifications they see fit and redistribute it. Furthermore, it allows developers to submit those changes back to the original developers for inclusion into the library. This changes the developers role from consumer to collaborator. Many large software projects have been successful with this model of development including the GNU/Linux operating system and the Apache Web Server.

What is FreeCLX?

FreeCLX is the Open Source project for Borland's CLX Component Library for GNU/Linux. The BaseCLX, VisualCLX and DataCLX packages have been dual-licensed to allow for open source collaboration. They are licensed under both the Borland proprietary No-Nonsense License and the GNU General Public License(GPL).

This means that developers with a licensed copy of Kylix Desktop or Server developer editions can deploy their applications as either a proprietary application (or an open source application compatible with the Borland No-Nonsense license) or as a GPL application. There will be a free download version of the Kylix IDE made available later this year, called the OpenEdition, which will allow for GPL only development with FreeCLX.

You may rebuild and redeploy FreeCLX in any manner you choose. In order to maintain compatibility with applications developed and distributed against the official Borland Kylix CLX libraries, modified binary runtime packages must be distributed under names other than those deployed officially from Borland.

The FreeCLX project has been made available using SourceForge to allow for anonymous CVS access, bug reports and patch submissions. The project can be found at http://sourceforge.net/projects/freeclx.

How to Collaborate

First, you need the source code. The source is available in a CVS archive on SoureForge. You will need a CVS client to get it. The latest version of CVS is 1.11 and there are several GUI and command-line clients available for both the Windows and Linux platforms. You can find a list of links to these downloads from CVSHome.org

Now that you have CVS you need to login to the SourceForge server as an anonymous user. This provides read-only access to the source tree. The CVS command-line to accomplish this is:

cvs -d :pserver:anonymous@cvs.freeclx.sourceforge.net:/cvsroot/freeclx login

When CVS asks for your password, hit Enter for a blank password.

Now that you are logged in you need to check out the FreeCLX module. This is accomplished with the following CVS command:

cvs -z3 -d:pserver:anonymous@cvs.freeclx.sourceforge.net:/cvsroot/freeclx co freeclx

This will create a subdirectory, called freeclx, under your current working directory and will download the source into it.

Submission Ground Rules

We welcome changes and additions to the FreeCLX library to be submitted. To submit your changes, you need to create a patch file by running diff against your changes and the original file.

Here are the ground rules for patch submissions.

  1. All submissions must be in universal diff format (diff -u4). It must be clear what version of the file is the base for the diff.

    For example, diff -u4 original_file patched_file > filename.patch

    You may also use the cvs diff command to accomplish this.

  2. All submissions must be as small and targeted as possible. The larger the submission the more likely it will be rejected.

  3. All submissions should be independent of each other or explicitly state the dependencies. (That is, if patch two requires patch one, state so in the patch description).

  4. All submissions must be made through the SourceForge patch submission utility.

  5. When a submission is to be accepted it must be digitally signed by the submitter and include a waiver allowing Borland to ship the changes with our proprietary license. When you are at the point of having your submission accepted we will contact you with more details.

So Get To It

Now that you have been empowered to collaborate with us on FreeCLX we look forward to reviewing your new features and/or bug fixes.

Server Response from: ETNASC01