hkaiser changed the topic of #ste||ar to: STE||AR: Systems Technology, Emergent Parallelism, and Algorithm Research | stellar-group.org | HPX: A cure for performance impaired parallel applications | github.com/STEllAR-GROUP/hpx | This channel is logged: irclog.cct.lsu.edu
hkaiser has quit [Quit: Bye!]
Yorlik__ has joined #ste||ar
Yorlik_ has quit [Ping timeout: 265 seconds]
prakhar has joined #ste||ar
prakhar has quit [Ping timeout: 260 seconds]
prakhar has joined #ste||ar
Neeraj has joined #ste||ar
prakhar has quit [Quit: Client closed]
K-ballo1 has joined #ste||ar
K-ballo has quit [Ping timeout: 268 seconds]
K-ballo1 is now known as K-ballo
K-ballo has quit [Read error: Connection reset by peer]
K-ballo has joined #ste||ar
Neeraj has quit [Ping timeout: 260 seconds]
prakhar has joined #ste||ar
Neeraj has joined #ste||ar
<Neeraj> can anyone tell how to build all tests seperatly
<Neeraj> separately*
<satacker[m]> `ninja <test name here>` or if you use make, `make <test name here> -j`
<Neeraj> cmake --build . --target tests      what about this command
Neeraj has quit [Quit: Client closed]
Neeraj has joined #ste||ar
prakhar has quit [Quit: Client closed]
hkaiser has joined #ste||ar
<Neeraj> when I run cmake for configure and generate of HPX tests , there no tests were built by this
<hkaiser> Neeraj: is that on windows?
<hkaiser> how do you run your tests?
<Neeraj> yes on windows
<hkaiser> and how do you run your tests?
<hkaiser> inside visual studio?
<Neeraj> they didn't built yet
<hkaiser> Neeraj: that not what I asked
<hkaiser> how do you run them? ctest? makes tests? ninja? msbuild?
<Neeraj> no I run tests in git command
<Neeraj> ctest
<hkaiser> try adding -DHPX_WITH_PSEUDO_DEPENDENCIES=On to your cmake command line
<Neeraj> firstly I run this command :- cmake . -DHPX_WITH_PSEUDO_DEPENDENCIES=On  this showing me two warnings , now second command is :- cmake --build . --target ALL_BUILD , and then I run the test by ctest command error shows that no test is related to this name
<hkaiser> please post the full logs (including your commands) somewhere and paste the link here
<Neeraj> ok
<Neeraj> https://gist.github.com/Neeraj8949/da4d82c4a4ed8d973c4816753dfef59b           first check this out
<Neeraj> In the sln file after generating the HPX tests  there  are only two projects that is ALL_BUILD and ZERO_CHECK
<zao> The tests are built as part of HPX's root CMake build as a whole, while you seem to be trying to treat hpx/tests/CMakeLists.txt as a standalone project.
<zao> If your top-level HPX directory is C:\hpx, you probably want something like `cmake -B C:\hpx\build-tests -S C:\hpx -DHPX_WITH_TESTS=ON` to generate a build tree with solution in C:\hpx\build-tests for the HPX project living in C:\HPX.
<Neeraj> *cmake .. -DHPX_WITH_TESTS=ON* by this command also generate the  same thing
<zao> In all cases you have the main HPX build and can add on examples and tests with the CMake configuration variables. I don't _think_ there's a way to build the tests separately against an existing HPX installation.
<zao> Note the importance of pointing out the top level of HPX when configuring the build, rather than the tests subdirectory.
<Neeraj> thanks zao ,Building the HPX tests separately from the main HPX build is not possible as the tests rely on the HPX libraries and headers that are built during the main HPX build
<zao> In summary, you'd configure the build for "HPX with tests/examples" exactly like you would configure a build for "HPX" - by running CMake with a build directory somewhere and pointing it at the top level HPX directory (the one with the readme and all the dot-files) and providing values for variables like HPX_WITH_TESTS and HPX_WITH_EXAMPLES. The default for tests is "ON" according to the top-level CMakeLists.txt.
<Neeraj> By build of INSTALL , tests is also build or I have to build another project file
Neeraj has quit [Quit: Client closed]
<zao> ALL_BUILD (the default target IIRC) should build everything I believe. On actually running tests, I don't actually know what you do on Windows as it's been ages since I've done it. It's either a target or running ctest or some script separately.
<zao> No idea about INSTALL, I don't have any reason to use that most of the time when testing.
<zao> Time to go to work in order to make it for the coffee break ;)
hkaiser has quit [Quit: Bye!]
diehlpk_work has joined #ste||ar
K-ballo1 has joined #ste||ar
K-ballo has quit [Ping timeout: 264 seconds]
K-ballo1 is now known as K-ballo
hkaiser has joined #ste||ar
<dkaratza[m]> hkaiser: about the GSOD application, do you have any specific parts of the docs that you would like to prioritize?
hkaiser has quit [Quit: Bye!]
hkaiser has joined #ste||ar
scofield-zliu has joined #ste||ar
scofield-zliu has quit [Remote host closed the connection]
K-ballo1 has joined #ste||ar
K-ballo has quit [Ping timeout: 276 seconds]
K-ballo1 is now known as K-ballo