Re: [sdcc-devel] [Sdcc-user] SDCC 3.4.0 RC2 created

[Philipp K. K. <pk...@sp...>]

On 31.03.2014 00:25, Raphael Neider wrote:
> Hi,
> 
> apparently I just have to find a way to not build the pic14/16 device
> libraries if configure (of the top sdcc project) is called with
> --disable-non-free. I will look into that on Monday evening and report
> my status late Monday evening. We will then see if we already have a
> solution or how long it would probably take to get one. We shall then
> decide how to proceed.
> 
> Update: As Gudjon had no problems with 3.3, changes to the PIC
> libraries/build system may not be required - there are no changes in how
> the PICs use/depend on non-free, were there?!?
> The code generators for the PICs should be usable (when omitting the
> --use-non-free sdcc command line option) - with access to the free
> libraries (libc18f, libm18f, libsdcc), albeit without the device-
> specific headers and libraries and without the I/O libs, which depend on
> the device libs.
> I need to check if the symbols (register names) required by the
> generated code are available even if the device libraries are not
> included. If we need replacement libraries to provide the common subset
> of register symbols, this change will definitely not be available for
> this release. I'll check that and report my findings.
> 
> @Gudjon: Can you briefly explain, how sdcc 3.3 was simple to package?
> What changed towards 3.4 to make packaging the free (i.e., removing the
> non-free parts) harder?
> I assume that you delete the non-free directories (especially
> device/non-free) before configuring and building. I further assume that
> you pass --disable-pic14 and --disable-pic16 to make that work with 3.3,
> and that this approach now fails with 3.4 because compilation of some
> other component (which one? another backend?) fails after removing non-free?
> What would you require/request?
> Since there was no change w.r.t. the PIC stuff (was there?), maybe
> whatever Philipp already did suffices?
> 
> @Philipp: Could you briefly explain what you did in this matter?
> Are you aware of any non-PIC backend having non-free parts/dependencies
> there?

AFAIK, no non-pic has any non-free stuff.

> Have you already removed/replaced/stubbed them when --disable-non-free
> is given?

I tried to change configure.in and Makefile.in (attached). Since the
changes didn't work as intended, I didn't commit anything.

Philipp

P.S.:

IMO, sdcc should build with --disable-non-free when the device/non-free
directory isn't even there.