On Wed, 5 Feb 2014 20:11:16 +0100 Peter Bex wrote:
> On Sat, Jan 25, 2014 at 10:36:43PM +0100, Peter Bex wrote:
>> I believe this patch does basically the correct thing, so here's a
>> signed-off copy. However, it breaks the Cygwin and MingW builds because
>> they have their own Makefile fragmen
On Sat, Jan 25, 2014 at 10:36:43PM +0100, Peter Bex wrote:
> I believe this patch does basically the correct thing, so here's a
> signed-off copy. However, it breaks the Cygwin and MingW builds because
> they have their own Makefile fragments for generating chicken-defaults.h
> and set CUSTOM_CHIC
On Fri, Jan 03, 2014 at 03:37:45PM +0100, Kristian Lein-Mathisen wrote:
> Hi folks,
>
> In the process of trying to ease the Android build cycle, I stumbled across
> sonames. I don't know what they are or what they do, but I know Android
> doesn't like them. In eval.scm, the binary version number
I think it means that binary-version is 0 is we don't have config.h:
https://github.com/chicken-mobile/chicken-core/blob/android-soname-fix-maybe/eval.scm#L45
does that help?
K.
On Fri, Jan 3, 2014 at 8:41 PM, Christian Kellermann wrote:
> * Kristian Lein-Mathisen [140103 15:38]:
> > (define
* Kristian Lein-Mathisen [140103 15:38]:
> (define dynamic-load-libraries
>(let ((ext
> - (if (and (memq (software-version) '(linux netbsd openbsd freebsd))
> - (not (zero? binary-version))) ; allow "configless" build
/--
Hi folks,
In the process of trying to ease the Android build cycle, I stumbled across
sonames. I don't know what they are or what they do, but I know Android
doesn't like them. In eval.scm, the binary version number is appended on
all linux software-versions, which includes Android.
This patch tr
