Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Errors during "Compile it yourself" installation at build_conda_package.bat #213

Open
baccigalopi opened this issue Nov 29, 2023 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@baccigalopi
Copy link

baccigalopi commented Nov 29, 2023

Several errors were encountered during the "build_conda_package.bat" command within the Anaconda prompt when following the "Compile it yourself" instructions (https://trex.run/docs/install.html#compile-it-yourself). The text from the prompt, which contains the error report, is attached below. After encountering these errors, attempts to install TRex via "conda create -n tracking -c local trex" were unsuccessful. How might I address these errors?

Note, I first installed TRex using "The easy way" for Windows, which seemed successful and even allowed me to initially use the "conda activate tracking" and "deactivate tracking" commands. However, since I desire to utilize Basler cameras in the future, I then elected to repeat the installation process using the "Compile it yourself" instructions, which is when I discovered the error.

To Reproduce
Steps to reproduce the behavior:
(base) C:\Users(name)>conda install conda build
Proceed ([y]/n)? y
(base) C:\Users(name)>git clone --recursive https://github.com/mooch443/trex
(base) C:\Users(name)>cd trex/conda
(base) C:\Users(name)\trex\conda>build_conda_package.bat
***ERROR ENCOUNTERED DURING THIS STEP, SEE ATTACHED DOCUMENT ***

Terminal output file attached.

Expected behavior
I expected the "build_conda_package.bat" to perform an error-free load and permit the TRex installation; however, as shown at the end of the attached error report, TRex does not load and is listed as a "package not available for current channels."

Computer:

  • Operating/computer system: Windows 10, NVIDIA GeForce RTX 2080 SUPER, NVIDIA CUDA 12.1
  • Terminal used - Anaconda Prompt 2023, Python 3.9, Visual Studio 2019 (note, according to the attached terminal output, it seems to only be looking for Visual Studio 2016)

Error Report.txt

@baccigalopi baccigalopi added the bug Something isn't working label Nov 29, 2023
@mooch443
Copy link
Owner

Hey, thanks for the report and sorry for the delay! Looking forward to the day where I can just let an AI do this reliably.

I have updated the description at https://trex.run/docs/install.html#compile-it-yourself, but essentially what is happening is that you will need to install Visual Studio 2019 on your PC if you want to compile the software for conda. While the next section states that 2022 is also supported, it is not supported by conda-build at the moment.

@baccigalopi
Copy link
Author

Thank you for the response. I have now ensured "Visual Studio Professional 2019" was installed, where I previously had "Visual Studio Community 2019," so that error during installation is no longer present. However, I seem to have different errors now, to include several "Entry Point Not Found" errors and what seems to be permission errors, even though I have ensured the ProgramData\anaconda3 and \trex, along with all subfolders, have Full Control. Have you experienced these issues or have any additional advice? (supporting documentation screenshots and error report attached)

20240103_TRex Error Report 2.txt

Entry Point Not Found Errors

Full Control for folders

@mooch443
Copy link
Owner

Hey, that seems odd. Although it appears to be a git error, not a TRex error - or more likely some kind of network access problems. Github sometimes has "slower" times, which can lead to errors, and sometimes it is the policies governing your connection. You could try from a separate location, for example, to see if the network connection is the issue here.

Also, my conda is installed in the user home directory - I don't know if that makes a difference?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants