|
Fire is step THREE! | github.com/perl6/toolchain-bikeshed | Channel logs: irclog.perlgeek.de/perl6-toolchain/today | useful prior art: metacpan.org/pod/CPAN::Meta::Spec Set by moderator on 6 September 2016. |
|||
|
01:49
ilbot3 joined
|
|||
| moderator | Fire is step THREE! | github.com/perl6/toolchain-bikeshed | Channel logs: irclog.perlgeek.de/perl6-toolchain/today | useful prior art: metacpan.org/pod/CPAN::Meta::Spec | ||
|
06:11
domidumont joined
06:17
domidumont joined
07:42
leont_ joined
08:31
leont__ joined
|
|||
| nine | Just a random thought regarding generated Makefiles: as someone who can actually write Makefiles from scratch, I've always been bothered, when I need a fix in a Makefile, know how to do it but the whole thing was generated and I had no idea how to tell the generator what I need. | 09:58 | |
| DrForr | Do we leave breadcrumbs in the autogenerated files? | 10:02 | |
| nine | Well what little infrastructure we currently have doesn't generate Makefiles fully but only replaces variables in a Makefile.in. So we don't actually have the problem right now. | 10:04 | |
| Just thought, I should mention it for any future discussion about where we want to go. | |||
| Btw. it's basically the same issue as with ORMs and SQL. | |||
| DrForr | Yeah, tracing that stuff back can be a pain; I was just wondering idly if we left "Don't modify anything before this marker" type comments that would help. | 10:06 | |
| moritz | adding markers where stuff comes from shouldn't be too hard | 10:29 | |
| we have basically a preamble written by Configure.pl, a part from Makefile-common.in and one from Makefile-$backend.in | |||
| ugexe | maybe something that could be invoked like `run 'make', :env( from-json('.generated-build-env'.IO.slurp).hash );` | 14:00 | |
| or be able to generate a static makefile from something like that | 14:01 | ||
|
17:02
domidumont joined
17:06
leont__ joined
18:31
FROGGS joined
18:36
domidumont joined
20:07
lizmat joined
20:27
lizmat joined
21:13
leont__ joined
|
|||