unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: David Pirotte <david@altosw.be>
To: Olivier Dion via General Guile related discussions <guile-user@gnu.org>
Cc: Olivier Dion <olivier.dion@polymtl.ca>, wolf <wolf@wolfsden.cz>
Subject: Re: Recommended project structure
Date: Fri, 9 Jun 2023 16:33:56 -0300	[thread overview]
Message-ID: <20230609163356.4f20b96b@tintin> (raw)
In-Reply-To: <87cz24ehkt.fsf@laura>

[-- Attachment #1: Type: text/plain, Size: 552 bytes --]


> > That is pretty embarrassing mistake on my part, the link is:
> > https://www.erikedrosa.com/2017/10/29/guile-projects-with-autotools.html

Very good tutorial and project structure ... which you may 'complete'
looking at some existing project(s) you 'like' ...

Fwiw, guile-hall is another option, excellent as well - though I think
it won't cover everything you need if you have to write part of the
project code in C (hopefully not, but sometimes it is just
'inevitable'):

	https://gitlab.com/a-sassmannshausen/guile-hall/

David

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2023-06-09 19:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-08 22:43 Recommended project structure wolf
2023-06-09  3:33 ` Olivier Dion via General Guile related discussions
2023-06-09 12:55   ` wolf
2023-06-09 16:17     ` Olivier Dion via General Guile related discussions
2023-06-09 19:33       ` David Pirotte [this message]
2023-06-16 23:04         ` wolf
2023-06-09 16:41 ` Thompson, David
2023-06-09 18:40 ` Nala Ginrut

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230609163356.4f20b96b@tintin \
    --to=david@altosw.be \
    --cc=guile-user@gnu.org \
    --cc=olivier.dion@polymtl.ca \
    --cc=wolf@wolfsden.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).