unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Olivier Dion <olivier.dion@polymtl.ca>,
	Christine Lemmer-Webber <cwebber@dustycloud.org>,
	guile-user@gnu.org
Subject: Re: Newbie thoughts on Guile Hall + Guix
Date: Sun, 06 Feb 2022 23:32:45 +0100	[thread overview]
Message-ID: <2b524db8e0d851b4cb4519d9c82dca1585ade66f.camel@telenet.be> (raw)
In-Reply-To: <87a6f37isj.fsf@laura>

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

Olivier Dion schreef op zo 06-02-2022 om 17:05 [-0500]:
> > Is it restricted to Makefiles, or can it also be used without
> > generating Makefiles?  If not, things like progress bars should be
> > easy
> > to implement and file names containing spaces or ‘special
> > characters’
> > can be used without any problems.
> 
> Since it's glued to my project, and since I'm very familiar with
> Makefiles, it only support Makefiles for now.  What would be the
> other
> targets you have in mind?

I was thinking of something like

$ cd ~/the-source-code
# (I haven't looked much yet, possibly the CLI needs to be very
different)
$ cbuild make --target=aarch64-linux-gnu --prefix=/foo/bar
$ cbuild install --staged-install=/blah

Basically, don't delegate to 'make' or 'ninja' or whatever, just build
it.

That's way less portable than 'make' of course, but people that don't
have 'cbuild' or don't want to learn 'cbuild' can still use the
Makefile.

Seems like I'll have to make some changes to support cross-compilation
(basically, pass --target=aarch64-linux-gnu or the like to "guild
compile", and search for TARGET-gcc/clang instead of gcc/clang)
but otherwise looks mostly ok.

I noted that you are using #nil in some places.
#nil (an amalgation of #false and the empty list ()) is mostly an
implementation detail for Emacs Lisp support, and not something that
needs to be used in pure Guile.  I would use '() instead; it's
also more portable to other Schemes.

There's also some potential reproducibility problems: in
https://gitlab.com/oldiob/cbuild/-/blob/master/config.scm#L19,
D1CACHE_LINE_SIZE is set based on the cache size where it was
compiled, instead of the cache size where it is supposed to run on.

For now, I'll keep using the Autotools-based system (if it works, don't
break it :p, also doing other things at the moment than tweaking build
systems), but I'll keep cbuild in mind for the future.

Greetings,
Maxime.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  reply	other threads:[~2022-02-06 22:32 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-05 20:01 Newbie thoughts on Guile Hall + Guix Christine Lemmer-Webber
2022-02-05 22:15 ` Mikael Djurfeldt
2022-02-05 23:19   ` Jose Antonio Ortega Ruiz
2022-02-06 14:09     ` Ricardo Wurmus
2022-02-06  0:40   ` Christine Lemmer-Webber
2022-02-06  4:54     ` Aleix Conchillo Flaqué
2022-02-06 13:14       ` Mikael Djurfeldt
2022-02-06 14:03         ` Ricardo Wurmus
2022-02-06 14:28           ` Vijay Marupudi
2022-02-06 14:53             ` Ognen Duzlevski
2022-02-06 15:13               ` Maxime Devos
2022-02-06 15:29               ` Vijay Marupudi
2022-02-06 21:34                 ` Zelphir Kaltstahl
2022-02-07  2:11                   ` David Pirotte
2022-02-07  2:47                     ` David Pirotte
2022-02-07 19:21                     ` Zelphir Kaltstahl
2022-02-07 22:35                   ` adriano
2022-02-05 22:16 ` Vivien
2022-02-06  2:53 ` Zelphir Kaltstahl
2022-02-06 16:35 ` Olivier Dion via General Guile related discussions
2022-02-06 16:44   ` Vivien Kraus
2022-02-06 22:10     ` Olivier Dion via General Guile related discussions
2022-02-06 16:55   ` Maxime Devos
2022-02-06 22:05     ` Olivier Dion via General Guile related discussions
2022-02-06 22:32       ` Maxime Devos [this message]
2022-02-06 23:00         ` Olivier Dion via General Guile related discussions
2022-02-06 21:37   ` Zelphir Kaltstahl
2022-02-06 22:12     ` Olivier Dion via General Guile related discussions
  -- strict thread matches above, loose matches on Subject: below --
2022-02-06 13:40 dsmich
2022-02-08 12:19 Blake Shaw
2022-02-08 19:46 ` Chris Vine
2022-02-09  6:28 ` Catonano
2022-02-08 16:13 Blake Shaw
2022-02-09  3:23 Blake Shaw
2022-02-09 10:30 Blake Shaw
2022-02-09 14:13 ` Olivier Dion via General Guile related discussions
2022-02-09 20:05   ` Aleix Conchillo Flaqué
2022-02-09 20:28     ` Maxime Devos
2022-02-09 21:13       ` Aleix Conchillo Flaqué
2022-02-10 18:03     ` Vivien
2022-02-10 12:42 Blake Shaw

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=2b524db8e0d851b4cb4519d9c82dca1585ade66f.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=cwebber@dustycloud.org \
    --cc=guile-user@gnu.org \
    --cc=olivier.dion@polymtl.ca \
    /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).