Closed NeoYY closed 1 month ago
Yes, that is correct. tapac
is the "main" executable of TAPA. tapacc
is a C++ source-to-source transformation tool, which is an internal component of TAPA and will be called from tapac
as part of the compilation process.
Yes, that is correct.
tapac
is the "main" executable of TAPA.tapacc
is a C++ source-to-source transformation tool, which is an internal component of TAPA and will be called fromtapac
as part of the compilation process.
In that case, if we cannot call tapac after installation, while can only call tapacc, that still means we messed up something during installation, is that correct? Otherwise, if tapacc is what we looking for after install from source, is there any document for specifically for tapacc that we can refer? Thank you!
Yes, that is correct.
tapac
is the "main" executable of TAPA.tapacc
is a C++ source-to-source transformation tool, which is an internal component of TAPA and will be called fromtapac
as part of the compilation process.In that case, if we cannot call tapac after installation, while can only call tapacc, that still means we messed up something during installation, is that correct? Otherwise, if tapacc is what we looking for after install from source, is there any document for specifically for tapacc that we can refer? Thank you!
Did you try https://tapa.readthedocs.io/en/release/installation.html#verify-installation
If tapac
is still not found, make sure python3 -m pip install tapa/backend/python
finished without error.
python3 -m pip install tapa/backend/python
finished without errors. However, we are trying to install tapa into a server, and running both installation methods will install it into/.local/bin
instead of /local/bin
. This cause only the root user can call and access tapac without errors. Even if we link tapac from /.local/bin
to /local/bin
, it still causes a permission denied error on the user side. Do you have any tips for installing tapa on the server and granting all users access? Thank you!
If you would like to install tapac for all users, please run python3 -m pip install tapa/backend/python
as root. The tapac
executable should appear as /usr/local/bin/tapac
.
Fixed! Thank you!
tapac --help => This command works fine. Thank you!
I am trying to run a simple vadd example from (https://tapa.readthedocs.io/en/release/getting_started.html). These are the steps I followed
git clone https://github.com/UCLA-VAST/tapa
=> Clonned the existing code code. I didnt modify any of the code
cd tapa/apps/vadd
g++ -o vadd -O2 vadd.cpp vadd-host.cpp -ltapa -lfrt -lglog -lgflags -lOpenCL
=> Compiled it.
I get the following error.
Please let me know if you can help me with this issue. Again thank you and the team so much for all the back and forth
Can you try adding -std=c++17
to the compiler arguments?
The most current version of TAPA should be compiled with just bazel build //...
. We do not have documentation for now and contributions are welcome. You may refer to https://github.com/rapidstream-org/rapidstream-tapa/tree/main/.github/workflows for how to run them.
I am closing this issue for now and please feel free to reopen if you have further questions.
Hi, we follow the tutorial here, with option 2. However, after we finshed the Build and Installation, we ended up with a tapacc executable. Is that correct? What is the difference between tapac and tapacc? Thank you!