From: Eric Wong <e@80x24.org>
To: spew@80x24.org
Subject: [PATCH 2/3] xap_helper_cxx: make the build process ccache-friendly
Date: Sat, 11 Nov 2023 23:35:11 +0000 [thread overview]
Message-ID: <20231111233512.1678903-2-e@80x24.org> (raw)
In-Reply-To: <20231111233512.1678903-1-e@80x24.org>
We need to have stable filenames and separate compilation
and linkage stages for ccache to hit.
---
lib/PublicInbox/XapHelperCxx.pm | 31 ++++++++++++++++++-------------
1 file changed, 18 insertions(+), 13 deletions(-)
diff --git a/lib/PublicInbox/XapHelperCxx.pm b/lib/PublicInbox/XapHelperCxx.pm
index 090ac9b7..88a83438 100644
--- a/lib/PublicInbox/XapHelperCxx.pm
+++ b/lib/PublicInbox/XapHelperCxx.pm
@@ -7,7 +7,7 @@
# The resulting executable is not linked to Perl in any way.
package PublicInbox::XapHelperCxx;
use v5.12;
-use PublicInbox::Spawn qw(run_qx which);
+use PublicInbox::Spawn qw(run_die run_qx which);
use PublicInbox::IO qw(read_all write_file);
use PublicInbox::Search;
use Fcntl qw(SEEK_SET);
@@ -24,8 +24,8 @@ my @pm_dep = map { $srcpfx.$_ } qw(Search.pm CodeSearch.pm);
my $ldflags = '-Wl,-O1';
$ldflags .= ' -Wl,--compress-debug-sections=zlib' if $^O ne 'openbsd';
my $xflags = ($ENV{CXXFLAGS} // '-Wall -ggdb3 -O0') . ' ' .
- ($ENV{LDFLAGS} // $ldflags) .
- qq{ -DTHREADID=}.PublicInbox::Search::THREADID;
+ qq{ -DTHREADID=}.PublicInbox::Search::THREADID . ' ' .
+ ($ENV{LDFLAGS} // $ldflags);
my $xap_modversion;
sub xap_cfg (@) {
@@ -58,12 +58,12 @@ sub build () {
die "mkdir($dir): $err" if !-d $dir;
}
use autodie;
- require File::Temp;
require PublicInbox::CodeSearch;
+ require PublicInbox::Lock;
+ require PublicInbox::OnDestroy;
my ($prog) = ($bin =~ m!/([^/]+)\z!);
- my $tmp = File::Temp->newdir(DIR => $dir) // die "newdir: $!";
- my $src = "$tmp/$prog.cpp";
- my $fh = write_file '>', $src;
+ my $lk = PublicInbox::Lock->new("$dir/$prog.lock")->lock_for_scope;
+ my $fh = write_file '>', "$dir/$prog.cpp";
for (@srcs) {
say $fh qq(# line 1 "$_");
open my $rfh, '<', $_;
@@ -73,6 +73,10 @@ sub build () {
print $fh PublicInbox::CodeSearch::generate_cxx();
close $fh;
+ opendir my $dh, '.';
+ my $restore = PublicInbox::OnDestroy->new(\&chdir, $dh);
+ chdir $dir;
+
# xap_modversion may be set by needs_rebuild
$xap_modversion //= xap_cfg('--modversion');
my $fl = xap_cfg(qw(--libs --cflags));
@@ -84,14 +88,15 @@ sub build () {
# distributed packages.
$^O eq 'netbsd' and $fl =~ s/(\A|[ \t])\-L([^ \t]+)([ \t]|\z)/
"$1-L$2 -Wl,-rpath=$2$3"/egsx;
-
- my $cmd = "$cxx $src $fl $xflags -o $tmp/$prog";
- system($cmd) and die "$cmd failed: \$?=$?";
- write_file '>', "$tmp/XFLAGS", $xflags, "\n";
- write_file '>', "$tmp/xap_modversion", $xap_modversion, "\n";
+ my @xflags = split(/\s+/, "$fl $xflags");
+ my @cflags = grep(!/\A-(?:Wl|l|L)/, @xflags);
+ run_die([$cxx, '-c', "$prog.cpp", @cflags]);
+ run_die([$cxx, '-o', "$prog.tmp", "$prog.o", @xflags]);
+ write_file '>', 'XFLAGS.tmp', $xflags, "\n";
+ write_file '>', 'xap_modversion.tmp', $xap_modversion, "\n";
undef $xap_modversion; # do we ever build() twice?
# not quite atomic, but close enough :P
- rename("$tmp/$_", "$dir/$_") for ($prog, qw(XFLAGS xap_modversion));
+ rename("$_.tmp", $_) for ($prog, qw(XFLAGS xap_modversion));
}
sub check_build () {
next prev parent reply other threads:[~2023-11-11 23:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-11 23:35 [PATCH 1/3] xap_helper_cxx: use write_file helper Eric Wong
2023-11-11 23:35 ` Eric Wong [this message]
2023-11-11 23:35 ` [PATCH 3/3] xap_client: spawn C++ xap_helper directly Eric Wong
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 \
--in-reply-to=20231111233512.1678903-2-e@80x24.org \
--to=e@80x24.org \
--cc=spew@80x24.org \
/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).