hkaiser changed the topic of #ste||ar to: The topic is '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/
K-ballo has quit [Quit: K-ballo]
K-ballo has joined #ste||ar
hkaiser has joined #ste||ar
simbergm has joined #ste||ar
<K-ballo> I'll fork boost::lexical_cast
<hkaiser> K-ballo: into hpx? create a module?
<K-ballo> yes
<hkaiser> nice, might allow for a major cleanup
<K-ballo> should I clang-format all the files?
hkaiser has quit [Ping timeout: 260 seconds]
hkaiser has joined #ste||ar
<K-ballo> how to handle cycles in modules?
<K-ballo> my #includes don't work.. do I need to do anything besides adding the module as a dependency?
<hkaiser> K-ballo: no, just add dependent modules in cmake
<hkaiser> however modules should not have cycles
<hkaiser> that's the whole idea
<K-ballo> yeah, but some modules are... interesting, let's say.. errors, for instance?
<K-ballo> anyways, I cut the cycle already
<hkaiser> we have added some callback registration to resolve cycles
<K-ballo> the global header is the one I cannot include from dependencies
<hkaiser> pls elaborate, not sure I understand
<K-ballo> the one generated by GLOBAL_HEADER_GEN
<hkaiser> ok, what is with it?
<K-ballo> I can include "normal" headers once I set up the dependency, but not the "global" header
<hkaiser> (you don't have to generate it btw, if it's not needed)
<hkaiser> hmmm
<hkaiser> so other modules don't findthe generated header?
<K-ballo> oh I'm using the wrong path
<K-ballo> it's hpx/{module_name}.hpp
<hkaiser> yes
<K-ballo> what could lead to an empty cmake HPX_CXX_STANDARD?
hkaiser has quit [Quit: bye]
<simbergm> it's not set on windows when the standard is auto-detected (i.e. just use whatever msvc has to offer, we don't actually detect what's available)
<K-ballo> no it's not, it's on release
<simbergm> K-ballo: yes, brain fart, I meant release
<simbergm> that was supposed to go into master before christmas with the release, but we can cherry pick that back into master if you'd like
<K-ballo> I'm in no rush personally
<simbergm> the check'll go away completely with the c++14 branch though
<simbergm> you can also safely ignore that test for now
<K-ballo> is the switch to 14 the first thing after the release?
<simbergm> K-ballo pretty much unless someone objects