<maker>
but there's no target run on my makefile, generated with env NET=socket mirage configure --unix
<maker>
where shall I dig to find how mirage generates makefile targets?
mort___ has quit [Quit: Leaving.]
<maker>
(It's more of a question to understand the internals)
<maker>
((but yeah, perhaps it's also a bug))
lobo has joined #mirage
mort___ has joined #mirage
mort___ has quit [Quit: Leaving.]
mort___ has joined #mirage
mort___ has quit [Quit: Leaving.]
mort___ has joined #mirage
mort___ has joined #mirage
<Drup>
erk, another piece of readme that I forgot to update ..
<Drup>
maker: did you follow the hello world tutorial ?
<maker>
yes
<maker>
I may have done something wrong though
<maker>
(read: maker did not double-check what he was doing)
* maker
rtfm to find the information about makefile targets
<Drup>
well, about makefile targets, it's quite simple
<Drup>
do mirage configure, open the makefile
<Drup>
:D
* aggelos_
is relieved that the replacement fan for his laptop arrived in time for the hackathon
<aggelos_>
not least b/c this laptop has been reliably running qubes for a couple of years now
<aggelos_>
borrowed laptops can be awkward
<maker>
Drup: the question was about how the makefile is generated
lars_kurth_alt has joined #mirage
lars_kurth_alt has quit [Ping timeout: 252 seconds]
mort___ has quit [Quit: Leaving.]
mort___ has joined #mirage
mort___ has quit [Ping timeout: 252 seconds]
<Drup>
maker: right, so first stem is to read the functoria blog post
<Drup>
then you can look inside mirage.ml
<Drup>
It's a bit messy, tbh
<hannes>
I think the run target was deprecated some time ago... seems like some documentation didn't get updated... after make, a main.native should be around which you can invoke
<Drup>
Lot's of documentation scatered everywhere, it was hard to find all of it ...
<Drup>
hannes: You should take a documentation day during the hackaton :3