Hi,
thanks for the detailled answer, but I still have a few questions.
On 2017 M03 30, Thu 17:14:46 CEST Hartmut Kaiser wrote:
> > On 2017 M03 24, Fri 16:53:03 CEST Hartmut Kaiser wrote:
> > > Alex,
> > >
> > > Sorry for the delay, just as a heads-up: I'll get back to you later
> > today.
> > I know it's not fancy, but could you havea look ?
>
> Alex, I sincerely apologize for the delay. Too many things are going on at
> the same time.
>
> > find_prefix(), according to the code and to the documentation, returns
> "the installation path of the specified module", i.e. 1 path.
> > Why is there the need to tokenize that using a PATH_DELIMITER (":" here)
> > and
> > then iterate over all tokens ? It looks to me like there is always exactly
> > one path ?
>
> While find_prefix() may in principle return a list of directories. The
> original idea was to encode there the build directory and the installation
> directory of the core library.
Hmm, I'm not sure I understand.
find_prefix() should return the prefix where the library is installed, right ?
What do you mean with encode "the build dir AND the installation dir" ?
Shouldn't the install dir be enough ?
A related question, why is HPX_PREFIX adjustable by hpx-using projects (e.g.
in hpx::init(): util::set_hpx_prefix(HPX_PREFIX);
Thanks
Alex
_______________________________________________
hpx-users mailing list
[email protected]
https://mail.cct.lsu.edu/mailman/listinfo/hpx-users
