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/ | GSoC2018: https://wp.me/p4pxJf-k1
kisaacs has joined #ste||ar
diehlpk has quit [Ping timeout: 255 seconds]
nikunj97 has quit [Quit: Leaving]
kisaacs has quit [Ping timeout: 240 seconds]
parsa has quit [Quit: Zzzzzzzzzzzz]
kisaacs has joined #ste||ar
hkaiser has quit [Quit: bye]
parsa has joined #ste||ar
stmatengss has joined #ste||ar
stmatengss has quit [Quit: Leaving.]
stmatengss has joined #ste||ar
stmatengss has quit [Client Quit]
K-ballo has quit [Quit: K-ballo]
galabc has joined #ste||ar
stmatengss has joined #ste||ar
galabc has quit [Client Quit]
kisaacs has quit [Ping timeout: 260 seconds]
parsa has quit [Remote host closed the connection]
parsa has joined #ste||ar
stmatengss has quit [Quit: Leaving.]
kisaacs has joined #ste||ar
parsa has quit [Quit: Zzzzzzzzzzzz]
kisaacs has quit [Ping timeout: 260 seconds]
aparikh756 has joined #ste||ar
aparikh756 has quit [Ping timeout: 260 seconds]
david_pfander has joined #ste||ar
david_pfander has quit [Ping timeout: 248 seconds]
david_pfander has joined #ste||ar
aparikh756 has joined #ste||ar
david_pfander has quit [Ping timeout: 240 seconds]
<github> [hpx] StellarBot pushed 1 new commit to gh-pages: https://git.io/vppHF
<github> hpx/gh-pages 480f359 StellarBot: Updating docs
kisaacs has joined #ste||ar
kisaacs has quit [Ping timeout: 256 seconds]
nikunj has joined #ste||ar
<nikunj> so, I was able to build hpx using msvc (all builds passed, none failed). However when I try to run one of the examples directly from bin folder, it cannot find boost related dll.
nikunj97 has joined #ste||ar
nikunj has quit [Read error: Connection reset by peer]
nikunj1997 has joined #ste||ar
nikunj97 has quit [Read error: Connection reset by peer]
nikunj97 has joined #ste||ar
nikunj1997 has quit [Read error: Connection reset by peer]
nikunj1997 has joined #ste||ar
nikunj97 has quit [Read error: Connection reset by peer]
nikunj97 has joined #ste||ar
nikunj1997 has quit [Read error: Connection reset by peer]
nikunj97 has quit [Remote host closed the connection]
nikunj97 has joined #ste||ar
nikunj97 has quit [Quit: Leaving]
nikunj97 has joined #ste||ar
kisaacs has joined #ste||ar
kisaacs has quit [Ping timeout: 256 seconds]
Anushi1998 has quit [Ping timeout: 255 seconds]
Anushi1998 has joined #ste||ar
<zao> nikunj97: Windows uses PATH to find dynamic libraries.
<zao> The HPX CI does things like set PATH="C:\vcpkg\boost\bin:%PATH%"
<nikunj97> zao: so i need to set path to make it work?
<zao> Or copy in the DLLs into the current directory or executable directory.
<zao> Or technically, do something naughty with manifests, but I have no idea how those work anymore :)
<nikunj97> ok, so it was a normal behavior to not work
<nikunj97> also, can msvc build a hpx application if provided with headers and linkers?
<nikunj97> mine doesn't seem to work
<nikunj97> ah, thanks!
<zao> As for using MSVC to build an external application? Heaven knows.
<nikunj97> zao: so I should create cmakelists instead and build it in msvc?
<zao> It'd probably be a good thing to try.
<nikunj97> zao: thanks! can I run hpx applications without using visual studio?
<zao> I would say that we have two more or less "supported" ways of using HPX, pkg-config (on non-MSVC) and the CMake bits.
<zao> If you know what you're doing, it's quite possible to link HPX directly in a MSVC solution's projects. I've done it in the past.
<nikunj97> zao: will that build the solution without any problem?
<zao> So you'd set -DHPX_DIR=C:\libs\hpx\lib\cmake\HPX and find_package(HPX) or something.
<zao> What problems are you running into?
<zao> I haven't played with this for years :)
<nikunj97> I had linking errors
<nikunj97> even though I provided with correct linker paths
<nikunj97> So I manually added header and linker paths for boost, hwloc and hpx
<nikunj97> and tried to build it
<nikunj97> but it still didn't build
<zao> So what errors did you get?
hkaiser has joined #ste||ar
<zao> Missing libraries, missing symbols, duplicate symbols, something else?
<nikunj97> I could share the exact linker error, but i'm currently on my linux pc and can't create a gist of windows errors
<zao> Ah.
<nikunj97> it was related to target machines being x86
<nikunj97> and linking error for boost
<zao> Make sure that you're linking libraries of the correct bitness matching your project.
<nikunj97> hpx recommends it's use for x64 right?
<zao> I believe the default for VC++ projects still is 32-bit, and you really should use 64-bit for HPX.
<nikunj97> iirc i read it in the docs somewhere
<zao> Unless you're really insane like me :D
<zao> hkaiser promises nothing if you're foolish enough to target 32-bit x86 :)
<nikunj97> zao: exactly so my build should target x64 right?
<zao> So you'd install 64-bit Boost binaries, 64-bit hwloc, build HPX with «-G "Visual Studio 15 2017" -A x64»
<nikunj97> zao: i see, I did change it to x64 later but still it did run into a few linker issues. I'll share the gist when I run windows
<zao> (or -G "Visual Studio 15 2017 Win64", same thing but in an older generator format.
<zao> No hurry, just wanted to investigate a bit :)
<nikunj97> zao: is it a cmake parameter?
<zao> Yeah, those are CMake params.
<zao> If you just use the "Visual Studio 15 2017" generator, you get a 32-bit project, at least historically.
<nikunj97> zao: ok then I'll rebuild hpx with those parameters and try again today
<zao> In the past, there was a separate "Visual Studio 15 2017 Win64" generator.
<nikunj97> I used visual studio 15win64 to configure the project
<zao> In more recent CMake, there's an architecture knob, -A
<zao> Ah, great.
<nikunj97> zao: so my build was correct?
<zao> Probably. Hard to tell at a distance.
<zao> My guess is that your VC++ project was x86 (32-bit).
<nikunj97> zao: you mean the solution it created after generation?
<zao> No, not the HPX solution.
<nikunj97> or the external project I was working on
<nikunj97> i see
<zao> The application one you were trying to use HPX in.
<nikunj97> zao: is it a good idea to actually use the hpx solution and add source file to build (pseudo)external projects
<zao> For a third party program that merely uses HPX, I would not try to nestle in its build into HPX's tree.
<zao> For something that eventually will be a test or example, sure, do it.
<nikunj97> zao: yes, I intend to try hooking with msvc
<zao> I would separately build HPX, pull in the exported CMake bits from HPX, and build my code separately.
<nikunj97> I identified the required functions, but i couldn't experiment due to these unexpected errors
<nikunj97> zao: i didn't understand what you said, could you please elaborate
<zao> I mean that if I was writing a freestanding program that would use HPX, I would build HPX first and install it.
<zao> And then just find_package(HPX) and add_hpx_executable() or however one actually uses HPX.
<nikunj97> zao: oh so you mean, use cmakelists to generate solutions and then building them
<nikunj97> is that what you mean?
<zao> Aye.
<nikunj97> zao: ya, I was thinking of the same
<nikunj97> zao: thanks for the help :)
<nikunj97> zao: I'll update you later with the exact errors
<nikunj97> hkaiser: yt?
<zao> And yes, if you need actual meaningful guidance, ask your mentor :P
K-ballo has joined #ste||ar
<hkaiser> here
<nikunj97> hkaiser: did you look into my code?
<hkaiser> no :/
<hkaiser> planning to do that this weekend
<nikunj97> ok, please let me know how can i refine my code after checking out the code
<nikunj97> i will then create a pull request for working linux/unix code, or should i wait until we do everything with perfection?
<hkaiser> ok
aparikh756 has quit [Ping timeout: 260 seconds]
parsa has joined #ste||ar
nikunj97 has quit [Quit: Leaving]
nikunj has joined #ste||ar
nikunj has quit [Remote host closed the connection]
nikunj has joined #ste||ar
elfring has joined #ste||ar
aparikh756 has joined #ste||ar
<github> [hpx] K-ballo force-pushed logging from 4ad11f6 to 6c95363: https://git.io/vx6Yc
<github> hpx/logging 6c95363 Agustin K-ballo Berge: pruning util/logging
kisaacs has joined #ste||ar
<github> [hpx] taeguk opened pull request #3324: Replace C++14 overload of std::equal with C++11 code. (master...tg_std_equal) https://git.io/vphJw
parsa has quit [Quit: Zzzzzzzzzzzz]
anushi has joined #ste||ar
mcopik has joined #ste||ar
taeguk has joined #ste||ar
taeguk has quit [Quit: Page closed]
kisaacs has quit [Ping timeout: 240 seconds]
kisaacs has joined #ste||ar
anushi has quit [Ping timeout: 256 seconds]
anushi has joined #ste||ar
jaafar has quit [Ping timeout: 256 seconds]
nanashi64 has joined #ste||ar
nanashi55 has quit [Ping timeout: 264 seconds]
nanashi64 is now known as nanashi55
hkaiser has quit [Quit: bye]
jaafar has joined #ste||ar
kisaacs has quit [Ping timeout: 240 seconds]
<nikunj> zao: yt?
<zao> Kind of, nursing a cup of tea trying to combat my cold.
<nikunj> it was an unresolved external symbol issue
<nikunj> with x64 debug
<zao> Note that the symbol names imply that it's trying to find symbols from a dynamic library import library.
<zao> Are you linking the correct `.lib` file?
<nikunj> yes i've included correct linker paths
<nikunj> i've linked with hwloc\lib, hpx\lib and boost\lib
<zao> So what actual library files are you linking to?
aparikh756 has quit [Quit: Page closed]
<zao> Not just setting up the paths.
aparikh756 has joined #ste||ar
<zao> Are you using a debug build of HPX too?
<nikunj> yes i am
<nikunj> ^^ command line for linker
<zao> Note that nowhere in your linker command line are you actually naming "hpxd.lib"
<zao> Linker -> Input -> Additional Dependencies
<nikunj> ah, they're gone now, but new one's popped
<nikunj> so I need to add them there as well
kisaacs has joined #ste||ar
<nikunj> which file are they related to?
jaafar_ has joined #ste||ar
jaafar has quit [Ping timeout: 268 seconds]
<zao> A wild guess is hpx_initd.lib :)
<nikunj> it does build it successfully but it requires the dll
<nikunj> should I simply copy paste it in the folder itself?
kisaacs has quit [Ping timeout: 276 seconds]
<zao> Either that or set a PATH in your Debugging settings, or have a post-build step to "copy" it in.
<zao> Many fine ways.
<nikunj> zao: let me try it out
jaafar_ has quit [Ping timeout: 256 seconds]
elfring has quit [Quit: Konversation terminated!]
Anushi1998 has quit [Ping timeout: 240 seconds]
kisaacs has joined #ste||ar
<nikunj> Finally created a solution which can build hpx codes. Now i'll try to experiment with hooking on hpx wrt windows
<nikunj> zao: thanks :)
jaafar_ has joined #ste||ar
hkaiser has joined #ste||ar
jaafar_ has quit [Ping timeout: 240 seconds]
<zao> Great!
aparikh756 has quit [Quit: Page closed]
kisaacs has quit [Ping timeout: 240 seconds]
kisaacs has joined #ste||ar
anushi has quit [Remote host closed the connection]
Anushi1998 has joined #ste||ar
kisaacs has quit [Ping timeout: 268 seconds]
nikunj has quit [Quit: Leaving]
jaafar_ has joined #ste||ar
parsa has joined #ste||ar
kisaacs has joined #ste||ar