On Wed, Aug 29, 2018 at 4:21 PM wrote:
> I don't see the motivation for installing files outside of the chicken
> installation
> tree, so it is not clear to me what you want to achieve with this.
>
>From what I understand (which may be wrong) it's so that chicken-install
can put a
file in a
> Additionally I propose that the (destination ...) form should be made
> relative to the default target directory and create all specified
> subdirectories as necessary, then I could just add a
>
> (destination "../extend/protobuf")
>
> to the c-include form above and be happy.
I don't see
On Wed, 29 Aug 2018 14:17:08 +0200 felix.winkelm...@bevuta.com wrote:
> > [...]
> > I can't say that I like this design decision, but I guess I'll have to
> > live with it. If this is unsupported, it also feels strange that
> > the .egg format allows specification of multiple import libraries per
On Wed, 29 Aug 2018 14:09:01 +0200 felix.winkelm...@bevuta.com wrote:
> > [...]
> > multiple sets of files may already be possible with multiple component
> > forms in the .egg, but installation into any nested subdirectories relative
> > to the CHICKEN installation prefix is currently not
>
> I can't say that I like this design decision, but I guess I'll have to
> live with it. If this is unsupported, it also feels strange that
> the .egg format allows specification of multiple import libraries per
> extension at all – the provider side of the picture, when you write a
> library
> Hello,
>
> multiple sets of files may already be possible with multiple component forms
> in the .egg, but installation into any nested subdirectories relative to the
> CHICKEN installation prefix is currently not possible.
>
> For example, some include files provided with the protocol
On Wed, 29 Aug 2018 10:57:54 +0200 felix.winkelm...@bevuta.com wrote:
> > As far as I understand the question (probably not really), a simple way to
> > do this is to (foreign-declare "#include \"foo.c\"") and add foo.h to the
> > source-dependencies of the file (see for example the simple-sha1
On Tue, 28 Aug 2018 20:40:33 +0200 felix.winkelm...@bevuta.com wrote:
> [...]
> I'll try to address some of your questions.
> [...]
Hello,
thanks for taking the time to reply :-)
> [...]
> > - Some eggs install one extension library containing several modules. The
> > new
> > CHICKEN module
Hello,
multiple sets of files may already be possible with multiple component forms in
the .egg, but installation into any nested subdirectories relative to the
CHICKEN installation prefix is currently not possible.
For example, some include files provided with the protocol buffers egg would
> On Wed, Aug 29, 2018 at 10:57:54AM +0200, felix.winkelm...@bevuta.com wrote:
> > The foreign-declare case is simple and straightforward and should
> > be used, if possible, but we need a fallback solution and this case
> > of a separate .c file is common enough to be addressed.
>
> For 5.0?
>
On Wed, Aug 29, 2018 at 10:57:54AM +0200, felix.winkelm...@bevuta.com wrote:
> The foreign-declare case is simple and straightforward and should
> be used, if possible, but we need a fallback solution and this case
> of a separate .c file is common enough to be addressed.
For 5.0?
Cheers,
Peter
> As far as I understand the question (probably not really), a simple way to
> do this is to (foreign-declare "#include \"foo.c\"") and add foo.h to the
> source-dependencies of the file (see for example the simple-sha1 and
> simple-md5 eggs, they do this). No need for any special handling.
>
>
On Tue, Aug 28, 2018 at 08:40:33PM +0200, felix.winkelm...@bevuta.com wrote:
> > - How can I compile multiple source files, for example one scheme file and
> > several C files, into an extension library in an .egg file? As far as I can
> > see, the only way to do that is a custom build script,
13 matches
Mail list logo
