13:51 <diehlpk_work> heller, Are you interested to attend the call with the Los Alamos people next week?

20:02 <heller> diehlpk_work: what will it be about? Will Al send me an email now with the issues he's running into?

20:03 <diehlpk_work> heller, https://github.com/hpc/kraken

20:04 <diehlpk_work> They developed a tool to boot the PI Cluster and he will explain how it is working and how e might could use it

20:27 <khuck> hey everyone - quick question... does HPX no longer generate hpx/config.hpp?

20:28 <khuck> I am trying to build HPX with APEX, and the APEX source code that includes HPX headers first includes hpx/config.hpp, and now it's failing. My builedbot server has been down for most of the last 3 weeks, so it could have been an older recent change.

20:28 <khuck> [ 7%] Building CXX object apex/src/apex/CMakeFiles/apex.dir/apex.cpp.o

20:28 <khuck> /home/users/khuck/src/phylanx/tools/buildbot/src/hpx/apex/src/apex/apex.cpp:12:10: fatal error: hpx/config.hpp: No such file or directory

20:28 <khuck> #include <hpx/config.hpp>

20:28 <khuck> ^~~~~~~~~~~~~~~~

20:28 <khuck> compilation terminated.

20:29 <parsa> khuck: it's still there. no clue why yours is missing

20:31 <K-ballo> hpx/config.hpp ?

20:33 <K-ballo> was config.hpp ever generated?

20:33 <K-ballo> it has moved into a module

20:35 <K-ballo> does this mean using hpx without cmake now requires messing with include directories?

20:36 <K-ballo> looks like it does

20:36 <hkaiser> khuck: I think this is an artifact of the stable tag issues we were discussing

20:37 <hkaiser> please remove your build directory (but you probably do that already)

20:46 <khuck> should I just use head of master?

20:47 <khuck> hkaiser: I do delete the build directory first

20:51 <hkaiser> khuck: worth a try

20:53 <K-ballo> are we positive we are properly exporting all the new include directory paths in our exported cmake targets?

20:53 <khuck> that was my next question - whether include paths changed

20:53 <K-ballo> they did, hpx/config.hpp moved

20:54 <K-ballo> hpx/config.hpp the physical file, the include remains <hpx/config.hpp>, but the include directory path is different

20:55 <khuck> I used to expect it in ${CMAKE_BINARY_DIR}

20:55 <K-ballo> no.. config.hpp was never generated

20:56 <K-ballo> are you thinking of defines.hpp ?

20:56 <khuck> APEX has included hpx/config.hpp for several years now.

20:56 <K-ballo> yes

20:57 <K-ballo> not from ${CMAKE_BINARY_DIR} though, unless it was copying it there..?

20:57 <khuck> unknown. still trying to debug this

20:57 <K-ballo> config.hpp is a tracked file, it does not get generated at configuration time

20:57 <khuck> ok, so where is it supposed to be?

20:58 <K-ballo> it used to be at <hpx-ROOT>/hpx/config.hpp, now it moved to <hpx-ROOT>/libs/config/include/hpx/config.hpp

20:58 <khuck> is there an "HPX-approved" way to add include paths to subdirectories?

20:59 <K-ballo> no, only the cmake targets are supported

20:59 <K-ballo> find_package(HPX) or whatnot

21:00 <khuck> APEX is a subdirectory of HPX, built with HPX - not a separate library

21:01 <K-ballo> then no need for find_package(HPX), just naming the targets ought to be sufficient

21:01 <K-ballo> APEX should not be manually configuring include directory paths for HPX in that case

21:03 <khuck> so...how do I add the include paths, if not "include_directories(${CMAKE_SOURCE_DIR}/libs/config/include)" ?

21:05 <K-ballo> it should not be adding include paths at all, it should just be linking the targets (modern cmake), or inheriting those from global directory scope (old cmake)

21:06 <K-ballo> I'm not familiar with hpx's own cmake framework to know which of those it implements, but gathering and setting all those include paths is its responsibility, not APEX's

21:08 <khuck> I am even less familiar.

21:13 <hkaiser> khuck: I positive that all directories are exported with their targets

21:13 <hkaiser> khuck: you already added hpx_preprocessor as a dependency to APEX, you might have to add the new modules as well

21:14 <khuck> I did

21:14 <hkaiser> or even just hpx_config as a dependency

21:14 <khuck> what are the others?

21:14 <hkaiser> that one recursively depends on hpx_preprocessor, so no need to have hpx_preprocessor

21:15 <hkaiser> khuck: yah, APEX is special as it is built as part of HPX and needs special handling

21:15 <hkaiser> khuck: as we add more modules we might have to update the APEX dependencies as well...

21:22 <khuck> hpx_cache depends on hpx_config depends on hpx_preprocessor

21:22 <khuck> so far...

21:26 <khuck> hpx_cache seems to be sufficient