Searches without login should now work. You must get asked to click a button.
Port details
cliAn implementation of the ECMA CLI and the ECMA C# language
20021101langΣ=1 20021101Version of this port present on the latest quarterly branch.
BROKEN: Does not handle PTHREAD_LIBS correctly DEPRECATED: 2006-12-01 IGNORE: is marked as broken: Does not handle PTHREAD_LIBS correctly RESTRICTED: "license terms need to be reviewed"
There is no maintainer for this port.
Any concerns regarding this port should be directed to the FreeBSD Ports mailing list via ports@FreeBSD.org
The Common Language Infrastructure (CLI) is the ECMA standard that
describes the core of the .NET Framework world. The Shared Source CLI is a a
working implementation of the ECMA CLI and the ECMA C# language specification.
This implementation is released under a shared source initiative. Please
see the accompanying license.
The Shared Source CLI goes beyond the printed specification of the ECMA
standards, providing a working implementation for CLI developers to explore and
understand. It will be of interest to academics and researchers wishing to teach
and explore modern programming language concepts, and to .NET developers
interested in how the technology works.
Features:
o An implementation of the runtime for the Common Language Infrastructure
(ECMA-335);
o Compilers that work with the Shared Source CLI for C# (ECMA-334) and JScript;
o Development tools for working with the Shared Source CLI such as
assembler/disassemblers (ilasm, ildasm), a debugger (cordbg), metadata
introspection (metainfo), and other utilities;
o The Platform Adaptation Layer (PAL) used to port the Shared Source CLI from
Windows XP to FreeBSD;
o Build environment tools (nmake, build, and others);
o Documentation for the implementation;
o Test suites used to verify the implementation.
WWW: http://msdn.microsoft.com/net/sscli/
This port does not need to be IGNOREd since it is already RESTRICTED.
However it is also broken since it doesn't respect PTHREAD_LIBS.
Since it is unmaintained and quite old, deprecate it with removal on
2006-12-01.
This port is scheduled for removal on Nov 7 2003 if it is still broken at
that time and no PRs have been submitted to fix it. If you are interested
in saving this port, please send your patches to the maintainer. If the
maintainer is unresponsive or the port has no maintainer, then please
submit them via send-pr.
Let be hohest: I really don't have a time now to properly maintain all
these great pieces of software, so that let others with more free time
to take over them.
Upgrade to 20021101 release (aka 1.0), which fixes compilation on
recent FreeBSD versions and allows to remove all of the gcc 3.x
fixes. sscli now supports Darwin/ppc, so that it might be possible
to port it to FreeBSD/ppc once it is available.
- Clean-up build system a bit;
- fix remaining two places where CFLAGS weren't respected;
- use cpio(1) to copy hierarchies instead of tar(1), so that it is possible
to build the port as ordinary user, but still have installed files be
owned by root;
- use slightly different solution for the problem with 777 permissions on
directories created during the build. Instead of harcoding resulting
prmission apply umask(2) to all mode arguments of [f]chmod() calls.
Since Rotor has no notion of file-level security anyway this should be
an optimal way to fix the problem.
Submitted by: Patrick Backlund <pbacklun@cc.hut.fi> (cpio fix)
sobomax (the rest)
Fix a silly permission bug, which results in a 777 permission all over the
WRKSRC. The problem was that when trying to map read-only FAT attribute into
*nix permission, MS assumed that if that attribute isn't set then write
permissions should be granted to everyone. Funny, eh?
Bump PORTREVISION.
Teach the creature how properly create shared libs on FreeBSD, so that
binaries linked to librotor_palrt.so no longer hardcode patch to a
specific location of librotor_palrt.so. Bump PORTREVISION.
Reported by: many
Add cli - Microsoft's Shared Source implementation if CLI ECMA standard
and C# language. Please note, that in order to build on -current you need
linker binary from -stable.
