Jump to content

Category:BSD Tools: Difference between revisions

From EDM2
No edit summary
mNo edit summary
Line 1: Line 1:
Tools that can turn out code for OS/2 from a FreeBSD/OpenBSD/NetBSD environment (Cross compilation or other cross platform capabilities) or tools that can turn out BSD code from an eCS enviroment, or have some OS/2 specific utility or support even though they are primarily BSD executables. Also tools that allow interoperation-ability between OS/2 based systems and BSD systems be that in an interactive way such as networking and communications or simpler tools that allow the use or viewing of OS/2 related file formats in a BSD environment.
Tools that can turn out code for OS/2 from a FreeBSD/OpenBSD/NetBSD environment (Cross compilation or other cross platform capabilities) or tools that can turn out BSD code from an eCS enviroment, or have some OS/2 specific utility or support even though they are primarily BSD executables. Also tools that allow interoperation-ability between OS/2 based systems and BSD systems be that in an interactive way such as networking and communications or simpler tools that allow the use or viewing of OS/2 related file formats in a BSD environment.


In addition tools that are or were available for both OS/2 and BSD may be tagged as BSD Tools as well even though the BSD executable has no specific OS/2 related utility or function. This is because merely the existence of the same tool on two or more platforms may not just help in porting an application from one system to another even if there is a version mismatch, it also help in the planning of a multi-target project than makes, or potentially makes use of the tool,  effectively making the tool a part of the target [[API]] by proxy.
In addition tools that are or were available for both OS/2 and BSD may be tagged as BSD Tools as well even though the BSD executable has no specific OS/2 related utility or function. This is because merely the existence of the same tool on two or more platforms may not just help in porting an application from one system to another even if there is a version mismatch, it also help in the planning of a multi-target project that makes, or potentially makes use of the tool,  effectively making the tool a part of the target [[API]] by proxy.

Revision as of 22:31, 12 November 2014

Tools that can turn out code for OS/2 from a FreeBSD/OpenBSD/NetBSD environment (Cross compilation or other cross platform capabilities) or tools that can turn out BSD code from an eCS enviroment, or have some OS/2 specific utility or support even though they are primarily BSD executables. Also tools that allow interoperation-ability between OS/2 based systems and BSD systems be that in an interactive way such as networking and communications or simpler tools that allow the use or viewing of OS/2 related file formats in a BSD environment.

In addition tools that are or were available for both OS/2 and BSD may be tagged as BSD Tools as well even though the BSD executable has no specific OS/2 related utility or function. This is because merely the existence of the same tool on two or more platforms may not just help in porting an application from one system to another even if there is a version mismatch, it also help in the planning of a multi-target project that makes, or potentially makes use of the tool, effectively making the tool a part of the target API by proxy.

This category currently contains no pages or media.