K-ballo changed the topic of #ste||ar to: STE||AR: Systems Technology, Emergent Parallelism, and Algorithm Research | stellar.cct.lsu.edu | HPX: A cure for performance impaired parallel applications | github.com/STEllAR-GROUP/hpx | Buildbot: http://rostam.cct.lsu.edu/ | Log: http://irclog.cct.lsu.edu/
<srinivasyadav227>
hkaiser: hi, did you find my proposal?
<hkaiser>
srinivasyadav227: have not looked today, sorry
<hkaiser>
will have omre time over the weekend
<srinivasyadav227>
ok sure np ;-)
hkaiser has quit [Quit: bye]
K-ballo has quit [Quit: K-ballo]
bita has quit [Ping timeout: 258 seconds]
jehelset has joined #ste||ar
K-ballo has joined #ste||ar
hkaiser has joined #ste||ar
hkaiser has quit [Quit: bye]
shubham has joined #ste||ar
hkaiser has joined #ste||ar
<gonidelis[m]>
Do we mention anywhere ninja in "How to build HPX"?
shubham has quit [Quit: Connection closed for inactivity]
<K-ballo>
that I don't know, but if we do then we should change all the outdated values
<gonidelis[m]>
K-ballo: on the docs?
<K-ballo>
everywhere
<gonidelis[m]>
ez
<K-ballo>
if this needs fixing in multiple places, makes little sense to fix them in just one
<gonidelis[m]>
it's easy to fix it in all places
jehelset has quit [Remote host closed the connection]
<gonidelis[m]>
i just compiled HPX with jemalloc and ninja like it was nothing
<gonidelis[m]>
K-ballo: if i want to create a cpp file that includes and uses both HPX and range-v3 should I have HPX and range-v3 compiled with the same dep. manager?
<K-ballo>
you need to build all three using compatible flags
<gonidelis[m]>
yeah all three
<gonidelis[m]>
compatible flags?
<K-ballo>
if a dependency manager is building those for you, you may not even know what those flags are
<K-ballo>
so the simple answer is yes, same dependency manager
<gonidelis[m]>
so it's better to build all three with the same dep. manager
<gonidelis[m]>
shit
<K-ballo>
not "better"
<gonidelis[m]>
can i skip the dep. manager?
<gonidelis[m]>
say for range-v3
<K-ballo>
sure
<K-ballo>
for all of them
<gonidelis[m]>
i don't expect the range-v3 to have many dependencies
<gonidelis[m]>
huh i dunno
<gonidelis[m]>
i don't even have to compile range-v3, lol