Hpx Install problems / examples won't compile

[heisarun]

I got the latest repository and built using msvc and clang.

MSVC compiled the bin and lib files with include folder.
Clang compiled the libraries and no include library was generated ( how to generate include files ? ). From a old repo pick.
Here is the log of the latest build of clang. It stopped working.

hpx_clang_build.txt

Both clang and msvc generate errors when you compile the example program from documentation.
The documentation is little daunting to learn CMAKE.

Please make the documentation developer/user friendly.

____________________________________________problems compiling of examples _______________________________
std::string_view not found
byte not found

---

I manually build and got these errors. Using b2 boost build.

manual.txt

This is a msvc output for simple program using cmake with visual studio____

mainexample.txt

This Version of HPX commit ea43d66 (HEAD, tag: v1.9.0)

[hkaiser]

Please try using either the latest release (v1.11.0) or top of master.

[heisarun]

i updated msvc cmake clang and visual studio also.

commit 96204b1 (HEAD, origin/index_queue_spawning_result)
Date: Tue Mar 10 14:13:28 2026 -0500

This is the repo point, i picked.

msvc_build_output.txt
msvc_build_output_error.txt
msvc_example_compile_log.txt
msvc_example_errors.txt
msvc_install.txt
msvc_install_errors.txt

Please do reply. Thank you.

[heisarun]

For version v1.11.0 . MSVC all were successful build. Yet this error.
Clang does not build for some reason. And no headers for cmake.exe --build . --target all.
I will take time to compile and let you know

I get these errors. For example build in the documentation.

'byte': ambiguous symbol
'byte': ambiguous symbol
'byte': ambiguous symbol
'byte': ambiguous symbol
'byte': ambiguous symbol
'byte': ambiguous symbol
'byte': ambiguous symbol
'byte': ambiguous symbol
'byte': ambiguous symbol
'byte': ambiguous symbol
'byte': ambiguous symbol
'byte': ambiguous symbol
'byte': ambiguous symbol
'byte': ambiguous symbol
'byte': ambiguous symbol
'byte': ambiguous symbol
'byte': ambiguous symbol
'byte': ambiguous symbol
'byte': ambiguous symbol
'byte': ambiguous symbol
'byte': ambiguous symbol
'byte': ambiguous symbol
'byte': ambiguous symbol
'byte': ambiguous symbol
'byte': ambiguous symbol
'byte': ambiguous symbol
'byte': ambiguous symbol
'byte': ambiguous symbol
'byte': ambiguous symbol
'byte': ambiguous symbol
'byte': ambiguous symbol
'byte': ambiguous symbol
'byte': ambiguous symbol
'byte': ambiguous symbol
'hpx::stop_token::stop_token': cannot access private member declared in class 'hpx::stop_token'
'hpx': a namespace with this name does not exist
'hpx': undeclared identifier

[hkaiser]

Yes, the documentation build produces a large number of messages. I think it's ok to ignore those.

[hkaiser]

i updated msvc cmake clang and visual studio also.

commit 96204b1 (HEAD, origin/index_queue_spawning_result) Date: Tue Mar 10 14:13:28 2026 -0500

This is the repo point, i picked.

msvc_build_output.txt msvc_build_output_error.txt msvc_example_compile_log.txt msvc_example_errors.txt msvc_install.txt msvc_install_errors.txt

Please do reply. Thank you.

I don't think you should use a branch that is still under development. If that was stable it would probably have been merged to master already. Please use master or the most recent release.

[heisarun]

Yes, the documentation build produces a large number of messages. I think it's ok to ignore those.

Which way to take, to learn the library then.

[heisarun]

i updated msvc cmake clang and visual studio also.
commit 96204b1 (HEAD, origin/index_queue_spawning_result) Date: Tue Mar 10 14:13:28 2026 -0500
This is the repo point, i picked.
msvc_build_output.txt msvc_build_output_error.txt msvc_example_compile_log.txt msvc_example_errors.txt msvc_install.txt msvc_install_errors.txt
Please do reply. Thank you.

I don't think you should use a branch that is still under development. If that was stable it would probably have been merged to master already. Please use master or the most recent release.

Yes, Thank you

[heisarun]

Also i searched and found hpxcxx to be used to compile the program.
Started and it won't run. It opens a file-association picker dialog window.
Tried hpxrun.py did nothing.

I did try python.exe hpxcxx an python.exe hpxrun.py. Same as before.
i later got this.
hpxcxx_

PS C:\deployment\hpx\bin> python.exe .\hpxcxx main.cpp
Traceback (most recent call last):
File "C:\deployment\hpx\bin\hpxcxx", line 45, in
os.path.join(os.environ["HOME"],"install","hpx","lib","pkgconfig"),
~~~~~~~~~~^^^^^^^^
File "", line 709, in getitem
KeyError: 'HOME'
end______

[heisarun]

I targeted master and 1 suceeded and rest failed.
A second try.

_______________________here is the log _______________________

master_errors.txt
master_log.txt

[hkaiser]

Yes, the documentation build produces a large number of messages. I think it's ok to ignore those.

Which way to take, to learn the library then.

You can view the generated documentation here: https://hpx-docs.stellar-group.org/branches/master/html/index.html

[heisarun]

I took time and compiled an empty main.cpp program with out any hpx header and it compiled.
To the program name.

After using hpx in headers and hpx::cout in the main program.

hpx::future<hpx::naming::gid_type>::future(const hpx::future<hpx::naming::gid_type> &) noexcept: attempting to reference a deleted function

This is the only Error.

I followed the Documentation.

[hkaiser]

• hpxcxx is a python script that most likely will not work on Windows.
• hpxrun.py doesn't do anything if you don't additionally tell it what to do, it should print a help message, however
• What version of msvc do you use? I have not seen the errors you see before.

[hkaiser]

I took time and compiled an empty main.cpp program with out any hpx header and it compiled. To the program name.

After using hpx in headers and hpx::cout in the main program.

hpx::future<hpx::naming::gid_type>::future(const hpx::future<hpx::naming::gid_type> &) noexcept: attempting to reference a deleted function

This is the only Error.

I followed the Documentation.

I would have to see the full code you're trying to compile.