hkaiser 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/
jaafar has quit [Ping timeout: 250 seconds]
hkaiser has quit [Quit: bye]
eschnett has quit [Quit: eschnett]
eschnett has joined #ste||ar
K-ballo has quit [Quit: K-ballo]
jaafar has joined #ste||ar
nikunj97 has joined #ste||ar
jaafar has quit [Ping timeout: 250 seconds]
nikunj97 has quit [Quit: Bye]
K-ballo has joined #ste||ar
brjsp has joined #ste||ar
brjsp has quit [Quit: Page closed]
hkaiser has joined #ste||ar
daissgr has joined #ste||ar
nikunj has joined #ste||ar
<K-ballo>
why can't phylanx use debug HPX when building debug and release HPX when building release?
<K-ballo>
is that a limitation with phylanx or with HPX itself?
<K-ballo>
maybe I'm reading too much on the build instructions?
<hkaiser>
K-ballo: the build types must match
<hkaiser>
is that what you're asking?
<hkaiser>
might be that the build type is not automatically propagated, though :/
<K-ballo>
maybe it does.. let me try
<K-ballo>
I expect to be able to pick phylanx in whatever configuration it offers and to have it pick the right hpx build each time
<K-ballo>
both phylanx and hpx are multiconfiguration cmake projects (no CMAKE_BUILD_TYPE involved)
<hkaiser>
yah, I don't think it's doing that
<hkaiser>
well, on Windows it does, I think
<K-ballo>
that's good, I'm on windows
<K-ballo>
once CMAKE_BUILD_TYPE is involved that flow can't work anymore
<hkaiser>
what I noticed is that vcpkg has the problem, that you need to configure hpx with CMAKE_BUILD_TYPE=Debug for it to pick up all configurations correctly
<K-ballo>
odd, vcpkg should not depend on CMAKE_BUILD_TYPE
<hkaiser>
right
<hkaiser>
could be my local setup being flawed, never bothered to investigate
<K-ballo>
unless it's a vcpkg limitation that it can only work with single configuration generators
<hkaiser>
no
<hkaiser>
it's not that
<hkaiser>
for me, if build type is not set, then it generates a multi-conf project, but all dependencies are release
<hkaiser>
if I set the build type explicitly, everything works as needed
<K-ballo>
ok, so it's a design decision that release is abi stable or something
<hkaiser>
could be
<K-ballo>
I'm seeing a bad_alloc from within std::string while processing command line arguments
<K-ballo>
so if vcpkg mixed release boost with debug std::, specially for msvc, that'd be bad right?
<K-ballo>
and if I truly want a debug phylanx I'm going to have to have a separate build and force the build type to debug and rebuild the world.. that it?
<hkaiser>
K-ballo: yah, you shouldn't mix debug/release
<hkaiser>
K-ballo: yes, you need debug boost, debug hpx and debug phylanx
<K-ballo>
this vcpkg makes dealing with boost more complex than usual, not less...
<hkaiser>
K-ballo: hmm, I think it's nice as installing everything is a one liner
<hkaiser>
it works flawlessly for me, sans for the need to explicitly set the cmake build type for hpx to Debug
<K-ballo>
it forces me to go back to the dark ages of single configuration projects
<hkaiser>
then I get proper multi-conf projects
<hkaiser>
no it doesn
<hkaiser>
t
<hkaiser>
you still get proper multi-conf projects
<K-ballo>
I don't, it's mixing release boost with debug hpx
<hkaiser>
K-ballo: only if you configured without setting the build type
<hkaiser>
it's a bug in vcpkg, I believe
<K-ballo>
are you suggesting if I do set the build type to something, anything, then it will support multi-config correctly?
<K-ballo>
as opposed to, say, simply use debug dependencies for all configurations
<hkaiser>
yes, that's what I'm trying to say
<hkaiser>
I know it works properly when the build type is set to debug
<hkaiser>
not sure if any other value would do the trick as well
<K-ballo>
that's..... odd
<K-ballo>
ok, I can give that a try
<hkaiser>
ndeed
<K-ballo>
so I guess it will build each dependency for all four configuations?
<K-ballo>
I just want two, I'd rather not have it build 4 in advance
<K-ballo>
I suspect boost autolinking might somehow be involved in this, it always is
<hkaiser>
K-ballo: no it will build only the configurations you need
<K-ballo>
how would it know which ones I need?
<hkaiser>
you seletc it in VS
<K-ballo>
yeah but vcpkg builds dependencies way before that
<hkaiser>
ahh
<hkaiser>
vcpkg builds Debug and Release only
<K-ballo>
I'm only seeing one flavor of each boost library being built
<K-ballo>
release, I suppose.. but there's a pdb next to each
<hkaiser>
K-ballo: hmmm, it builds both for me
<hkaiser>
they end up in different directories, though
<K-ballo>
aha! there's a separate debug directory
jaafar has joined #ste||ar
<K-ballo>
about to finish building debug/release pairs now
<K-ballo>
should I expect the generated vs project to just work if I run the examples?
<K-ballo>
I understand there's certain working directory considerations and stuff
<K-ballo>
seems to be working
daissgr has quit [Quit: WeeChat 1.9.1]
<K-ballo>
suddenly getting a missing entry point, after switching to more recent sources
<K-ballo>
release build is looking for Debug/bin/_phylanxd.cp36-win_amd64.pyd for some reason