Alex https://github.com/STEllAR-GROUP/hpx/pull/2398
This will help. If you want to take on the task of going through all the HPX defines and separating them out into smaller 'groups' so that we can put them into different defines.hpp files, then please do. it's been on my @todo list for a while, but fortunately, I don't rebuild ALL of hpx very often any more, just the core and whatever exe I'm workin on, so it isn't too painful for me. I will admit though that the way all of HPX gets rebuilt every time you change one option is extremely frustrating. JB -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Alexander Neundorf Sent: 12 March 2017 22:17 To: [email protected] Subject: [hpx-users] Question regarding defines.hpp - many recompiles Hi, it seems that a change in defines.hpp triggers a rebuild of more or less everything. Also, it seems that many things end up in defines.hpp. E.g. if I enable some examples, this changes defines.hpp, e.g. enabling the OpenMP examples adds the line #define HPX_HAVE_EXAMPLES_OPENMP I would assume that nothing inside the HPX library/tools is interested in which examples are enabled. By moving the HPX_HAVE_EXAMPLES-defines into a separate .hpp file (or just not putting them into any .hpp file) one reason for full rebuilds would be removed. Comments ? Related, why is such a custom solution for creating the defines.hpp used (which builds a string internally and then puts this into defines.hpp) instead of using a normal defines.hpp.in file ? Alex _______________________________________________ hpx-users mailing list [email protected] https://mail.cct.lsu.edu/mailman/listinfo/hpx-users _______________________________________________ hpx-users mailing list [email protected] https://mail.cct.lsu.edu/mailman/listinfo/hpx-users
