liberty-eiffel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Liberty-eiffel] Liberty-eiffel Digest, Vol 26, Issue 3 - here: reas


From: Bernd Schoeller
Subject: Re: [Liberty-eiffel] Liberty-eiffel Digest, Vol 26, Issue 3 - here: reasoning for using Pelles-C on Windows
Date: Tue, 8 Mar 2016 07:37:14 +0000
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.6.0

On 07/03/16 11:53, Hans Zwakenberg | Ocean Consulting GmbH wrote:
Hi Rahpa, Bernd et al,
Pelles-C is free, free as in 'free speech' AND as in 'free beer'... ;)

No, it is free as 'free beer', but not as in 'free speech' - if it would be, you would have the source, and you would be allowed to change the source, and you would be allowed to distribute your changes.

Also, you are not allowed to charge money for it. So, it will never be possible to distribute it on Magazine DVDs or similar. That is quite a heavy restriction if you think about it. All real open source code can be distributed for a fee.

http://www.gnu.org/philosophy/free-sw.en.html

As to compiler integration:  other compilers are available:  CLANG/LLVM,
Code::Blocks and the ones previously mentioned.  Also, in the past we
discussed integrating Tiny-C as well, more specifically to get faster
edit-compile-test turnarounds.  The idea was to use Tiny-C for
development and any of the others (to be implemented) for deployment...
Using MinGW/MSYS would keep it closer to the Linux counterpart and hence
reduce integration effort, but I don't know enough about it
(license-wise, deployment-wise) to be able to choose/decide between them...

Having looked a second time, I really would recommend to start by using MinGW. While there has not been an official release for 3 years, it seems to be reasonably well maintained. And, as it is the compiler that Liberty Eiffel normally uses, you will run into much less problems.

That is only my 5cc - your choice.

Bernd




reply via email to

[Prev in Thread] Current Thread [Next in Thread]