nikunj has quit [Remote host closed the connection]
Yorlik has joined #ste||ar
daissgr has joined #ste||ar
hkaiser has joined #ste||ar
eschnett has quit [Quit: eschnett]
eschnett has joined #ste||ar
<Yorlik>
Finally falling back to HPX 1.3.0 and VS 2017 fixed it for now.
<hkaiser>
Yorlik: does stable work with VS2017?
<Yorlik>
I had issues with stable
<Yorlik>
I'll give it another shot, it compiled, but the using app broke
<Yorlik>
HPX probably is too sophisticated for cl
<hkaiser>
nah
<hkaiser>
cl is too braindead to compile C++
<Yorlik>
So it's neither a C nor a C++ compiler - rather a cl compiler ;)
<Yorlik>
Means: We need Clang work
<Yorlik>
And Bosst is a royal pain inthe assets here.
<Yorlik>
Boost.
<hkaiser>
my theory is that they have a (secret) database of patterns somewhere hidden that is used to match the code to compile in order to find the proper binary ;-)
<Yorlik>
ROFL
<Yorlik>
Cl is a hashtable lookup and when you have hash collisions stuff blows up ;)
<Yorlik>
So - we need an official recommended and supported way to build HPX on Windows .. With an idiot proof recipe. Not just "Use vcpkg for everything".
<hkaiser>
Yorlik: vcpkg is idiot-proof, I think
<Yorlik>
Well - it broke for me - so - make it Yorlik proof :)
<hkaiser>
Yorlik: no idea what you were doing
<hkaiser>
for me it's as simple as described in the docs :/
<Yorlik>
I can compile HPX, but by app using it breaks