From: Karl Dahlke <email@example.com> To: firstname.lastname@example.org Subject: [edbrowse-dev] quick js Date: Sun, 07 Mar 2021 11:44:38 -0500 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> [-- Attachment #1: Type: text/plain, Size: 1041 bytes --] Chris: If you could help with a robust, portable makefile, that would be great. Start with GNUmakefile as template, and the same environment variables I guess, they seem to work for us. Cept, we want edbrowse target to use quick, and still keep an edbrowseduk target to use duktape. I guess we can keep edbrowsesm to build with spider monkey, though that one doesn't build at present, but that's my problem, not yours. I'd let hello build the hello targets, I think that's ok. Nobody but us is ever going to make any of these nonstandard targets. As per cmake I don't know the answer to that one. When the dust settles I'll ask Geoff - but I didn't want to bother him til we had a clear path. I could have pestered him about building with spider monkey a few months ago; I'm glad I didn't. Let's make sure we really know where we're headed first. Also - how would this change your procedures for static builds. Probably simplify them, since quickjs.a is already static. And tidy builds a statid library too. Karl Dahlke
next prev parent reply other threads:[~2021-03-07 16:45 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-07 13:26 Karl Dahlke 2021-03-07 16:15 ` Chris Brannon 2021-03-07 16:44 ` Karl Dahlke [this message] 2021-03-07 17:15 ` Chris Brannon 2021-03-07 18:40 ` Geoff McLane 2021-03-07 19:27 ` Karl Dahlke 2021-03-07 19:37 ` Chris Brannon 2021-03-08 8:46 ` Karl Dahlke 2021-03-08 19:31 ` Geoff McLane 2021-03-08 21:18 ` Karl Dahlke 2021-03-09 10:23 ` Kevin Carhart 2021-03-09 14:37 ` Geoff McLane 2021-03-09 22:52 ` Kevin Carhart [not found] ` <email@example.com> 2021-03-14 20:36 ` Geoff McLane 2021-03-15 9:44 ` Kevin Carhart
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 * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [edbrowse-dev] quick js' \ /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
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 NNTP newsgroup(s).