Philipp, thank you for the explanation.
I propose to create a non-free (or something like that) directory at the
same level as include and lib are, and put all anon-free header files
and libraries there, retaining the same structure:
lib/pic/*.lib: free pic libraries
include/pic/*.h: free pic header files
non-free/lib/pic/*.lib: non free pic libraries
non-free/include/pic/*.h: non free pic header files
This is makes life easy for the package maintainers: just put the
contents of the non-free directory in a separate package.
Developers should add additional paths to the sdcc command line: -I
/usr/local/sdcc/non-free/include/pic -L /usr/local/sdcc/non-free/lib/pic
We could also introduce a sdcc command line option, for exeample
--non-free, to tell sdcc to automatically search header and library
files also in the non-free directory.
On 09/22/2010 11:20 PM, Philipp Klaus Krause wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> Am 22.09.2010 22:57, schrieb Borut Razem:
>> so you are 100% sure that the "only to be used with authentic Microchip
>> devices" requirement is not GPL compatible?
> I rarely hurts to re-read the GPL. However AFAIK adding additional
> restrictions to the GPL is always GPL-incompatible, unless explicitly
> allowed by the GPL (e.g. AGPL conversion clause in GPL v3).
> Outside of the GPL world it would violate e.g. clause 6 of the Debian
> Free Software guidelines (DFSG), and thus not be allowed into Debian
> main (and since Debian considers the GPL to be DFSG-free, this means
> Debian considers the restriction GPL-incompatible).
> But without looking at the legal texts, the restriction would be against
> the spirit of free software, and freedom in general.
> There are PIC clones not made by microchip. There even are free
> implementations of the PIC architecture, some of them compatible with
> specific PIC devices, such as the 16C55 or 16F84.
> It would be absurd if free sdcc could not legally generate code for
> certain chips depending on who manuifactured the hardware. Most absurd,
> if sdcc could not legally generate code for free hardware compatible
> with Microchip's PICs.
> ²A few minutes of search found three free PIC implementations:
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
> -----END PGP SIGNATURE-----
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment and
> accelerate your shift to cloud computing.
> sdcc-devel mailing list