[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Does guile have serious win32 ambition?
From: |
stefan |
Subject: |
Re: Does guile have serious win32 ambition? |
Date: |
Fri, 2 Nov 2001 00:18:26 +0100 (CET) |
On Thu, 1 Nov 2001, Thien-Thi Nguyen wrote:
> also, see libguile/scmconfig.h.in for current practice.
>
> in another mail, you noted that some of the __FOO__ cpp symbols are
> required for building. that's fine. all we need to do now is distill
> the smallest (yet most flexible) number of top-level HAVE_* symbols, and
> use those to conditionalize definition of the __FOO__ stuff.
Ok. I rearranged the macros a bit. At configure time a macro
USE_DLL_IMPORT gets defined in `scmconfig.h'. This will cause the
definition of the __FOO__ macros (here: __READLINE_IMPORT__,
__REGEX_IMPORT__ and __CRYPT_IMPORT__) in the file `__scm.h'.
All other macros (here: __FOOBAR__) have been replaced to:
SCM_IMPORT
SCM_EXPORT
SCM_RL_IMPORT
SCM_RL_EXPORT
SCM_SRFI4_IMPORT
SCM_SRFI4_EXPORT
SCM_SRFI1314_IMPORT
SCM_SRFI1314_EXPORT
Is this a style you all could cope with? I made the changes locally on my
machine and could resend the whole patch. Before this I would generally
like to know if you are really planning to put the changes into CVS or
not.
Cheers,
address@hidden